[M3devel] archive bloat

[Mika Nystrom]

I'm just saying, what you're proposing is an exception to how Modula-3
works.  When you make a package and ship it, you always ship it with
both interface and library files.  Is it really warranted making a special
exception for m3back, m3front, m3quake?

Besides, how are you going to re-use the m3back package unless you
add "cm4" to the main compiler distribution?  I want to be able to
maintain my own software separately from the CM3 distribution...and
then you have to keep the sources around, too?  Hrmph....
 
     Mika

Jay writes:
>
>Is it really meant to be reusable by anything other than cm3?
>Even still, the workspace includes all the source. You can just build it if yo
>u really need it.
> 
> - Jay
>
>
>----------------------------------------
>> To: jay.krell at cornell.edu
>> Date: Fri, 26 Jun 2009 05:38:28 -0700
>> From: mika at async.caltech.edu
>> CC: m3devel at elegosoft.com
>> Subject: Re: [M3devel] archive bloat
>>
>> Woudln't not including libm3back.a (e.g.) be a special case?
>>
>> What if I write another program, call it "cm4", that imports the
>> m3back package... what does it link against?
>>
>> Mika