Node: Known Bugs, Next: Planned Features, Up: To Do

### Known bugs in GPC

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.

- `setlimit` is applied when it shouldn't be ((a) variable/constant declarations, (b) `set of ShortCard`, (c) constant sets)
- problem with string operations and `goto` (contourbug.pas, martin1.pas, berend3.pas)
- global variables of dynamic size don't work (john1.pas)
- declaring a procedure in the implementation with the same name as an imported procedure doesn't work (chief18.pas), detect name collisions between imported EP modules (mod9.pas)
- dynamic sets don't work
- there are some bugs with mathematical functions; GPC fails, for example, the Paranoia test
- check `goto` targets more strictly <261020020000077022%gpaeper@empirenet.com>, <Pine.LNX.4.44.0210281004000.31943-100000@duch.mimuw.edu.pl> (fjf701*.pas)