[fpc-pascal] Object pascal language compatiblity - was: Does FPC 2.8.0 can actually still be called Pascal ?

[Dimitri Smits]

----- Oorspronkelijk e-mail -----
> Van: "Florian Klämpfl" <florian at freepascal.org>
> Aan: "FPC-Pascal users discussions" <fpc-pascal at lists.freepascal.org>
> Verzonden: Vrijdag 1 maart 2013 18:13:42
> Onderwerp: Re: [fpc-pascal] Object pascal language compatiblity - was: Does	FPC 2.8.0 can actually still be called
> Pascal ?
> 
> Am 01.03.2013 11:04, schrieb Sven Barth:
> > 
> > But even if LLVM would support all targets that FPC supports the
> > core
> > developers don't *want* to make LLVM the default.
> 
> Actually, I wouldn't have any interest working on a compiler using
> llvm
> as a backend because it leaves only the boring front end work :) Not
> to
> mention the maintainance problems when depending on an external cg
> written not in pascal, the probably significant speed drop etc.
> 

as a matter of fact, the llvm-stack is not just your front-end to provide the intermediate bytecode (or textual variant)! You can provide/maintain multiple plugins for almost every "pass". Going from optimisation passes to the entire "executable generation" as back-end. Admittedly you need to make a C(++?) compatible interface, but I think nobody stops you from making those passes/plugins in FPC...

on the other hand... the speed difference with Delphi XE 3.5 or later would level out a bit more :-)

that being said, Embarcadero will surely implement such proprietary passes/plugins and additions for their own benefit.

At least I am very curious to next fall when the next version(s) come out. Not in the least if they also support Android with a cross-platform library/interface between iOS and Android for common features, like they 'promised' last fall on a conference. (BE-Delphi last november)

full disclosure: yes, paying owner of a licence DXE3

kind regards,
Dimitri Smits