On 6/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> 4. The amount of classes that comes with Java as part of the compiler :P Can live with them. Make your own libraries.
i think that is wrong thinking. one of the reasons i was drawn to freepascal, and then lazarus, being a java developer, was because of the richness of the libraries that were bundled with the software. the more the better, and then the better an alternative Pascal/Lazarus becomes to 'C'.
> 5. Associative/anonymous classes (like in script language). Not recomemnded. Dificult to control.
control ? like a car ? like a dog ? what is hard to control ?
> 6. "inline" code inside class (like in C++/Java). Not recommended. Bad design.
hooey. there is nothing "bad" about inner classes. this is like saying the use of a "Type" that is private, but is intended to aggregate some attributes is "bad design". inner classes in Java are an awesome construct. it allows you to model your implementation, using classes as required, so that your implementation is robust, but where some of those classes aren't useful outside of the implementation, you don't have to pollute your namespace with classes that won't ever be used by other parts of the application.
> 9. Hashes (associative arrays) -> Yes there are classes that mimic Classes with indexed properties work and look like associative arrays.
how do index'ed properties help you store objects by a key ? i've not seen this technique. Tony -- X-SA user ? 0.5.1 is out ! XData 0.1 for X-SA is out ! http://x-plane.dsrts.com _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
