On Mon, 13 Nov 2006, Nightrider wrote:
> I'm trying my first compilation under mandriva 2006 and receive a message I
> can solve, may someone you help me?
>
> See snapshot below:
>
>
> [EMAIL PROTECTED] prog_apoio]$ fpc geratestadoresintegridadereferencial
> Free Pascal Compiler version 2.0.4
Adrian Maier ha scritto:
Hello,
I am trying to write a program that is embedding the python interpreter
in order to execute python code. I don't need to transfer values between
pascal and python.
you welcome!
If you are using Lazarus on Windows, I can send you the core units of
Python for D
I'm trying my first compilation under mandriva 2006 and receive a message I can solve, may someone you help me? See snapshot below:[EMAIL PROTECTED] prog_apoio]$ fpc geratestadoresintegridadereferencial
Free Pascal Compiler version 2.0.4 [2006/08/20] for i386Copyright (c) 1993-2006 by Florian Klaem
On 11/14/06, Tiziano_mk <[EMAIL PROTECTED]> wrote:
Adrian Maier ha scritto:
> Hello,
>
> I am trying to write a program that is embedding the python interpreter
> in order to execute python code. I don't need to transfer values between
> pascal and python.
>
you welcome!
If you are using Lazaru
Hello,
I have a quick question: are there (m)any people here who store/load
sets to/from files?
The reason is that we are considering to change the internal format
of sets in FPC on big endian machines. The reason is that this would
be necessary to allow byte-packing of sets (so that e.g.
Adrian Maier ha scritto:
On 11/14/06, Tiziano_mk <[EMAIL PROTECTED]> wrote:
Adrian Maier ha scritto:
I (on windows) and my friend (on Linux) are actually working in order to
make some experiment and documentation about this matter. If you could
partecipate and help...
It's good to know abo
On 14 nov 2006, at 13:15, Tom Verhoeff wrote:
For purposes of converting between one representation and the other,
it might be nice to provide a means to declare "old"sets, which use
the
current representation, _alongside_ the new sets, which use the
improved
representation. Then it would
> On 14 nov 2006, at 12:32, Ewald Horn wrote:
>
> > is it possible to keep a legacy reader in place ? That way it'll be
> > easy to read old data and convert it to the new format and have
> > little impact on historic data. If you happen to work on a big
> > endian machine you could then do
On Tue, Nov 14, 2006 at 11:47:37AM +0100, Jonas Maebe wrote:
>
> I have a quick question: are there (m)any people here who store/load
> sets to/from files?
I do not mix sets and files, but I do mix sets and Single/Double
in a record to decompose floating point numbers.
However, I don't see a b
Hi,
I have a Symbol mobile device with an integrated barcode scanner.
The scanner's API in C and I cannot use every API calls.
An example: The problem appears in the
ScanBuffer:=SCAN_AllocateBuffer(TRUE,dwScanSize);
line (see the test app below).
If I run in GDB the error message is:
warning:
Many thanks Felipe, the problem is the exported name(s).
The exported names is SCAN_AllocateBuffer_A and SCAN_AllocateBuffer_W.
Thanks again!
Gabor
Felipe Monteiro de Carvalho írta:
Can you show us the c declaration of the function you are calling? It
should be on a .h file.
Also, you should
Hi,
is it possible to keep a legacy reader in place ? That way it'll be easy to
read old data and convert it to the new format and have little impact on
historic data. If you happen to work on a big endian machine you could then
do a once-off conversion.
Kind regards
Ewald Horn
On 14 nov 2006, at 12:32, Ewald Horn wrote:
is it possible to keep a legacy reader in place ? That way it'll be
easy to read old data and convert it to the new format and have
little impact on historic data. If you happen to work on a big
endian machine you could then do a once-off convers
On 14 nov 2006, at 13:31, Vincent Snijders wrote:
A set of 0..63 requires 64 bits, doesn't it?
Yes, my mistake.
Jonas
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Can you show us the c declaration of the function you are calling? It
should be on a .h file.
Also, you should put an way to verify if the calls are working, like:
DLL_Handle:=LoadLibrary('SCNAPI32.DLL');
if DLL_Handle = nil then raise EException.Create('Could not load library');
Poin
On 14 nov 2006, at 13:20, Marco van de Voort wrote:
is it possible to keep a legacy reader in place ? That way it'll be
easy to read old data and convert it to the new format and have
little impact on historic data. If you happen to work on a big
endian machine you could then do a once-off conv
On Tue, 14 Nov 2006, Gabor Boros wrote:
> Hi,
>
> I have a Symbol mobile device with an integrated barcode scanner.
> The scanner's API in C and I cannot use every API calls.
>
> An example: The problem appears in the
> ScanBuffer:=SCAN_AllocateBuffer(TRUE,dwScanSize);
> line (see the test app
> On 14 nov 2006, at 13:20, Marco van de Voort wrote:
>
> >>> is it possible to keep a legacy reader in place ? That way it'll be
> >>> easy to read old data and convert it to the new format and have
> >>> little impact on historic data. If you happen to work on a big
> >>> endian machine you coul
Another question, do you intend to fix the other size problem too? (another
Delphi incompatability)
I mean by this sets of x..y having a size of roundup((y-z+1)/8) with z as
x rounded down to the lower multiple of 8.
IOW, a set of 79..83 is two bytes in delphi.
___
Marco van de Voort schrieb:
> Another question, do you intend to fix the other size problem too? (another
> Delphi incompatability)
>
> I mean by this sets of x..y having a size of roundup((y-z+1)/8) with z as
> x rounded down to the lower multiple of 8.
>
> IOW, a set of 79..83 is two bytes i
Jonas Maebe schreef:
Hello,
sets in FPC on big endian machines. The reason is that this would be
necessary to allow byte-packing of sets (so that e.g. a set of 0..63
would only occupy 1 byte as opposed to 4 like is currently the case).
A set of 0..63 requires 64 bits, doesn't it? So it woul
On Tuesday 14 November 2006 11:47, Jonas Maebe wrote:
> Hello,
>
> I have a quick question: are there (m)any people here who store/load
> sets to/from files?
It would be nice to have an option like
{$MINENUMSIZE xxx}
so that binary compatibility with frequently used
bitmasks in C APIs is easier
Hi,
the c long int type is always mapped to longint in h2pas
but I guess this is not correct in linux (have no 64 bit to verify)
If I am correct:
linux64: c long int -> pascal int64
win64 : c long int -> pascal longint
What is the size of long on the Mac Os X platform ?
Is there a pascal inte
On 14 Nov 2006, at 22:22, Den Jean wrote:
Is there a pascal integer type defined somewhere in rtl
that allows me to map to this c-type sometimes
used in api's ?
There's a unit called ctypes in the rtl with all these types defined
(prefixed by "c", i.e. cshort, cchar, clong, ...)
Jonas
__
On 14 Nov 2006, at 22:04, Den Jean wrote:
so that binary compatibility with frequently used
bitmasks in C APIs is easier
Aren't bitpacked records/arrays more appropriate for that?
Jonas
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
h
On Tuesday 14 November 2006 22:28, Jonas Maebe wrote:
> There's a unit called ctypes in the rtl with all these types defined
> (prefixed by "c", i.e. cshort, cchar, clong, ...)
>
thx,
I do not see the win64 exception in the defines ??
regards,
Den Jean
_
Op Tue, 14 Nov 2006, schreef Jonas Maebe:
>
> On 14 Nov 2006, at 22:04, Den Jean wrote:
>
> > so that binary compatibility with frequently used
> > bitmasks in C APIs is easier
>
> Aren't bitpacked records/arrays more appropriate for that?
Semantically speaking, no.
Daniël__
On 14 Nov 2006, at 23:12, Daniël Mantione wrote:
Op Tue, 14 Nov 2006, schreef Jonas Maebe:
On 14 Nov 2006, at 22:04, Den Jean wrote:
so that binary compatibility with frequently used
bitmasks in C APIs is easier
Aren't bitpacked records/arrays more appropriate for that?
Semantically spe
Den Jean schrieb:
> On Tuesday 14 November 2006 22:28, Jonas Maebe wrote:
>
>> There's a unit called ctypes in the rtl with all these types defined
>> (prefixed by "c", i.e. cshort, cchar, clong, ...)
>>
>
> thx,
>
> I do not see the win64 exception in the defines ??
Win64 has no such exception
29 matches
Mail list logo
