Rainer Schuetze, el 12 de October a las 10:30 me escribiste:
> On 12.10.2014 05:41, Walter Bright wrote:
> >On 10/11/2014 4:23 PM, Leandro Lucarella wrote:
> >>It basically defines a bunch of environment variables and run the
> >>binary. This is a super common practice in posix systems. We are not
> >>inventing anything here. I don't know how windows or other OSs deal with
> >>defining environment variables in a script.
> >>
> >>Very basic facilities are always configured this way, for example try
> >>man 3 mallopt to see how can you change options in the malloc
> >>implementation using environment variables...
> >>
> >
> >I don't deny it is common practice on Linux, but defining a bunch of
> >environment variables and then running the app, i.e. using the ev's as
> >command line switches, seems pointless. Just use command line switches.
> >
> >Anyhow, environment variables are a common source of problems on
> >Windows, which is why dmd, for example, uses dmd.conf instead.
> 
> C# programs also use app.exe.config files alongside the executable
> to setup the application. Maybe we could do something similar.
> 
> I just found this in msbuild/14.0/bin/csc.exe.config:
> 
> <configuration>
>   <runtime>
>     <gcServer enabled="true" />
>     <gcConcurrent enabled="false"/>
>   </runtime>
> </configuration>

Windows only please! :-)

Also, completely unflexible, so to run 2 instances of the same program
with different configuration you have to run one, modify the config file
and then run the seconds?

OUCH.

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
De tan fina la condesa, por no cagarse, reza.
        -- Ricardo Vaporeso

Reply via email to