Mail Archives: djgpp/2000/06/09/17:35:10
On Fri, 9 Jun 2000 21:53:41 +0200, =?iso-8859-1?Q?G=FCnter_Ladwig?=
<gladwig AT iname DOT com> ate too many hallucinogenic mushrooms and wrote:
>Most of my Allegro files have a modification date of 31/01/2000, certainly
>not only a few days old.
Well I am not developing for it or anything. I downloaded and unpacked
the zip yesterday, so the file timestamps for the files I thus created
on my system ought to be yesterday.
>AFAIK the DJGPP version is maintained by Shawn himself and it
>is the most stable and the most thoroughly tested part of Allegro.
It's supposed to be, bot honestly I don't see anything wrong in my
installation procedures. I consulted the Allegro FAQ; it would have
informed me if overwriting an old version could in any way cause a
problem. It says no such thing.
>It may be that it was never tested
>on your type of configuration, but it can't be possibly tested everywhere.
Well, that could be. If that's the case, then I would have to conclude
that it's the PGCC support that's broken, which is a crying shame...
>And so this complaining won't help you, instead look into the source and see
>what the reason for the failure was. Or write to the Allegro mailing list.
I don't know beans about Allegro's internals. I would probably not be
able to make heads or tails of the source. If it was a single typo,
this I could probably fix, but there are hundreds of errors -- the
error log runs to 50 kilobytes! It could be that one of the parse
errors derailed the compiler, but odds are there are multiple real
errors if there are any at all in the sources, probably in the #ifdef
PGCC areas...
>And you know what? This is the reason why it's called 3.9.32 and not 4.0.
>The development till the version 4.0 is nearly complete, but we want to be
>sure that the will be no errors in the first release.
I am well aware that beta products can be expected to have bugs or
quirks. However, I don't consider it unreasonable to expect that betas
do *not* contain showstopping errors that prevent the thing from even
being installed... Alphas can be expected to be that unstable, or CVS
snapshots, with the occasional build not actually building on some
targets, or not working on certain configurations...
--
Any sufficiently advanced magic is indistinguishable from
an Allegro-using C++ program compiled with gcc.
- Raw text -