Sender: nate AT cartsys DOT com
Message-ID: <35C89BB3.D96041E9@cartsys.com>
Date: Wed, 05 Aug 1998 10:51:47 -0700
From: Nate Eldredge <nate AT cartsys DOT com>
MIME-Version: 1.0
To: sl AT psycode DOT com DOT REMOVE_THIS
CC: djgpp AT delorie DOT com
Subject: Re: RHIDE, commandline-line and linking
References: <m0z43tk-000S4fC AT inti DOT gov DOT ar> <iCdMCj1ZQ5j2-pn2-u2Hjd1eiSfbu AT portD18 DOT Generation DOT NET>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

sl AT psycode DOT com DOT REMOVE_THIS wrote:
> 
> On Wed, 5 Aug 1998 10:57:14, "Salvador Eduardo Tropea (SET)"
> <salvador AT inti DOT gov DOT ar> wrote:
> 
> > I think you'll have the same problems that you could experiment using command
> > line: Memory and speed. But if you have enough memory and don't worry about
> > speed it will be ok.
> > I use around 12 libraries in my editor.
> 
>         Ok, but in the case of linking 100 .o files together.. Is _that_
> possible?

Sure, why not?  The only possible limitation is if the command line
exceeds 16K or so, in which case you can just stubedit the caller to a
larger transfer buffer.

A better option might be to group them into libraries, which will dodge
the long line problem.  And don't worry about all the .o files in the
library-- libc has a few hundred .o files inside it.
-- 

Nate Eldredge
nate AT cartsys DOT com