How are bug reports against 1.0.x handled? I went through some bugs just for the fun of it and found a lot to close -- however I only tested with the current CVS.
1954 - new TThread makes FHandle <> PID at all times
1694 - can probably be closed - I don't see how he could get gibberish
output but a runtime error I can see, sock2text was broken
2126 - another TThread thing
2683 - select is in winsock
2699 - attached is a patch to fix this
2726 - works for me with current CVS
(rtl a bit older because CVS doesn't compile)
2741 - works for me, "certain telnet clients" seems a bit odd anyway
2759 - attached is a patch of i386 only. However, wouldn't it be more
appropriate to handle FPU exceptions than checking all
pre-conditions?
All for now, got some other stuff to do.
johannes
--
http://www.sipsolutions.de/
GnuPG key: http://www.sipsolutions.de/keys/JohannesBerg.asc
Key-ID: 9AB78CA5 Johannes Berg <[EMAIL PROTECTED]>
Fingerprint = AD02 0176 4E29 C137 1DF6 08D2 FC44 CF86 9AB7 8CA5
? kerneldefs.ppu
? kernelioctl.ppu
? libc.ppu
Index: bstath.inc
===================================================================
RCS file: /FPC/CVS/fpc/packages/base/libc/bstath.inc,v
retrieving revision 1.1
diff -u -r1.1 bstath.inc
--- bstath.inc 26 Jun 2003 08:31:12 -0000 1.1
+++ bstath.inc 24 Nov 2003 18:13:46 -0000
@@ -13,7 +13,7 @@
type
P_stat = ^_stat;
PStat = ^_stat;
- _stat = record
+ _stat = packed record
st_dev : __dev_t;
__pad1 : word;
st_ino : __ino_t;
Index: math.inc
===================================================================
RCS file: /FPC/CVS/fpc/rtl/i386/math.inc,v
retrieving revision 1.16
diff -u -r1.16 math.inc
--- math.inc 11 Nov 2003 21:08:17 -0000 1.16
+++ math.inc 24 Nov 2003 18:42:27 -0000
@@ -191,8 +191,8 @@
else if expo=0 then
power:=1
else
- { bas < 0 is not allowed }
- if bas<0 then
+ { bas < 0 is not allowed when doing roots }
+ if (bas<0) and (frac(expo) <> 0) then
handleerror(207)
else
power:=exp(ln(bas)*expo);
signature.asc
Description: This is a digitally signed message part
