Hello.

Does it exist a option to compile fpc without Delphi compatibility ?

If no, what do you think about that ?
I know, it will be lot of work (like create a Delhi_Compatiblizer class...)

PS : I absolutely do not want to hurt somebody, it is only a proposition.

-----
Many thanks ;-)

Hello.

Does it exist a option to compile fpc without Delphi compatibility ?

If no, what do you think about that ?

I know, it will be lot of work (like create a Delhi_Compatiblizer class...) but it could be great for people who want a "lighter" compiler...(like me, who have already done, since years ago, the fpc migration)...

PS : I absolutely do not want to hurt somebody, it is only a proposition.

Many thanks.

Fred

Ooops, sorry for 2X same topic...

I used http://free-pascal-general.1045716.n5.nabble.com/ for first topic it responds that the message was refused...

So i sent the second one, as usual, with hotmail.com...

Fred

And what would be the benefit of doing that? If you don't like the Delphi mode, then simply use one of the other compiler modes :)

Nikolay

What extent of Delphi incompatibility would satisfy you?

{$objfpc}
has offered 'mild' incompatibility for many years. What additional incompatibilities are you looking for?

Howard

Hum, maybe i do not explain good the proposition...

I
do not want a other {$define not Delphi}, i would like to compile fpc himself witout the Delphi-compatible module-class (if there are one, but i do not think it is like that in fpc).

And the proposition was,
if there are not a "special" class for Delphi compatibility ( only some

  {$ifdefine Delphi}, inside fpc.source code ) to create a "Delphi

compatibility class" and use parameter for compile fpc himself :

if (ParamStr(2) = 'delphi') then => include Delphi class.

Re-hum,...

It seams to me that fpc do not need delphi-compatibility to compile himself (or i miss something).

So it could be possible to compile fpc without any Delphi-compatible module (Yes/No).

But maybe it does not will change lot of things, only it will make fpc a few "lighter" (so forget that stupid proposition).

fredvs wrote

Hello. Does it exist a option to compile fpc without Delphi compatibility ?

does {$mode objpfc} not suit your needs? ;)

or whatever the default is? O:)

Ok, i will try to explain better.

When you compile fpc, you do > make clean + make all.

Is it possible to configure fpc-compil and disable Delphi compatibility...?

If not possible, no problem, i only want to know :-) .

Fred

Hello Waldo.

Aaargh, there is double-topic, can you look at the twins topic ?

Thanks.

Short and simple answer - no, it isn't possible.

Slightly longer answer - even if disregarding mode "DELPHI", there are several other modes supported by FPC. More than one mode is used within the FPC source tree (at least FPC, OBJFPC and MACPAS). The modes do not differ only by syntax but also by the supported features, but different modes use a combination of features often also used in other modes. All in all, even if someone wanted to perform the surgery and remove all references to mode DELPHI, the potential gains with regard to compilation speed would be probably very limited.

Finally - trying to remove a feature allowing users to reuse source code coming from others doesn't sound very smart even if somebody doesn't use such external source code today.

Tomas

Hello.

Thank you Tomas for your cool and clear answer.

Finally - trying to remove a feature allowing users to reuse source code coming from others doesn't sound very smart even if somebody doesnt use such external source code today.

Hum, yes, you are right...

Long life for fpc....

27.01.2014, 15:02, "Fred van Stappen" :

More compiler modes = more complexity = more difficulties for people who support & develop FPC Over time FPC and Delphi modes are becoming increasingly incompatible. I predict that sooner or later FPC developers will have to drop Delphi mode support because FPC & Delphi modes will become just too different to be built in one compiler. Maybe we will have two compilers: FreeDelphi and FreePascal. Note that Embarcadero introduces more and more new features to their product. FPC already can't support many of them. For example, string in Delphi 2009 and later is double-byte string; char is widechar. In FPC Char is still 1-byte char even in Delphi mode. What I think will happen is that at some point FPC will no longer be able to add more new Delphi features support to Delphi mode like it already happened with string=widestring, so Delphi mode in FPC will always mean Delphi 2007 and earlier. The reasons is that introducing new Delphi features to FPC Delphi mode is becoming increasingly difficult because Delphi and FPC are following different paths; so we are likely to be left with Delphi 2007 compatibility forever. So perhaps FPC developers can safely remove Delphi mode support in 2027... Well, for now we can still reuse Delphi libraries which are supposed to work in Delphi 2007 or earlier; these are good news. Having both Delphi and FPC modes in one compiler had sense while these modes were similar; but with latest Delphi versions this is no longer the case.

We will add string=widestring in the next (or next+1) trunk release.

What else is missing ? Only anonymous functions, to my knowledge.

Michael.

Michael Van Canneyt wrote

On Mon, 27 Jan 2014, hinst wrote: > so Delphi mode in > FPC will always mean Delphi 2007 and earlier.

The above is correct.

We will add string=widestring in the next (or next+1) trunk release.

... in {$mode delphiunicode}, which will mean Delphi 2009 and later (well, or maybe Delphi XE or XE2 or later over time).

Jonas

have

> two compilers: FreeDelphi and FreePascal. Note that Embarcadero > introduces more and more new features to their product. FPC already

can't

Nitpicking: it's String=UnicodeString. WideString is at least on Windows systems something different...

What else is missing ? Only anonymous functions, to my knowledge.

Extended RTTI, generic methods (and depending on who you ask: ARC for classes)

Regards,
Sven