delorie.com/archives/browse.cgi | search |
Message-Id: | <200002281851.MAA23742@darwin.sfbr.org> |
Date: | Mon, 28 Feb 2000 12:51:01 -0600 (CST) |
From: | Jeff Williams <jeffw AT darwin DOT sfbr DOT org> |
Subject: | Re: ANNOUNCE: Bison 1.28 ported to DJGPP |
To: | eliz AT is DOT elta DOT co DOT il |
Cc: | djgpp-workers AT delorie DOT com |
MIME-Version: | 1.0 |
X-Mailer: | dtmail 1.3.0 @(#)CDE Version 1.3.4 SunOS 5.7 sun4u sparc |
Reply-To: | djgpp-workers AT delorie DOT com |
-: > -: Somebody suggested in the past a better solution: support for -: > -: program-specific .env files. That is, the startup code of a program -: > -: foo.exe would look for a file foo.env *after* reading djgpp.env. -: > -: > How is this different from having program specific `.rc' files? -: -: I don't know. Why is it important whether it is or isn't similar to .rc -: files? Aren't .rc files a canonical means for modifying a program's environment at startup? This thread got me thinking about how much of djgpp.env is (or must be) djgpp-specific, and how much of djgpp.env could be taken over by individual .rc files.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |