the .ppu/ppw files are the interface parts of the unit in a compiled form,
while the .o/ow files are the implementation part of an unit or a program in
it's compiled form. Those files (.o/.ow) are needed to perform the linking
of the app.
Once you've compiled the compiler you don't need them. Howe
I'm trying to use the unit getopts, but something goes wrong.
In a program I get extrange results if I insert a non-option between two
options. In the example program of the unit:
next is ok.
testopt --verbose --add me --delete you
Long option : verbose
Long option : add With value : me
Long opti
The .ppu are compiled units. You probably want to keep them hanging
around, but it's not neccessary. If you delete them, the compiler
simply needs to re-compile all the units each time you compile. If
you leave them, I think it will only compile the changed units and
the main program.
I think
> Question 1:
> Will such code result in memory corruption somewhere in both the
> cases where runtime range checking is enabled and the one where
> it is not enabled?
No memory corruption. The length of the array is passed to the helper routine
>
> Question 2:
> Is this something that needs to b
> Upon compiling the freepascal compiler from cvs, I noticed a lot of
> .o and .ppu files generated in addition to the final executable.
> What is the difference between .o and .ppu files and can I delete them
> both to eliminate the clutter?
.ppu contains information for the compiler
.o contains
Apparently, activating -Cr is needed to enable enforcement of
compile time constant range checking as well.
The ff. program:
program blah;
var
E: array[2..4] of Integer;
begin
E[10]:=15;
end.
will compile albeit with a warning. Only when -Cr is enabled
will the range violation become an error
Upon compiling the freepascal compiler from cvs, I noticed a lot of
.o and .ppu files generated in addition to the final executable.
What is the difference between .o and .ppu files and can I delete them
both to eliminate the clutter?
___
fpc-pascal mai
