In our previous episode, John Lee said:
> You are making it sound v complicated - but the settings eg for the main
> program eg might be -O3 or -O2 or something are meaningful - most people
> don't mess with them anyway. I feel sure that I've seen somewhere how to
> get them into compiler string, b
Am 08.01.2014 22:16 schrieb "John Lee" :
>
> You are making it sound v complicated - but the settings eg for the main
program eg might be -O3 or -O2 or something are meaningful - most people
don't mess with them anyway. I feel sure that I've seen somewhere how to
get them into compiler string, but
You are making it sound v complicated - but the settings eg for the main
program eg might be -O3 or -O2 or something are meaningful - most people
don't mess with them anyway. I feel sure that I've seen somewhere how to
get them into compiler string, but can't remember how!
J
On 8 January 2014 18
Am 08.01.2014 14:21 schrieb "John Lee" :
>
> In Pascal programmers guide v2.6 Feb 2013 it explains how to use {$I ...
} to include compiler information eg version string, time string etc so one
can include eg in a writeln, but it does not mention not the optimisation
level at which program was com
.org] De la part de John Lee
> > Envoyé : mercredi 8 janvier 2014 14:21
> > À : FPC developers' list
> > Objet : [fpc-devel] programmers guide 2.6 issue
> >
> > In Pascal programmers guide v2.6 Feb 2013 it explains how to use {$I
> > ... } to include compiler info
FPC developers' list
> Objet : [fpc-devel] programmers guide 2.6 issue
>
> In Pascal programmers guide v2.6 Feb 2013 it explains how to use {$I
> ... } to include compiler information eg version string, time string
> etc so one can include eg in a writeln, but it does not menti
In Pascal programmers guide v2.6 Feb 2013 it explains how to use {$I ... }
to include compiler information eg version string, time string etc so one
can include eg in a writeln, but it does not mention not the optimisation
level at which program was compiled.
Is this an omission or is this info e
