CompuServe Messages

[Continued] >>U>I hope this is not barking up the wrong tree, but why do you think the >>U>code does not compile? Is his example incomplete? Or do you think there is >>U>some sort of obvious thing you are missing or what? >> >>The example is not complete. > >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. >>I'll take your suggestion and try to look on USENET, if I can figure >>out how to access USENET yet through Compuserve or BIX. > >You don't get usenet access through CIS or BIX (although CIS has e-mail >capability at the moment). > >>I'll put the code I'm working on here, one file per message. I believe >>that I've changed Mr. Stroustrup's code in a nondestructive way but missed >>part of it or grabbed the wrong part of it. (My command line is >>"rx como -V -D__NO_PRAGMAS if.c" .) > >Not sure what I should do with any of this code. I was hoping you could look at it, maybe try to compile it, and tell me why it won't compile. Your message gave me the idea to try to exactly duplicate Stroustrup's code. 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>> error: table.grow( 5, 5) (By the way, I have 6 MB of RAM free before the compilation, in case that's important.) My next message will contain the code that demonstrates the bug. [More]