• weaselcat (4/4) Mar 05 2015 Seems barely maintained and there was a proposed replacement
• ketmar (12/17) Mar 07 2015 they both suxalot. both of them are ugly, and people tend to avoid ugly=...
• Jonathan M Davis via Digitalmars-d-learn (16/20) Mar 07 2015 I think that the wiki page pretty much says what needs to be said. Any

"weaselcat" <weaselcat gmail.com> writes:

Seems barely maintained and there was a proposed replacement 
claiming it was broken(http://wiki.dlang.org/Review/std.signal) 
that never got approved.

Is std.signals worth using over a dub package?

ketmar <ketmar ketmar.no-ip.org> writes:

On Thu, 05 Mar 2015 21:54:01 +0000, weaselcat wrote:

 Seems barely maintained and there was a proposed replacement claiming it
 was broken(http://wiki.dlang.org/Review/std.signal)
 that never got approved.
=20
 Is std.signals worth using over a dub package?

they both suxalot. both of them are ugly, and people tend to avoid ugly=20
things. i believe that singal/slot concept must have some support in the=20
compiler. i don't want to throw all that stupid templates everywhere, and=20
i don't want to mixin things manually. i want to tell the compiler that=20
this method is  signal, that method is  slot, and compiler will happily=20
do the hidden things for me. the same with `connect` and `emit`. ah, and=20
`emit` must be keyword, just like in Qt.

i will do that in Aliced eventually.

the only thing i'm unsure is `connect`: i still can't think out the nice=20
syntax for it. maybe i'll reintroduce that nice C arrow ("->"), but this=20
time for good. ;-)=

Jonathan M Davis via Digitalmars-d-learn writes:

On Thursday, March 05, 2015 21:54:01 weaselcat via Digitalmars-d-learn wrote:
 Seems barely maintained and there was a proposed replacement
 claiming it was broken(http://wiki.dlang.org/Review/std.signal)
 that never got approved.

 Is std.signals worth using over a dub package?

I think that the wiki page pretty much says what needs to be said. Any
replacament to std.signals would have to get through the Phobos review
queue, and that hasn't happened yet. And aside from a few folks, there has
been very little interest in it one way or the other. So, std.signals will
be around for a quite a while and so you shouldn't have to worry about
needing to switch your code to something else anytime soon if you use
std.signals, but if you want something where active work is being done on
it, then you'll need to find an implementation elsewhere.  Given the dates
on std.signals, it looks like it was done for D1 by Walter Bright and has
just kind of stuck around since without getting any kind of overhaul, so it
may or may not be of a particularly relevant design at this point (I've
never used it or really looked at it, so I have no idea how suitable it is
at this point).  But I expect that which solution you should use really
depends on what you're looking for and what the available solutions provide.

- Jonathan M Davis