[fpc-devel] Feature announcement: Record management operators
Sven Barth
pascaldragon at googlemail.com
Mon Mar 21 18:54:42 CET 2016
On 21.03.2016 15:21, Maciej Izak wrote:
> 2016-03-21 15:08 GMT+01:00 Michael Van Canneyt <michael at freepascal.org
> <mailto:michael at freepascal.org>>:
>
> No need for that.
>
> You just need to {$IFNDEF VER3_0} all record operators code.
>
> A make cycle compiles 3 times.
>
> During a make cycle you must start with 3.0.0, this will compile the RTL
> with 3.0.0 and this excludes record operators.
>
> During the second compile, it will be with the latest compiler, so
> VER3_1_1,
> which will include the record operators code, and all will be well.
>
>
> Sounds perfect!
>
> @Michael, @Sven: now I know why compiler_cycle was problematic for my
> branch :)
When you add a new feature as a first step it's recommended to do a
"make cycle" in the compiler directory. This way you know that cycling
the compiler (starting with the last release and coming to the trunk
one) works. If you changed something in code generation then a "make
fullcycle" is advisable as well as that builds the compiler once for
each supported architecture. And then "make all" at the top level is the
next big step with the final one being a testsuite run with a comparison
of the results.
Regards,
Sven
More information about the fpc-devel
mailing list