[fpc-pascal] const records passed incorrectly
sysrpl at gmail.com
Mon Nov 16 15:29:22 CET 2009
As I said in my introduction. I am new to Linux and FPC. I've used
them both for maybe 8 years, but not seriously.
On the Linux side for years I've just used it for minimal compiling
and a lot of web browser.
On the FPC I've fired it up from time to time over the years (and read
the website, mailing lists).
None of that I consider real use, just casual poking around.
But now I am taking a serious stab at porting my Windows OpenGL game
engine to a cross platform Windows, Linux, and Mac engine. I feel like
I am actually doing something real with Linux and FPC for the first
One thing I've noticed about the FPC community which has me a somewhat
apprehensive is a bit of a particular attitude I've picked up on.
A few times now I've read comments by or had conversations with people
in the FPC community who have explained incompatibilities away using
"FreePascal did this before something else so we shouldn't change"
Forgetting the whole argument about who was actually first, I have to
ask what difference does it make?
Why does doing something first make it written in stone. It seems a
bit childish to say, "No way, I way here first, I won't budge. You
Really, that attitude is quite the turn off.
There there these incompatibilities causing me to avoid language
features. I'd like to use them but just won't (Operator overloading
and generics come to mind), mostly because I really don't want to have
ifdefs all over the place.
In my opinion, there is an incompatibility. Fix it.
On Mon, Nov 16, 2009 at 9:03 AM, Jonas Maebe <jonas.maebe at elis.ugent.be> wrote:
> On 16 Nov 2009, at 15:01, Anthony Walter wrote:
>> Jonas, why is FPC emulating C when it could simply follow the Delphi
>> way and prevent these incompatibilities?
> I think that FPC's behaviour predates the existence of Delphi.
> fpc-pascal maillist - fpc-pascal at lists.freepascal.org
More information about the fpc-pascal