[fpc-devel] Some compiler changes...

Michael Van Canneyt michael.vancanneyt at wisa.be
Tue Jan 23 09:41:22 CET 2007



On Tue, 23 Jan 2007, Dani=EBl Mantione wrote:

> =

> =

> Op Tue, 23 Jan 2007, schreef Michael Van Canneyt:
> =

> > I think this goes against all that pascal stands for. We don't want to
> > butcher the language. Next thing you'll be asking to have it case sensi=
tive.
> > As a programmer you know that certain keywords are keywords. Don't use =
them
> > in your fields/variables whatever. Keep you code readable.
> =

> Well, there are many things in Delphi against all Pascal stands for. Yet =

> we need it for compatibility, and despite our, IMHO totally =

> reasonable, clean-up attempts $mode delphi might even be used more =

> than $mode objfpc :(

Well, not in e.g. lazarus, and only to 'import' delphi code.

> I think history has shown that it is not wise to reject things. IMO, the =

> features can be provided in a Chrome mode, while fpc and objfpc remain =

> clean Pascal. Even that has its limits, code exchange must remain =

> possible between fpc and non-fpc modes, but despite all the crap, we can =

> at least try to keep them clean.

In that case I suggest introducing a rule that all FPC provided code is =

fpc or objfpc or macpas (for unified pascal headers) mode.

And if we implement this, we should also introduce the foreach and whatever =

other insane things Borland thinks of the last years, which we refused with
arguments like "it's only a typing saver". You can't sit on two chairs at
once.

We should at least be consequent in our policies.

Personally, I think the foreach is even more reasonable than this.
Pascal is a readable language. This proposal seriously threatens that.

Michael.


More information about the fpc-devel mailing list