At 21:39 13-8-2006, you wrote:
Hi,
This patch will enable the variable declaration in .fp files. It's
very easy if you have repeating sequences or you want to make pages
"configurable".
The patch should be applied on top of the 3rd patch I sent a few day's ago.
Thanks, applied 3rd and 4th p
Marco van de Voort wrote:
>> Dave Parsons wrote:
>> > Has there been any discussion/attempt to get away from GDB and
>> > integrate a native FPC solution? Using an external debugger
>> > doesn't seem ideal to me.
>>
>> It isn't ideal indeed. Creating a debugger requires some time, though.
>> You
>>
On 15 Aug 2006, at 14:21, Alexander Todorov wrote:
AFAIK gcc can compile code for some models microcontrollers(cpus for
embeded devices).
GCC, like FPC, can compile code for any cpu it has a code generator for.
I am not specialist in this area but know people who write software
for custom m
On 15 Aug 2006, at 14:12, Daniël Mantione wrote:
The problem is that if you use source code "for reference", your
source code
automatically gets tainted by the original one. To be clean you
would need
someone to write reference documentation based on the original
source code,
and other peo
> Not sure about the 'feature' you mention.
> Regards John
> > There is a feature with '-Rfp' option of 'cp' program: if you
> > enter path with "incorrect" slash (microsoft's '\' instead of
> > '/'), you get somewhat strange errors with all 'exampledirs='
> > in makefile.fpc (problem is in t
On Tue, 15 Aug 2006, Michael Van Canneyt wrote:
Could you be more clear ? I don't understand the question?
What is the relation with gcc ?
Michael.
AFAIK gcc can compile code for some models microcontrollers(cpus for
embeded devices).
I am not specialist in this area but know people who write
Thanks - we already spotted the fpcmem.dll (.exe) problem in daily win32
snapshot. Guess it'll be fixed quite soon. Not sure about the 'feature' you
mention.
Regards John
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of
> [EMAIL PROTECTED]
> Se
Op Tue, 15 Aug 2006, schreef Jonas Maebe:
>
> On 15 Aug 2006, at 13:29, Marco van de Voort wrote:
>
> > > On 15 Aug 2006, at 12:41, Jonas Maebe wrote:
> > >
> > > > Not only passing them on, but to re-license them under the GPL or
> > > > (modified) LGPL.
> > >
> > > Or pretty much any other
I didn't see anyone mention it, but the last revisions are not being made
correctly (WinXP-sp2, i386).
There is a problem in rtl\win32 with fpcmemdll.dll (make tries to treat it like
.exe).
There is a feature with '-Rfp' option of 'cp' program: if you enter path with
"incorrect" slash (microso
On 15 Aug 2006, at 13:29, Marco van de Voort wrote:
On 15 Aug 2006, at 12:41, Jonas Maebe wrote:
Not only passing them on, but to re-license them under the GPL or
(modified) LGPL.
Or pretty much any other Open Source/Free Software license for that
matter...
I was thinking more for referen
> On 15 Aug 2006, at 12:41, Jonas Maebe wrote:
>
> > Not only passing them on, but to re-license them under the GPL or
> > (modified) LGPL.
>
> Or pretty much any other Open Source/Free Software license for that
> matter...
I was thinking more for reference, and less for reuse.
_
On 15 Aug 2006, at 13:09, Peter Popov wrote:
Well, what I mean is that C++ Builder specifically specifies how
Delphi (Object Pascal) open array parameters should be viewed from C
++. If this is the current FPC standard this is good. On the other
hand FPC does not allow cdecl functions with
On 15 Aug 2006, at 12:41, Jonas Maebe wrote:
Not only passing them on, but to re-license them under the GPL or
(modified) LGPL.
Or pretty much any other Open Source/Free Software license for that
matter...
Jonas
___
fpc-devel maillist - fpc-
Tomas Hajny wrote:
The following alternatives would be possible:
1) FPC already has internal assembler and linker, but these don't support
the OS/2 target at the moment. Changing the assembler part to support
output of a.out object files wouldn't make much sense, so you'd basically
need to chang
Well, what I mean is that C++ Builder specifically specifies how Delphi
(Object Pascal) open array parameters should be viewed from C++. If this
is the current FPC standard this is good. On the other hand FPC does not
allow cdecl functions with open arrays (see
http://www.freepascal.org/man
On 15 Aug 2006, at 12:31, Marco van de Voort wrote:
Most of this was done via chat though, so some confirmation from
Alan that I
can pass the src on would be nice.
Not only passing them on, but to re-license them under the GPL or
(modified) LGPL.
Jonas
> Dave Parsons wrote:
> > Has there been any discussion/attempt to get away from GDB and
> > integrate a native FPC solution? Using an external debugger
> > doesn't seem ideal to me.
>
> It isn't ideal indeed. Creating a debugger requires some time, though. You
> need modules for reading the indiv
On Tue, 15 Aug 2006, Alexander Todorov wrote:
> Hello list,
> I found this and it may be interesting to some of you:
>
> http://jal.sourceforge.net/
>
> A Pascal like compiler for microcontrollers.
>
> It is a good thing to have in FPC like there is in gcc.
> What do you think?
Could you be
On Tue, 15 Aug 2006 09:55:42 +0200 (CEST), Marco van de Voort wrote:
> > I don't know yet whether it will be worth the effort, but it
> > looks as though it could be done if necessary.
>
> It isn't. I never saw the TP compilability of later 1.0.x versions
> confirmed, and even before 1.0 times, s
Dave Parsons wrote:
> On Mon, 14 Aug 2006 18:48:55 +0200 (CEST), Tomas Hajny wrote:
>> Dave Parsons wrote:
>> > On Mon, 14 Aug 2006 13:15:51 +0200 (CEST), Tomas Hajny wrote:
>> >> Dave Parsons wrote:
>> >> > On Sun, 13 Aug 2006 23:08:29 +0200, Tomas Hajny wrote:
.
.
>> 2) Function for accessing p
Hello list,
I found this and it may be interesting to some of you:
http://jal.sourceforge.net/
A Pascal like compiler for microcontrollers.
It is a good thing to have in FPC like there is in gcc.
What do you think?
___
fpc-devel maillist - fpc-devel
Marco van de Voort wrote:
>> I don't know yet whether it will be worth the effort, but it
>> looks as though it could be done if necessary.
>
> It isn't. I never saw the TP compilability of later 1.0.x versions
> confirmed, and even before 1.0 times, special care need to be taken (due
> to
> TP's m
On 15 Aug 2006, at 09:52, Dave Parsons wrote:
FPC on OS/2 is no problem since we already have an up-to-date
native version of FPC. Lazarus will require work.
VMS Pascal is a bit different from Turbo Pascal but it might
be possible even if I have to find an early FPC, bootstrap that
using VMS P
On 15 Aug 2006, at 09:13, Peter Popov wrote:
I have the following question: how are open array parameters
currently implemented in FPC? The reason I am asking is that I am
using DLL functions in C which rely on borland's syntax, that is,
void __cdecl SomeProc(const double *coords, const in
On Tue, 15 Aug 2006, Peter Popov wrote:
> Are you saying that a delphi open array is binary compatible to a FPC open
> array?
No-one has investigated this, as far as I know.
> Peter
>
> Voodoo or not, code should be binary compatible.
In order to work, yes.
But FPC code is not by definitio
Are you saying that a delphi open array is binary compatible to a FPC open
array?
Peter
Voodoo or not, code should be binary compatible.
On Tue, 15 Aug 2006 09:47:18 +0200, ik <[EMAIL PROTECTED]> wrote:
Hi,
You should use
PDouble = ^Double;
procedure SomeProc2(const coords: PDouble; const
Marco van de Voort wrote:
I don't know yet whether it will be worth the effort, but it
looks as though it could be done if necessary.
It isn't. I never saw the TP compilability of later 1.0.x versions
confirmed, and even before 1.0 times, special care need to be taken (due to
TP's memory restra
> I don't know yet whether it will be worth the effort, but it
> looks as though it could be done if necessary.
It isn't. I never saw the TP compilability of later 1.0.x versions
confirmed, and even before 1.0 times, special care need to be taken (due to
TP's memory restraints).
But more importan
Hmm, to the list this time.
On Mon, 14 Aug 2006 21:57:18 +0200, Jonas Maebe wrote:
> On 14 Aug 2006, at 18:28, Dave Parsons wrote:
>
> > Well, it should be possible then but are you really saying that the
> > original FPC was all written in assembler?
>
> No, the original FPC was written in Tu
Op Tue, 15 Aug 2006, schreef Dave Parsons:
> Has there been any discussion/attempt to get away from GDB and
> integrate a native FPC solution? Using an external debugger
> doesn't seem ideal to me.
We made the conclusion that we need our own debugger already a few years
ago. But making the con
Hi,
You should use
PDouble = ^Double;
procedure SomeProc2(const coords: PDouble; const high: Integer); cdecl;
The reason is simple, it's equal to C's code...
Open arrays are voodoo magic, specially for C\++ compilers..
Ido
On 8/15/06, Peter Popov <[EMAIL PROTECTED]> wrote:
Hi
I have the foll
Hi
I have the following question: how are open array parameters currently
implemented in FPC? The reason I am asking is that I am using DLL
functions in C which rely on borland's syntax, that is,
void __cdecl SomeProc(const double *coords, const int high) (in
C++ Builder)
is equivallet t
On Tue, 15 Aug 2006 08:29:17 +0200 (CEST), Tomas Hajny wrote:
> Dave Parsons wrote:
...
> > Well, it should be possible then but are you really saying that the
> > original FPC was all written in assembler?
>
> No, but FPC can generate assembler code from Pascal sources, and
> assembling and link
On Mon, 14 Aug 2006 18:48:55 +0200 (CEST), Tomas Hajny wrote:
> Dave Parsons wrote:
> > On Mon, 14 Aug 2006 13:15:51 +0200 (CEST), Tomas Hajny wrote:
> >> Dave Parsons wrote:
> >> > On Sun, 13 Aug 2006 23:08:29 +0200, Tomas Hajny wrote:
> .
> .
> > To help me, I would like to know for instance h
34 matches
Mail list logo
