big deal they are playing god.
Its pretty funny that your comment totally supports genetic screaning of unborn infants, except for your one argument... (which is total bs, and holds no weight)
Society started playing god first, when they started giving aid to children who would normally die because they are not possibly able to support themselves. This is in the form of aids for retarted kids, and drugs for people with diseases that are always fatal at early ages (and both these are totally genetic).
So either society should let the people die, who would otherwise die if not for their unholy intervention; OR, they should genetically screen the children so they are never born with the burden of dying early or having to take medicine for their entire lives and die early as well, just not as early, and either way suffer more than they should.
> Personally, I found C# support of events to
> be a very exciting new feature! Whereas an
> object method operates the object in a
> certain way, object events let the object
> notify the outside world of particular
> changes in its state.. A Socket class, for
> instance, might define a ReadPossible event > or a data object might release a
> DataChanged event. Other objects may then
> subscribe for such an event so that they'd
> be able to do some work when the event is
> released. Events may very well be
> considered to be "reverse- functions", in
> the sense that rather than operate the
> object, they allow the object to operate
> the outside world, and in my programming
> experience, events are almost as important
> as methods themselves.
Sounds an awful lot like the Trolls Qt Lib way of doing events. Slots and Signals, where a signal is simply a defined like a method, but in the signals: part of the class.h file. and you simply connect(class, signal, slot); in your code.
Definatly not much of an innovation on MSs part.
Slashdot Mirror
big deal they are playing god.
Its pretty funny that your comment totally supports genetic screaning of unborn infants, except for your one argument... (which is total bs, and holds no weight)
Society started playing god first, when they started giving aid to children who would normally die because they are not possibly able to support themselves. This is in the form of aids for retarted kids, and drugs for people with diseases that are always fatal at early ages (and both these are totally genetic).
So either society should let the people die, who would otherwise die if not for their unholy intervention; OR, they should genetically screen the children so they are never born with the burden of dying early or having to take medicine for their entire lives and die early as well, just not as early, and either way suffer more than they should.
> Personally, I found C# support of events to
.h file. and you simply connect(class, signal, slot); in your code.
Definatly not much of an innovation on MSs part.
> be a very exciting new feature! Whereas an
> object method operates the object in a
> certain way, object events let the object
> notify the outside world of particular
> changes in its state.. A Socket class, for
> instance, might define a ReadPossible event
> or a data object might release a
> DataChanged event. Other objects may then
> subscribe for such an event so that they'd
> be able to do some work when the event is
> released. Events may very well be
> considered to be "reverse- functions", in
> the sense that rather than operate the
> object, they allow the object to operate
> the outside world, and in my programming
> experience, events are almost as important
> as methods themselves.
Sounds an awful lot like the Trolls Qt Lib way of doing events. Slots and Signals, where a signal is simply a defined like a method, but in the signals: part of the class