On 1 Sep 01, at 15:58, Frank Heckenbach wrote:
[...]
Like I said, putting them in any of the standard units (unless you change the names slightly) will create problems for those who use the real WinAPI stuff. In Delphi, you have to USE the Windows unit to get access to those functions. I have a functional Windows unit for the WinAPI imports, and there will be name clashes. So, until GPC gets qualified identifiers, I suggest you put them in a totally new Delphi compat unit so that nothing else is affected.
That's why I thought of the System unit (which GPC does not use automatically). But, of course, I have no personal interest in writing them at all, so if they're typically only used with other WinAPI routines, it might not be worth to write replacements, but rather a WINE interface or something for those who'll need it ...
Well, my suggestions here are a bit self-serving, because I normally USE the System unit, and I also have a functional "Windows" unit (the WinAPI imports unit). This of course means linker problems if the new routines are also in the System unit. One possible solution is to have them in the System unit, but to have them within an IFDEF. However, GetEnvironmentStrings et. al. do not really serve any useful purpose when you have the Dos unit, because there are Pascal routines in the Dos unit which do a better job, and without ugly C constructs.
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) Author of: Chief's Installer Pro for Win32 http://www.bigfoot.com/~African_Chief/chief32.htm Email: African_Chief@bigfoot.com