The author of a book I'm reading has a rather narrow world view, basically thinking that Microsoft products and Win32 are the entire history of computing. He makes sweeping statements, but obviously doesn't know other languages like Self, CLOS, Smalltalk, or Perl.
Anyway, one thing he points out is the ability to supply a default initial value for a data member when it is declared, and not have to specify that value as an initializer in every contructor (though it has that effect). He says (implied all) other OO languages can't do that.
Update: add example pseudocode
In pseudo-C++ (I don't want to butcher C# since I don't know it yet), it would be something like this:
That is, for all constructors, not initializing a value will imply the global initialier's value, without specifying the same value in each constructor.class C { int x= 5; int y= 9; public: C() {}; // don't need to state x,y values. C (int xx) : x(xx) {} // y=9 without me saying it again. };
But, I seem to remember such a thing in one of the Perl object systems. Does anyone know which one that might be?
Second, what ever happened to ActiveState's Perl.NET? I heard lots of hype once upon a time, then reports that it didn't work but they are providing a seemless way to integrate Perl with .NET (which is all I care about the idea anyway). Has anybody used it and reported on it in detail yet?
--John
In reply to OOP, ".NET", Perl, and all that by John M. Dlugosz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |