Re: [fpc-devel] Some Dataset and Variants patches
Any reason to re-implement the tempbuffer? Or were you just using an older version? Please give me more datails (history) about tempbuffer. Well, it was an empty procedure. But no-one had a clue where it was used for. Probably it had something to do with some very old fpc-TDataset- descendents. So it got removed. But if you can find a reason to keep it there... Maybe that ZEOS uses it? I can look deeply into ZeosLib and find out why it needs tempbuffer. Patch with constraints and tempbuffer is really not important. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Some Dataset and Variants patches
It seems that there are many delphi compatible components left that use tempbuffer. I have myself reintroduced this function instantly, becouse it is used in filtering/searching operations by my dataset component. Since this function exists in delphi and it is used by some components, i see no reason not to have it in fpc. Ok, forget my last message then, i'll re-implement it. Do you also know what it should do? Regards, Joost ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Some Dataset and Variants patches
On 9/19/05, Joost van der Sluis [EMAIL PROTECTED] wrote: It seems that there are many delphi compatible components left that use tempbuffer. I have myself reintroduced this function instantly, becouse it is used in filtering/searching operations by my dataset component. Since this function exists in delphi and it is used by some components, i see no reason not to have it in fpc. Ok, forget my last message then, i'll re-implement it. Do you also know what it should do? Regards, Joost Function TDataset.TempBuffer: PChar; begin Result := FBuffers[FRecordCount]; end; The result of this function is used in filtering/searching operations. Alex ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Sets and delphi compatibility
Hi.
I found, that this code does not work like in Delphii (-Sd).
var
v: variant;
begin
v := 'hi';
writeln(VarType(v));
writeln(varEmpty);
writeln(varNull);
if VarType(v) in [varEmpty, varNull] then
writeln('NULL')
else
writeln(v);
end.
FPC output:
256
0
1
NULL
DCC output:
256
0
1
hi
I think that compiler makes set [varEmpty, varNull] only 8-bit. Is't any
switch here to increase Delphi compatibility?
Petr
--
Ing. Petr Kristan
.
EPOS PRO s.r.o., Bozeny Nemcove 2625, 530 02 Pardubice
tel: +420 466335223Czech Republic (Eastern Europe)
fax: +420 466510709
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] FPC and valgrind
I thought the following message on the valgrind users list might be of interest - it is in response to a message I posted. (The reply came months after the original, so I didn't notice it immediately). I do not know how to respond to the question at the end. The first patch at least seems to have made it into the 2.4.1 release of valgrind. Colin (Original URL: http://sourceforge.net/mailarchive/message.php?msg_id=12412006) In message [EMAIL PROTECTED] C. Western [EMAIL PROTECTED] wrote: My knowledge of stabs is very limited, but with a bit of guess work and some help from a bugzilla report I was able to get valgrind working on my free pascal programs by applying the attached patch to rc4. Thanks for the report. --- ./coregrind/vg_stabs.c.orig2005-03-12 08:22:46.0 + +++ ./coregrind/vg_stabs.c 2005-03-19 19:25:21.813549592 + @@ -646,6 +646,7 @@ case -27: type = VG_(st_mkint)(def, 1, True); break; case -28: type = VG_(st_mkint)(def, 2, True); break; case -29: type = VG_(st_mkint)(def, 4, True); break; + case -30: type = VG_(st_mkint)(def, 2, False); break; case -31: type = VG_(st_mkint)(def, 8, True); break; case -32: type = VG_(st_mkint)(def, 8, False); break; case -33: type = VG_(st_mkint)(def, 8, False); break; Ive committed this to the valgrind 3.0 SVN repository. --- ./coregrind/vg_stabs.c.orig2005-03-19 21:33:03.0 + +++ ./coregrind/vg_stabs.c 2005-03-19 21:33:29.0 + @@ -1610,8 +1610,8 @@ scope.nsyms = 0; } - vg_assert(scope.addr != 0); - VG_(addScopeInfo)(si, scope.addr, addr, scope.scope); + if (scope.addr != 0) + VG_(addScopeInfo)(si, scope.addr, addr, scope.scope); /* XXX LEAK: free scope if it or any of its inner scopes was never added to a scope range */ How did you manage to get a scope at address zero? why do you think such a scope should be ignored rather than added - maybe your program really does have code at address zero? Tom Tom -- Tom Hughes ([EMAIL PROTECTED]) http://www.compton.nu/ ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
