🚀 go-pugleaf

In article <1991Mar22.190524.2666@Octopus.COM> pete@octopus.COM (Pete Holzmann) writes:
>>> mwick@.com (Mark Wick) /  2:27 am  Mar 15, 1991 /
>>>> We have a very large application which we are trying to move to Windows
>	      ^^^^^^^^^^^^^^^^^^^^^^
>	      [and had trouble linking]
>
>> richardh@hpopd.pwd.hp.com (Richard Hancock) writes:
>>>We had a similar problem. The work-around (?) is to only selectively compile
>>>with the Zi compiler switch, ie. compile only those modules you're 
>>>particularly interested in.
>
>pcb@basin04.cacs.usl.edu (Peter C. Bahrs) writes:
>>hmmmm...I have an application that is 38,000 lines of code, numerous
>				       ^^^^^^^^^^^^
>>obj files.  I have no problem and compile under a command.com shell 
>>while running windows...
>>It works fine.
>
>Your application is medium-large, not very large. You'll know you're at
>the very large stage when the linker stops working. When the compiler
>runs out of heap space while it is still working its way through your
>include files. When you can't debug your program even under Magic CodeView.
>THEN you've got a very large application! May you never have to work on
>such a beast :-) :-). (I, unfortunately, have and am. Selective use of
>/Zi/Od is only the first stage of this particular disease :-))
>

Actually, when I said I have a very large application, I meant just that.
We have ~150,000 lines of code right now, not counting another 150K or so
in libraries we are linking to.  I finally got around the compiling and
linking problems - 386Max or Quarterdeck (QEMM) give another 90K or so of
memory, which was enough to compile the files and link.  Microsoft's end of
March release will hopefully provide a compiler that can use extended
memory.  Of course, Codeview is currently giving us problems that no one
seems to have answers for, but that's another story.



Mark