CompuServe Thread

> #: 29493 S5/C Programming > 22-Oct-92 15:41:50 > Sb: #29492-C++ question > Fm: Greg Comeau@Comeau Cmptg 72331,3421 > To: Greg Comeau@Comeau Cmptg 72331,3421 > > … > > >By doing that, I think I have found a bug > >in Cfront. I'm not sure whether it's an AT&T bug or a Comeau Computing > >bug (or my bug). By merely declaring two objects of similar but > >distinctly named classes (just before function "main"), I get the error: > >"aplist.h", line 116: internal <<AT&T USL C++ Language System <3.0> 09/15/91>> e > > Interesting, we compiled the code under MS-DOS, then UNIX SVR4 (and with > 3.0.1 as well as 3.0 here), and then under AmigaDOS, and only the AmigaDOS one > produced the result you got (the others compiled fine). It blew up in a > routine which allocates more symbol table space for cfront. It does not > look like your bug, and 3.0 is known to have some template problems from > AT&T (I'll have to work on checking this out with a 3.0.1 under AmigaDOS). What would be the next step in getting us Amigos a version that will run under AmigaDOS without this problem? Do you have an idea how long that will take? Is this strictly a problem with the Amiga port of Cfront, or basically an AT&T bug that only shows on the Amiga, or something else? Will you take on this bug yourself, Greg, or can you get AT&T to fix it? Is there anything I can do to grease the wheels of progress? Tom