On Mon, 19 Jul 2004, Arkady V.Belousov wrote:
Hello,
----------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^Unfortunately, FreeCOM (included into 2035 package) wrongly handles empty enviornment (easy to reproduce in MS-DOS, as I report this in group). Lookslike Steffen fixes (at least, one) bug, related to environment, but up to now I don't know where to download fixed version. (May be, now you remind for Steffen to make fixed version available for download?)SK> Arkady, FreeCOM _never_ had a problem with an _empty_ environment, but:
See underlined words above. With empty environment FreeCOM (whic is currently available for use) _is_ buggy.
SK> + with a missing '.' in PATH, long fixed, and SK> + with the MS-DOS-style of an empty environment, you've called "broken" SK> yourself.
You mean "Arkady called MS-DOS-style empty environment broken"? Yes, I call this. But this is MS-DOS and all its bugs become standard and called
So, you've "fixed" the FreeDOS kernel to issue the broken MS-DOS "empty environment" to programs, did I understood it correctly?
Actually, it would be cleaner to never issue an empty environment. You will, for instance, find a reply in the archives from yourself, stating that the end of the environment is _not_ marked by '\0\0' (two bytes zero) as the poster stated, but by an empty string, hence, when the environment is completely empty, there is a single '\0'.
To have a good and working work-around for any program and your own advices, it would be best to never pass on an empty environment.
Bye,
--
Steffen Kaiser
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
