After some discussions with Stefan Haubenthal, I've written new routines for handling the environment. Available functions are putenv and getenv, plus the environment pointer _environ. The module that defines _environ will call a constructor named initenv, which is not defined and must come from platform code. For platforms that have some form of environment (Lunix?), this constructor can initialize _environ, which makes its values available to the program. Other platforms that want to use the environment routines must supply an empty constructor. Using a dummy module that contains .export initenv initenv = return0 is sufficient. Existing platform dependent getenv routines (which all returned NULL) have been removed. Regards Uz -- Ullrich von Bassewitz uz@musoftware.de ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Thu Apr 21 23:42:53 2005
This archive was generated by hypermail 2.1.8 : 2005-04-21 23:42:56 CEST