If you request for features please come up with something realistic and also provide good information how it then should work. E.g. provide grammar how the syntax and semantics work. And if it is for compatibility you should also be able to provide real pascal examples that show how ambigious constructs are handled by Delphi.
So please answer first the question that Marco already wrote before continueing other discussions about this topic: Take as example the reference to a.b.c.d. - Can someone provide the grammar how an identifier looks like in Delphi? - How shall the compiler detect that "a.b" is an unit if a is also defined as a record that doesn't contain a field b? - How shall the compiler handle if "a.b.c" is an unit and a.b.c is class? So please come with a design instead of just asking give me this feature in one line. Because if the feature was really important and simple it was for sure already implemented. The left over features are therefor not in the category simple anymore. Also important is debatable because we've already lived without them for years. Peter _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
