Oh, is that so? What about defining CREATE_SMART and LINK_SMART?
Jonas Maebe-2 wrote:
On 21 Aug 2010, at 08:59, leledumbo wrote:
I want to build a smartlinked (stripped and optimized as well) version of
fpc
for win64 from win32, so I call:
make all smart STRIP=1 OPTIMIZE=1
In our previous episode, Frank Church said:
I did this kind of thing some time ago, but have forgotten the details.
Let us say you have something like TBaseType(Variable).Method, you want to
let TBaseType be a variable so you can have some code like this.
procedure (value:someType)
var
On 24 Aug 2010, at 08:09, leledumbo wrote:
Oh, is that so? What about defining CREATE_SMART and LINK_SMART?
Adding OPT=-CX -XX will force smartlinking all binaries.
Jonas
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
Date: Mon, 23 Aug 2010 13:57:30 -0300
From: Andreas Berger andr...@thebergerclan.org
Subject: Re: [fpc-pascal] ARM-Cortex port
To: FPC-Pascal users discussions fpc-pascal@lists.freepascal.org
Message-ID: 4c72a87a.7020...@thebergerclan.org
Content-Type: text/plain; charset=ISO-8859-1;
Hi,
On Tue, 24 Aug 2010 10:53:55 +0100, Geoffrey Barton m...@periphon.net
wrote:
Date: Mon, 23 Aug 2010 13:57:30 -0300
Thanks Jonas and Jeppe for your answers. I will probably wait then to
switch (or try to convince the company to use an ARM-9)
using Jonas and Jeppe's answers to my idiot
Am 24.08.2010 11:53, schrieb Geoffrey Barton:
using Jonas and Jeppe's answers to my idiot questions in this forum, and
Jeppe's startup code for the STM32F, I have FPC cross-compiling for the
LM3S9B92, one of the TI Luminary processors.
If you've any reusable startup code, we would be happy
Hi!
At time I'm playing around with fcl-passrc to automate some actions I have
to perform with the source code.
Unfortunately, FCL-PASSRC does not process the source of a library:
Expected unit at token library
(In ParseSource() call)
How do I make FCL-PASSRC process the lib source code too?
Trying to compile the following code (porting from MW Pascal)
type
myObject = object
procA (x: integer);
procC (procedure procD (var
y: myObject));
end;
procedure myObject. procC (procedure procD (var
y: myObject));
On 24 August 2010 18:29, Matthias Klumpp wrote:
(In ParseSource() call)
How do I make FCL-PASSRC process the lib source code too?
It's not implemented yet - just like fcl-passrc can't parse Program
units either. Based on what I found while looking what to implement
for Program unit parsing,
On 24 Aug 2010, at 19:29, fpanas...@tiscali.it wrote:
Trying to compile the following code (porting from MW Pascal)
[snip]
It's fixed. When reporting problems in the future, please include full source
code instead of only snippets.
Jonas
___
Trying to compile the following code (porting from MW Pascal)
procC (procedure procD (var y: myObject));
the compiler is complaining because the ProcB is a nested procedure of
ProcA.
Try defining it outside the object, if possible.
If not, define it as an object method(*)
I
On 24 Aug 2010, at 22:38, Alberto Narduzzi wrote:
Trying to compile the following code (porting from MW Pascal)
procC (procedure procD (var y: myObject));
the compiler is complaining because the ProcB is a nested procedure of ProcA.
No. He's using MacPas mode in FPC 2.5.1. In
Jonas,
No. He's using MacPas mode in FPC 2.5.1. In that mode, nested procedural
variables are supported (and also in ISO mode, and also in all other syntax
modes if you add {$modeswitch nestedprocvars}). The error message was caused by
a compiler bug.
This declares a regular procvar, while
13 matches
Mail list logo
