Node:Known Bugs, Next:Planned Features, Up:To Do
In this section, you can find information about GPC bugs that are known to the developers.
If you encounter a bug with GPC, please check whether it is one of the known bugs. If not, report it to the GNU Pascal mailing list. (But always report if you solve the problem! :-)
Solved problems are moved to "Fixed Bugs" (see Fixed Bugs), and implemented features to the "News" chapter (see News).
A message ID (like <42@foo.bar>
) refers to a message in the
GPC mailing list or a newsgroup where the topic was discussed (often
a bug report). A note of the form (xy20001231)
refers to an
internal message of the GPC developers. A file name like
(foo42.pas)
refers to the according program in the GPC test
suite included in the GPC source distribution.
--borland-pascal
) when assigning/passing by value an object of derived type to one of a base type (and change the VMT pointer in the destination/actual parameter), don't change the VMT pointer when assigning to a polymorphic object (chief35[ab].pas), don't allow value parameters of abstract types, handle value parameters like variables in is
/as
setlimit
is applied when it shouldn't be ((a) variable/constant declarations, (b) set of ShortCard
, (c) constant sets)
goto
(contourbug.pas, martin1.pas, berend3.pas)
for
-loop counters after the loop (EP 6.8.1)
goto
targets more strictly <261020020000077022%gpaeper@empirenet.com>, <Pine.LNX.4.44.0210281004000.31943-100000@duch.mimuw.edu.pl> (fjf701*.pas)
goto
jumping out of two procedure nesting levels doesn't work (GCC bug; fixed in gcc-3) <200111170922.KAA09125@goedel.fjf.gnu.de> (fjf558[op].pas) (-> Trap
unit)
ReturnAddress
doesn't work after use of dynmamic variables (GCC bug)