Re: [fpc-pascal] Getting fast output

2008-07-22 Thread Jonas Maebe
On 22 Jul 2008, at 06:29, leledumbo wrote: Peter Vreman wrote: http://www.freepascal.org/docs-html/rtl/system/settextbuf.html http://www.freepascal.org/docs-html/rtl/system/settextbuf.html Oh, yeah! I forgot to mention this. But declaring the buffer will eat spaces ,for instance: ... var

[fpc-pascal] Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

2008-07-22 Thread Roland Turcan
Hello FPC-Pascal users discussions! Compilation shows me next ugly error messages during building lazarus with our components. How can I turn on move verbose outputs to see more about the problem. The strangest is, the same source code is buildable into Lazarus/Linux without any problem, but

Re: [fpc-pascal] Getting fast output

2008-07-22 Thread Marco van de Voort
Peter Vreman wrote: http://www.freepascal.org/docs-html/rtl/system/settextbuf.html http://www.freepascal.org/docs-html/rtl/system/settextbuf.html Oh, yeah! I forgot to mention this. But declaring the buffer will eat spaces ,for instance: ... var Buf: array [0..65535] of Byte;

Re: [fpc-pascal] Getting fast output

2008-07-22 Thread Vincent Snijders
Marco van de Voort schreef: will add 64k to the executable because it's allocated on the stack. Huh? A filebuffer variable must be available always, so it is a global variable. I thought the file buffer variable must available for the time a file is opened and can be discarded after the

Re: [fpc-pascal] Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

2008-07-22 Thread Mattias Gaertner
On Tue, 22 Jul 2008 11:02:40 +0200 Roland Turcan [EMAIL PROTECTED] wrote: Hello FPC-Pascal users discussions! Compilation shows me next ugly error messages during building lazarus with our components. How can I turn on move verbose outputs to see more about the problem. The strangest

Re: [fpc-pascal] Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

2008-07-22 Thread Vincent Snijders
Roland Turcan schreef: Hello FPC-Pascal users discussions! Compilation shows me next ugly error messages during building lazarus with our components. How can I turn on move verbose outputs to see more about the problem. The strangest is, the same source code is buildable into Lazarus/Linux

Re: [fpc-pascal] Getting fast output

2008-07-22 Thread Marco van de Voort
Marco van de Voort schreef: will add 64k to the executable because it's allocated on the stack. Huh? A filebuffer variable must be available always, so it is a global variable. I thought the file buffer variable must available for the time a file is opened and can be discarded

Re: [fpc-pascal] Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

2008-07-22 Thread Mattias Gaertner
On Tue, 22 Jul 2008 11:33:30 +0200 Vincent Snijders [EMAIL PROTECTED] wrote: Roland Turcan schreef: Hello FPC-Pascal users discussions! Compilation shows me next ugly error messages during building lazarus with our components. How can I turn on move verbose outputs to see more

Re: [fpc-pascal] Getting fast output

2008-07-22 Thread Jonas Maebe
On 22 Jul 2008, at 08:06, Jonas Maebe wrote: On 22 Jul 2008, at 06:29, leledumbo wrote: Peter Vreman wrote: http://www.freepascal.org/docs-html/rtl/system/settextbuf.html http://www.freepascal.org/docs-html/rtl/system/settextbuf.html Oh, yeah! I forgot to mention this. But declaring the

Re: [fpc-pascal] Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

2008-07-22 Thread Jonas Maebe
On 22 Jul 2008, at 11:13, Mattias Gaertner wrote: The Lineinfo unit does not work currently under Mac OS X. The lineinfo unit does work under Mac OS X (but only for stabs currently). Depending on the used system version, it may also only work if you start the program with the full path,

Re: [fpc-pascal] Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

2008-07-22 Thread Mattias Gärtner
Zitat von Jonas Maebe [EMAIL PROTECTED]: On 22 Jul 2008, at 11:13, Mattias Gaertner wrote: The Lineinfo unit does not work currently under Mac OS X. The lineinfo unit does work under Mac OS X (but only for stabs currently). Ah. This means: either lineinfo and a lot of linker warnings on

Re: [fpc-pascal] Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

2008-07-22 Thread Jonas Maebe
On 22 Jul 2008, at 12:43, Mattias Gärtner wrote: This means: either lineinfo and a lot of linker warnings on each compile XOR no lineinfo and no warnings, right? If you don't use the patched linker, yes. dwarf is the future, isn't it? What is needed to get lineinfo working with dwarf?

Re[2]: [fpc-pascal] Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

2008-07-22 Thread Roland Turcan
Hello all, Backtrace from lazbuild: An unhandled exception occurred at $00148A30 : Breakpoint 1, 0x00018090 in fpc_raiseexception () (gdb) bt #0 0x00018090 in fpc_raiseexception () #1 0x001106d4 in CHECKFORURGENTMESSAGES (P=1, parentfp=0xbfffe0c0) at outputfilter.pas:561 #2 0x0010e400 in

[fpc-pascal] EOLESysError calling CreateOLEObject

2008-07-22 Thread Felipe Monteiro de Carvalho
Hello, I created a very simple program to create a shortcut in the desktop, but it crashes with EOLESysError (nothing else in the error message). I tryed to google, but it didn't show much. Am I missing some kind of initialization call that should be made? thanks, here is the full program. {

Re: [fpc-pascal] EOLESysError calling CreateOLEObject

