Re: [fpc-devel] Local procedures as procedural parameter

2005-03-16 Thread Peter Vreman
> 05-03-16 23.08, skrev Peter Vreman följande: >> >> But the framepointer parameter must then be the last. That will make >> macpas local procedures incompatible with the current code where it is >> passed as the first parameter. > > Couldn't the framepointer be last parameter in all modes ? That

[fpc-devel] TField.IsNull for Interbase (or rather Firebird :) implemented

2005-03-16 Thread Michalis Kamburelis
Hi I managed to implement correct TField.IsNull behaviour for fields inside TIBQuery dataset. I'm attaching: -- patch to packages/base/ibase/ibase60types.inc, this fixes a small bug in ibase60 unit that defined Short as Integer (= 32 bits, since ibase60 unit is compiled in objfpc mode), while i

[fpc-devel] xf86dga unit

2005-03-16 Thread Nikolay Nikolov
xf86dga unit attached you may add it to packages/extra/x11 xf86dga.tar.bz2 Description: application/bzip ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel

Re: [fpc-devel] Local procedures as procedural parameter

2005-03-16 Thread Olle Raab
05-03-16 23.08, skrev Peter Vreman följande: > > But the framepointer parameter must then be the last. That will make > macpas local procedures incompatible with the current code where it is > passed as the first parameter. Couldn't the framepointer be last parameter in all modes ? > Things lik

Re: [fpc-devel] Local procedures as procedural parameter

2005-03-16 Thread Peter Vreman
> > On 16 Mar 2005, at 21:46, Peter Vreman wrote: > >>> Then you can do it just as well on ppc and other processors, but the >>> point of the trick was to avoid having to do this. Implementing this >>> sort of hacks will complicate the code generator (I'm not even >>> immediately sure how it would

Re: [fpc-devel] Local procedures as procedural parameter

2005-03-16 Thread Jonas Maebe
On 16 Mar 2005, at 21:46, Peter Vreman wrote: Then you can do it just as well on ppc and other processors, but the point of the trick was to avoid having to do this. Implementing this sort of hacks will complicate the code generator (I'm not even immediately sure how it would be implemented). This

Re: [fpc-devel] crt unit fix

2005-03-16 Thread Michael Van Canneyt
On Wed, 16 Mar 2005, Dr. Karl-Michael Schindler wrote: > Hi, > > When I was at the crt unit, I noticed that a number procedures are small (less > then 5 lines of code) and called only once. Some others are quite general like > scrollregion, but called only once with one line. In my opinion the

Re: [fpc-devel] Local procedures as procedural parameter

2005-03-16 Thread Peter Vreman
>>> That won't work on x86 when the static link would be on the stack, >>> because there the callee removes the parameters from the stack (so if >>> it's a global function, it will remove sizeof(pointer) bytes too >>> little from the stack. >> >> On x86, you can generate code that checks the static

Re: [fpc-devel] Create installer for MacOSX

2005-03-16 Thread Vincent Snijders
Jonas Maebe wrote: On 15 mrt 2005, at 05:58, Adriaan van Os wrote: PackageMaker is basically a GUI interface to pax, so it might be possible to create a Mac OS X installer package with command line tools. You would have to look at the file layout of a package by using PackageMaker first or by lo

[fpc-devel] crt unit fix

2005-03-16 Thread Dr. Karl-Michael Schindler
Hi, When I was at the crt unit, I noticed that a number procedures are small (less then 5 lines of code) and called only once. Some others are quite general like scrollregion, but called only once with one line. In my opinion the code would be better readable with some degree of "inlining" thes

Re: [fpc-devel] crt unit fix

2005-03-16 Thread Jonas Maebe
On 16 mrt 2005, at 17:54, Dr. Karl-Michael Schindler wrote: On Mac OS X I could fix it by deleting line 463 and 464 of crt.pp. Then it works with ALL 6 different terminals (Terminal.app, X11, xterm, aterm, eterm, rxvt, mlterm) I have installed. Thanks, fixed (worked fine under Linux as well). Jon

Re: [fpc-devel] crt unit fix

2005-03-16 Thread Dr. Karl-Michael Schindler
On Mac OS X I could fix it by deleting line 463 and 464 of crt.pp. Then it works with ALL 6 different terminals (Terminal.app, X11, xterm, aterm, eterm, rxvt, mlterm) I have installed. Am 15.03.2005 um 10:20 schrieb Jonas Maebe: On 15 mrt 2005, at 08:51, Dr. Karl-Michael Schindler wrote: There i

Re: [fpc-devel] Local procedures as procedural parameter

2005-03-16 Thread Jonas Maebe
On 16 mrt 2005, at 17:42, Adriaan van Os wrote: That won't work on x86 when the static link would be on the stack, because there the callee removes the parameters from the stack (so if it's a global function, it will remove sizeof(pointer) bytes too little from the stack. On x86, you can generat

Re: [fpc-devel] Local procedures as procedural parameter

2005-03-16 Thread Adriaan van Os
Jonas Maebe wrote: [EMAIL PROTECTED] wrote: Example Powerpc with static link first: local static link r3 param no 1 r4 ... global param no 1 r3 ... To avoid this problem, it would be better to have the static link last. That won't work on x86 when the static link would

Re: [fpc-devel] Local procedures as procedural parameter

2005-03-16 Thread Jonas Maebe
On 14 mrt 2005, at 12:15, [EMAIL PROTECTED] wrote: Example Powerpc with static link first: local static link r3 param no 1 r4 ... global param no 1 r3 ... To avoid this problem, it would be better to have the static link last. That won't work on x86 when the static link

[fpc-devel] Interbase.TIBTransaction should publish some private things

2005-03-16 Thread Michalis Kamburelis
Hi Looking at Interbase unit (fcl/db/interbase/interbase.pp), I see that TIBTransaction was probably meant to publish properties AccessMode, IsolationLevel, LockResolution and TableReservation. This would be definitely useful to users of this class. I'm attaching simple patch that does this. M