Mehmet Erol Sanliturk wrote:
(E)
When
c:\fpc\2.2.2\examples\gtk2\gtk_demo\gtk_demo.exe
is started , it is giving the following exception message
and then closing :
--
An unhandled exception occurred at $66E9433E :
EDivByZero : Division by zero
$66E9433E
$66E94B30
Dear Sirs ,
The examples within the following directories
could be compiled with their Makefile use .
c:\fpc\2.2.2\examples\gtk1\
c:\fpc\2.2.2\examples\gtk2\
(A)
During execution of programs some DLL files
are requested which none of them found in
either FPC directories or in other Window
Hello Graeme,
Thursday, September 25, 2008, 9:50:04 PM, you wrote:
GG> Yes I know we have had lengthy discussions about this before.
GG> Everybody (whoever they might be) keeps saying that UTF-16 was chosen
GG> for Tiburon's UnicodeString because it makes "significant speed gains"
GG> when callin
Graeme Geldenhuys schrieb:
Hi,
Yes I know we have had lengthy discussions about this before.
Everybody (whoever they might be) keeps saying that UTF-16 was chosen
for Tiburon's UnicodeString because it makes "significant speed gains"
when calling the Windows API based on UTF-16 - compared to the
On Thu, Sep 25, 2008 at 9:50 PM, Graeme Geldenhuys
<[EMAIL PROTECTED]> wrote:
> Marco Cantu, as far as I can see, is the only one that shows a
> comparison and numbers. Surprisingly, the ANSI calls where faster!
Maybe it's due to such reasons that the Delphi EULA forbids posting
benchmarks? Lucki
Hi,
Yes I know we have had lengthy discussions about this before.
Everybody (whoever they might be) keeps saying that UTF-16 was chosen
for Tiburon's UnicodeString because it makes "significant speed gains"
when calling the Windows API based on UTF-16 - compared to the ANSI
API's. The whole debate