Re: [fpc-devel] Simplicity vs. Complexity

2019-03-26 Thread J. Gareth Moreton
Food for thought indeed. One of my past contracts was to decipher an old database that I could only describe as Frankenstein's Monster. Everyone who had developed it had long left the company and no-one dared touch it, because it worked but no-one knew how! That is a very dangerous

Re: [fpc-devel] Simplicity vs. Complexity

2019-03-26 Thread Joao Schuler
Dear Moreton, I think that you might have touched the most important question of all. I'll express my own professional opinion in regards to this (not wishing to convince others - just expressing my own). I've been thinking on this question for more than 20 years. If you own a company and your

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

2019-03-26 Thread Joost van der Sluis
On 3/25/19 6:24 PM, Bart wrote: On Mon, Mar 25, 2019 at 1:55 PM Joost van der Sluis wrote: That's correct. That's why it should be provided on the command-line. fpcmkcfg only shows the values of all defined macro's. For example, try 'fpcmkcfg -d foo=jojo -m'. As an end user howvere I do

[fpc-devel] Simplicity vs. Complexity

2019-03-26 Thread J. Gareth Moreton
This is a question regarding the compiler in general, and I sense there is no single correct answer. As you may already know, FPC compiles source code into intermediate nodes. Most of these are quite straightforward, like addition and a procedure call, but then you get quite a few that map

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

2019-03-26 Thread Sven Barth via fpc-devel
Ben Grasset schrieb am Di., 26. März 2019, 13:47: > On Tue, Mar 26, 2019 at 2:33 AM Sven Barth via fpc-devel < > fpc-devel@lists.freepascal.org> wrote: > >> Those paths are not handled relative to the compiler binary, they are >> handled relative to the current directory when calling the

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

2019-03-26 Thread Ben Grasset
On Tue, Mar 26, 2019 at 2:33 AM Sven Barth via fpc-devel < fpc-devel@lists.freepascal.org> wrote: > Those paths are not handled relative to the compiler binary, they are > handled relative to the current directory when calling the compiler. The > compiler does not differentiate whether a

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

2019-03-26 Thread Sven Barth via fpc-devel
Am 26.03.2019 um 01:08 schrieb Ben Grasset: On Mon, Mar 25, 2019 at 5:34 PM Ben Grasset > wrote: To be properly cross-platform, it should really generate something like "-Fu..\..\units\$fpctarget" I meant to say, "generate something like that specifically