Message-Id: <m0y4kR4-000S2eC@inti.gov.ar>
Comments: Authenticated sender is <salvador AT natacha DOT inti DOT gov DOT ar>
From: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
Organization: INTI
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date: Tue, 17 Feb 1998 13:48:18 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: open patch for share flags
References: <m0y4gFl-000S1oC AT inti DOT gov DOT ar>
In-reply-to: <Pine.SUN.3.91.980217172314.6103E-100000@is>
Precedence: bulk

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
> On Tue, 17 Feb 1998, Salvador Eduardo Tropea (SET) wrote:
> 
> > Yes if we want to use the same way that was used for __crt0... flags, no if the 
> > user assigns the value in main (that's what I make).
> > What's the better?
> 
> I think it is better to let the user say "int share_flags=whatever" 
> outside any function, because this is more flexible.  So I think the 
> variable should be in a separate module in the library.
 
Ok, I'll do it in this way.

SET 
------------------------------------ 0 --------------------------------
Visit my home page: http://set-soft.home.ml.org/
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-sot AT usa DOT net - ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013