Tony Pelton wrote:
hi all,
i wanted to ask a question, before i spend time going down a road to
implement it.
are there any know limits on how big a source file can be for the FPC compiler ?
i was thinking about experimenting with "code generating" a source
file that would become a memory resi
On 1/5/06, L505 <[EMAIL PROTECTED]> wrote:
>
> > are there any know limits on how big a source file can be for the FPC
> > compiler ?
>
> interesting question... hmm did you try a 3GB file which calls
> writeln('test') over
> and over and over again?
> That's the stupid way of doing tests - the
> are there any know limits on how big a source file can be for the FPC
> compiler ?
interesting question... hmm did you try a 3GB file which calls writeln('test')
over
and over and over again? That's the stupid way of doing tests - the smart way
would
be waiting for an answer from the FPC
hi all,
i wanted to ask a question, before i spend time going down a road to
implement it.
are there any know limits on how big a source file can be for the FPC compiler ?
i was thinking about experimenting with "code generating" a source
file that would become a memory resident database of sort
> i learned a few things from here:
>
> http://velthuis.homepage.t-online.de/articles/articles-pchars.html
> http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_howto5
>
I have seen Rudy's article too, and am reading the other website now, though.
I'm at the point where I feel 100 percent confi
Jonas Maebe wrote:
On 04 Jan 2006, at 21:51, Hans Mårtensson wrote:
The type of pBoxtemplate is ^word.
Is it not true that
(dword(pBoxtemplate) and 1)=1
evaluates to TRUE, if and only if pBoxtemplate is NOT aligned to a
word boundary (16 bit boundary)?
And then, assuming pBoxtemplate is
On 04 Jan 2006, at 21:51, Hans Mårtensson wrote:
Does PPC 2.0.2 handle alignment of data the same way as former
versions?
The statements below have nothing to do with alignment.
The type of pBoxtemplate is ^word.
Is it not true that
(dword(pBoxtemplate) and 1)=1
evaluates to TRUE, if and
Jonas Maebe wrote:
On 04 Jan 2006, at 17:51, Hans Mårtensson wrote:
Does PPC 2.0.2 handle alignment of data the same way as former
versions?
The statements below have nothing to do with alignment.
Will the statements (the conditions)
if (dword(pBoxtemplate) and 1)=1 then pBoxtemplate:=
On 04 Jan 2006, at 17:51, Hans Mårtensson wrote:
Does PPC 2.0.2 handle alignment of data the same way as former
versions?
The statements below have nothing to do with alignment.
Will the statements (the conditions)
if (dword(pBoxtemplate) and 1)=1 then pBoxtemplate:=nil;
I can only thin
On 04 Jan 2006, at 18:25, Mattias Gaertner wrote:
How can I see, how fpc calls the linker under MacOSX?
Compile with -s and check ppas.sh and link.res. There are still
various 255 char limits in fpc regarding command line arguments
passed to the assembler and linker.
Jonas
I run into some strange linker errors. Shorten the paths fixed the problem.
The application has the following linker options:
-k-framework -kcarbon -k-framework -kAGL
And the output file was
-o/Users/Username/pascal/carbon/agl/carboncustomcontrol.app/Contents/MacOS/
TestProgram
Granted, it is n
Hans Mĺrtensson wrote:
.
.
> Does PPC 2.0.2 handle alignment of data the same way as former versions?
.
.
Actually, I don't think so - I believe the default alignment might have
changed from 2 to 4 (at least this seems to be indicated by my simple
test). You can check this easily for pBoxtempl
Jonas Maebe wrote:
They should be.
Thank you for your careful answer. I will return later if I am able
to make a simple sample program that can reproduce the problem.
(Or may be I should stick to 1.0.10 that worked for me)
It would be nice if you could provide the sample program (and subm
Hi
I am programming to an embedded ARM platform and my question
is, is it possible to force constants to stay in the code segment
(constant strings etc.) In C you can do this using "static".
It looks as all string constants are placed in the data segment, and all
variables are placed in the bss
On 03 Jan 2006, at 23:58, Alain Michaud wrote:
plPlotterParams * pl_newplparams (void)
The function "pl_newplparams" is supposed create a structure (record)
and then return some "pointer" to it. The user is not supposed to
access
this data directly, so there is NO reference to "plPlotterPara
15 matches
Mail list logo
