[fpc-pascal]The state of FPC - wrap up

Boguslaw Brandys brandys at o2.pl
Fri Jul 25 17:24:24 CEST 2003


Just for adding my few cents : I'm not keen on FPC , and rather know a
little about FPC design but I think this is academical disscuss becouse
Pascal never used preprocessor like C++ and becouse of that was so fast, but
also so complicated when  using it in multiplatform envinronment.
Look into wxWindows details and You will find that an platform independent
code and platform dependent library working very good together ! And even
processor specific such like type declaration or machines with different
byte orders is doable that way.

I'm not insist that it is the right solution for FPC, but looking into it
could help.


----- Original Message -----
From: "Michael Van Canneyt" <michael.vancanneyt at wisa.be>
To: <fpc-pascal at lists.freepascal.org>
Sent: Friday, July 25, 2003 10:12 AM
Subject: [fpc-pascal]The state of FPC - wrap up

> Hello,
> I think the point about users finding include files cumbersome to use,
> and developers who require maintainability, has been made clear.
> We can discuss about this for ages, and never agree. So I would like to
> conclude the discussion with a proposal.
> My proposal is as follows:
> If someone contributes a tool which does the necessary preprocessing
> i.e. including needed files, then I will set up a system where the
> source files are 'assembled' into single-source units for a given
> platform/cpu combination. These single-source units can be distributed
> with each platform or separately downloaded.
> This tool can be run on a daily basis on our CVS server, and zips can be
> made available as a service to the FPC users.
> As for the tool, I ask only 3 things:
> 1. It should compile with FPC and should be cross-platform.
> 2. Should obey {$ifdefs}/{$define} and the like, such as
>    run-time platform selection.
>    (linux based tool must generate sources for e.g. win32)
> 3. As for the rest, it would be good to have the command-line options
>    which match the compiler's:
>    -d define symbol
>    -u undefine symbol
>    -I/-Fi set include path
>    -T select target os/cpu
>    -FE set output name.
> If someone makes this tool, I will do the rest.
> Hopefully, this proposal helps to end an otherwise lengthy discussion.
> Michael.
> _______________________________________________
> fpc-pascal maillist  -  fpc-pascal at lists.freepascal.org
> http://lists.freepascal.org/mailman/listinfo/fpc-pascal

More information about the fpc-pascal mailing list