2008-07-22 Thread Marco van de Voort
I created a very simple program to create a shortcut in the desktop, but it crashes with EOLESysError (nothing else in the error message). I tryed to google, but it didn't show much. Am I missing some kind of initialization call that should be made? thanks, here is the full program. I'm no

Re: Re[2]: [fpc-pascal] Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

2008-07-22 Thread Jonas Maebe
On 22 Jul 2008, at 13:29, Roland Turcan wrote: I wanted to make the backtrace from lazarus too, but when I run lazarus from terminal then terminal's menu is shown instead of lazarus' one. If you use gdb lazarus.app it should work fine. Jonas

Re: [fpc-pascal] EOLESysError calling CreateOLEObject

2008-07-22 Thread Felipe Monteiro de Carvalho
Thanks, but it didn't solve it. The same code (+coinitialize) works in Delphi 5. Maybe it's the dispinterfaces problem in fpc? Is it expected to work in 2.2.2 or in 2.3.1? thanks, -- Felipe Monteiro de Carvalho ___ fpc-pascal maillist -

Re: Re[2]: [fpc-pascal] Ugly exception during compilation FPC 2.3.1 MacOS X 10.5 PowerPC

2008-07-22 Thread Mattias Gärtner
Zitat von Roland Turcan [EMAIL PROTECTED]: Hello all, Backtrace from lazbuild: An unhandled exception occurred at $00148A30 : Breakpoint 1, 0x00018090 in fpc_raiseexception () (gdb) bt #0 0x00018090 in fpc_raiseexception () #1 0x001106d4 in CHECKFORURGENTMESSAGES (P=1,

Re: [fpc-pascal] EOLESysError calling CreateOLEObject

2008-07-22 Thread Marco van de Voort
Thanks, but it didn't solve it. The same code (+coinitialize) works in Delphi 5. Maybe it's the dispinterfaces problem in fpc? Is it expected to work in 2.2.2 or in 2.3.1? I suspect it is in the classid. (the clsid_ constant). Apparantly when I converted the headers, I thought there only was

Re: [fpc-pascal] EOLESysError calling CreateOLEObject

2008-07-22 Thread Marco van de Voort
DEFINE_SHLGUID(CLSID_ShellLink, 0x00021401L, 0, 0); // 00021401---C000-0046 while the iid starts with 000214EE Fixed, added some more clsid constants in the process r11434 ___ fpc-pascal maillist -

Re: [fpc-pascal] EOLESysError calling CreateOLEObject

2008-07-22 Thread Inoussa OUEDRAOGO
Apparantly when I converted the headers, I thought there only was one ID. However it seems that classids, and the ids in interfaces are different. I don't know enough from com to understand the difference, classids are used to identify implementation objects, while iid identify interfaces as

Re: [fpc-pascal] EOLESysError calling CreateOLEObject

2008-07-22 Thread Marco van de Voort
Apparantly when I converted the headers, I thought there only was one ID. However it seems that classids, and the ids in interfaces are different. I don't know enough from com to understand the difference, classids are used to identify implementation objects, while iid identify

Re: [fpc-pascal] EOLESysError calling CreateOLEObject

2008-07-22 Thread Inoussa OUEDRAOGO
2008/7/22 Marco van de Voort [EMAIL PROTECTED]: Apparantly when I converted the headers, I thought there only was one ID. However it seems that classids, and the ids in interfaces are different. I don't know enough from com to understand the difference, classids are used to identify

Re: [fpc-pascal] EOLESysError calling CreateOLEObject

2008-07-22 Thread Felipe Monteiro de Carvalho
On Tue, Jul 22, 2008 at 10:59 AM, Marco van de Voort [EMAIL PROTECTED] wrote: Fixed, added some more clsid constants in the process r11434 Could the fix be merged to 2.2.2? I would like to use the example in the Lazarus book, which will most likely come after 2.2.2 thanks, -- Felipe Monteiro

[fpc-pascal] Internal error 200502052

2008-07-22 Thread jordi
I get this error when I try to compile the compiler: sysos.inc(97,3) Fatal: Internal error 200502052 My OS: linux x86_64, any help will be welcome Thanks. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org

Re: [fpc-pascal] Internal error 200502052

2008-07-22 Thread Peter Vreman
jordi wrote: I get this error when I try to compile the compiler: sysos.inc(97,3) Fatal: Internal error 200502052 My OS: linux x86_64, any help will be welcome There is an problem with code generation. Please submit a bug with the steps how we can reproduce the issue. Peter

Re: [fpc-pascal] FreeBSD FPC i386 to AMD64

2008-07-22 Thread [EMAIL PROTECTED]
No Graeme, you isn't wrong, 64 bit FPC is not ready yet for FreeBSD... :( Thank you 2008/7/16 Graeme Geldenhuys [EMAIL PROTECTED]: On Wed, Jul 16, 2008 at 2:50 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi! What's the steps to build FreeBSD FPC AMD64 from FreeBSD FPC i386? Is

[fpc-pascal] freeing string equal to setting to empty string?

2008-07-22 Thread Marc Santhoff
Hi, I understand right that (as I have asked before) an empty (ansi)string is equal to NIL. If this is correct, is setting a string to '' the same as setting the string to NIL? So i can e.g. use exchagably: {$H+} var s: string; begin s := 'something'; { this ... } s := ''; { ...