From: Steven E. <ste...@ya...> - 2002-07-07 07:13:29
|
I would assume it may have something to do with the line right above that "This function is retained for backward compatibility with Windows 3.1. Use ExpandEnvironmentStrings instead. " Win3.1 wasnt the most stable beast M$ has ever made and I assume the "unexpected" could cause very bad results in other areas besides the target application. --- Royce Mitchell III <ro...@ev...> wrote: > I was reading about shell32.DoEnvironmentSubst(), > and I came across an > interesting comment in MS documentation: > > Parameters must contain valid values that are not > NULL. You are responsibile > for validating these values. If you do not validate > it, you will experience > unexpected results. > > Here's the link where that comment can be found: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/pla > tform/shell/reference/functions/doenvironmentsubst.asp > > Now, my question is this: what is the harm in > checking for invalid params, > and returning failure instead of just letting the OS > do it's "unexpected" > thing? > > Royce3 > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Got root? We do. > http://thinkgeek.com/sf > _______________________________________________ > reactos-kernel mailing list > rea...@li... > https://lists.sourceforge.net/lists/listinfo/reactos-kernel __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com |