ok, thanks for your response.
But I believed that the Widestring manager, are routines that are included in
the compiled program. But you mention that there is an "OS widestring manager".
I'm confused, how many widestring manager exist?.
For example, when I write this statement:
Writeln ('прив
Jonas wrote:
> It's probably caused by r14184, which was in response to
> http://bugs.freepascal.org/view.php?id=14958
> The problem is probably that the lib's exit code is called both when the
> library is unloaded
> (in which case you don't want the process to terminate) and when the
> "libra
On 10 Sep 2010, at 20:21, Luis Fernando Del Aguila Mejía wrote:
> In the following program:
>
> {$ Codepage UTF8}
> var str: string;
> Begin
> Readln (str);
> Writeln (str)
> End.
>
> When I enter the following: €uro, shows me: ?uro.
> The console uses 850 and S.O. 1252, for non-Unicode program
On 10 Sep 2010, at 18:58, Seth Grover wrote:
> It seems the cause of this is that halt, which calls InternalExit and
> System_exit, which in turn calls haltproc, does not actually halt the
> program in the case of a library. Instead, haltproc for the library
> just calls InternalExit again and re
Dear list
Can someone summarize the status of COM / OLE in Windows using recent
versions of freepascal? As far as I got: COM clients are possible
since 2.4.0. You can use them for i.e. Office automatisation. It
works. But what about COM servers?
Is programming i.e. Office possible without using D
In the following program:
{$ Codepage UTF8}
var str: string;
Begin
Readln (str);
Writeln (str)
End.
When I enter the following: €uro, shows me: ?uro.
The console uses 850 and S.O. 1252, for non-Unicode programs.
My question is:
Who puts the question mark?
The widestring manager or my console.
Greetings! An interesting problem I've run into:
Under Linux, I have a small example program written in C (we'll call
it cprog) which uses a FPC-compiled shared object library
(libfpcso1.so) inside which I want to catch access violations in
try/except blocks. I don't care about access violations i
I would recommend listing it here:
http://wiki.lazarus.freepascal.org/Components_and_Code_examples#Packages_for_FPC.2FLazarus_.28not_hosted_here.29
thanks,
--
Felipe Monteiro de Carvalho
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http:
With tests and documentation. Requires trunk FPC.
Download: http://code.google.com/p/fprb/
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
On 10 September 2010 10:38, Henry Vermaak wrote:
>
> You should use the ctypes here, since they'll change for 64 bit.
Thanks Henry, that was indeed the problem.
--
Regards,
- Graeme -
___
fpGUI - a cross-platform Free Pascal GUI toolkit
http://ope
On 10 September 2010 10:18, Marco van de Voort wrote:
>
> You are not passing unix types, and are passing pointers to 32-bit types to
> parametesr that expect pointers to 64-bit types (pculong).
Oops! Thanks Marco, changing them to ctypes solved the problem. I
better double check my other X11 cod
On 10 September 2010 09:08, Graeme Geldenhuys wrote:
> Hi,
>
> I'm having trouble fetching the XdndTypeList data. It works 100% on my
> 32-bit Linux laptop, but now trying on my 64-bit Linux desktop at
> work, the XGetWindowProperty() call under 64-bit linux for the
> XdndTypeList always returns c
In our previous episode, Graeme Geldenhuys said:
> I'm having trouble fetching the XdndTypeList data. It works 100% on my
> 32-bit Linux laptop, but now trying on my 64-bit Linux desktop at
> work, the XGetWindowProperty() call under 64-bit linux for the
> XdndTypeList always returns count = 0, whe
Hi,
I'm having trouble fetching the XdndTypeList data. It works 100% on my
32-bit Linux laptop, but now trying on my 64-bit Linux desktop at
work, the XGetWindowProperty() call under 64-bit linux for the
XdndTypeList always returns count = 0, when in fact it should be 8, as
my last section of the
Am 09.09.10 15:45, schrieb Jonas Maebe:
On 09 Sep 2010, at 15:31, Mark Morgan Lloyd wrote:
I've just had my attention drawn to this elsewhere, and thought it
would be of general interest.
"In particular, we are relaxing all restrictions on the development
tools used to create iOS apps, as lon
15 matches
Mail list logo
