> 1. class that can have more then one object as it's parent (at this
Multiple Inheretance. Difficult to understand, difficult to implement,
but I have a problem where multiple inheretance was the solution, instead
of multiples interfaces.
> 2. Powerful containers for class usage such as class X requires class
Same as templates/generics.
> 3. Better/Faster IO usage ;)
Better designed I/O libraries/classes ?
> 4. The amount of classes that comes with Java as part of the compiler :P
Can live with them. Make your own libraries.
> 5. Associative/anonymous classes (like in script language).
Not recomemnded. Dificult to control.
> 6. "inline" code inside class (like in C++/Java).
Not recommended. Bad design.
> 7. Build in regex syntax like in Perl, Ruby Javascript.
Replace it, by a library.
> 8. Templates. (there is something that is cooking)
OK. This one is right. We reealy need templates/generics support.
> 9. Hashes (associative arrays) -> Yes there are classes that mimic
Classes with indexed properties work and look like associative arrays.
> 10. The infamous support of "..." for "infinite' parameters (You can
Open arrays.
> And I had more things on my list I just don't remember all of them at
> the moment ...
1. operator overloading
type
X: TMyType;
operator +(A, B: TMyType): TMyType;
2. Property type overloading.
type
TA = class
...
end;
TB = class(TA)
...
end;
TC = class
...
property X: TA;
end;
TD = class(TC)
...
property X: TA as TB;
end;
NOW, TD.X property is TB class not TA.
If you declare a TD variable, with this feature,
you no longer need to cast the X property to TB type
each time you need it.
> There is the D language and other mutant of that language that suppose
I think D IS BETTER. But not enough.
-----
Marco Aurelio Ramirez Carrillo
lazarus dot mramirez at star-dev dot com [dot mx]
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
