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.

I was just asking why FPC can't compile a unit that has dot(s) within its file name, since Delphi allows it. I know nothing about compiler so I can't provide enough informations how it should work. If it's too much, then forget it... I can live happily with current FPC.

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 discussion goes wider to namespace and (Delphi).Net features. I didn't intend to go that far. I don't even know what namespace exactly is, let alone use it. I just want to have dot(s) within my unit's file name. That's all. If it's too much, then forget it... I can live happily with current FPC. As Michael suggested, I would change the dot to underscore. Fine.

Also important is debatable because we've already lived without them for years.

Ah, you should throw away your car, your cellphone, or even your laptop. Those are not important, because humans had already lived happily without them for ages! :-P

-Bee-

has Bee.ography at:
http://beeography.wordpress.com

_______________________________________________
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Reply via email to