Maurice Lombardi wrote:
The bug did not show up with the default debugging format for djgpp (COFF). But since stabs is much better for pascal debugging than COFF, I have recompiled gpc 2.1 with this only change (not others which might be in CVS) and uploaded it in the "contrib" section under
http://www.gnu-pascal.de/contrib/maurice/gpc-2.1-gcc-2953.i586-pc-msdosdjgpp...
(not yet in the "current" section to avoid confusion: pgp signatures etc..)
Actually, I'm not sure we should put it in current at all. It might be better to leave 2.1 (only) in current until some major changes have taken place -- maybe even until the release of 2.2 (provided the time between 2.1 and 2.2 will be a little shorter than that between 2.0 and 2.1 ;-).
So I think when I upload the next patch, I'll put it in alpha (which is currently empty), and move the contents of beta to old (to avoid confusion), and leave current as it is. Would this be reasonable?
(The GPC manual says: "You can download the source code of the current GNU Pascal release from http://www.gnu-pascal.de/current/" -- which remains true if we consider alphas not releases, but snapshots. ;-)
I could see a problem for the install.gpc script, though ...
Hmm, if necessary I could create `latest' or so which always contains the most recent upload (whether snapshot or release).
Or we could move 2.1 from current to, say, `stable', and put the new alpha in current.
I remember we talked about this some time ago, but I don't remember the final conclusions (if any). And I'm not familiar with the current status of the script (does or should it allow the user to select between alpha/beta/stable/latest, whatever?) ...
Frank