CompuServe Messages

[Continued] >>Have you sent Stroustrup mail on BIX asking him if he has complete code for >>this example? >I will try to find his address and take it up with him. Please do not necessarily say I said for you to demand this from him. As you are saying that the code is alledgedly incomplete as posted in *his* book (and maybe he intended it that way), all I am saying then is that he is a likely source of telling you where (if anywhere) to look in the book or electronically somewhere. >Your message gave me the idea to try to exactly >duplicate Stroustrup's code. I guess I'm confused. I thought you said the S2 code was incomplete? >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).