XPost: comp.os.linux.advocacy   
   From: ahlstromc@xzoozy.com   
      
   Tom Shelton pulled this Usenet face plant:   
      
   > Chris Ahlstrom formulated on Sunday :   
   >> Tom Shelton pulled this Usenet face plant:   
   >>   
   >>> Chris Ahlstrom pretended :   
   >>>>   
   >>>> Hmmm.  As far as I can tell, a delegate is a function pointer, or a member   
   >>>> function pointer.  (I know there is more to it than that, of course).   
   >>>   
   >>> I would say that a delegate is closer to the function objects in the   
   >>> STL.  A delegate is an object that wraps a function pointer.   
   >>   
   >> This discussion could get pretty hairy!  A delegate also lets you insert   
   >> functions into the list, so they all get called.  A bit of a solution   
   >> looking for a problem, but nifty.   
   >   
   > Yes, it allows for multi-cast scenario's where one object can notify   
   > multiple clients with a single call.   
      
   It's multiple callbacks.   
      
   I wonder if signals/slots (e.g. as provided by Qt or Boost) are better.   
   Or, more accurately, how do their use cases overlap?   
      
   >> Anyway, there's quite a difference in the way C# and C++ apportion   
   >> functionility between the language itself and to libraries.  No doubt that   
   >> C# is pretty tightly coupled to .NET.   
   >   
   > C# is coupled to .net for certain things, but that's what it was   
   > designed for :)   
      
   I have to admit I was a bit "gobsmacked" to find that some C# key words   
   (e.g. "char") are simply aliases for .NET objects.   
      
   I find that idea difficult to "consume"  :-D   
      
   --   
   If an experiment works, something has gone wrong.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)