Quote:

There is a reaosn why we have created the UDF Guidelines and why we try to have every single UDF adhere to this. For example, by posting addtional text before the UDF itself, you've just messed up the automatci extraction process used to populatethe UDF mirrors.

Also, we are holding UDFs to a much higher standard than code thatis posted in the scripts forum. The reason being that UDFs should be black boxes mirroring the style of internal Kixtart functions. UDFs have to be graceful with regards to the interactions and be clean, e.g. not keep the log file open as it will interfere with other script functionality. UDFs posted here are not meant to be specialized functions that only work under special circumstances but generalized functions that work in all kinds of environments. Thsi is one of the reasosn we the UDF rules are on the restrictive side. If a UDF does not comply with NoVarsInStrings=ON and Explicit=ON, then the UDF will break a lot of scripts.

Hey, here's an idea. Why don't you all take turns explaining something to me that I ALREADY COMPLETELY UNDERSTAND.

I've removed the script. Problems solved. Cheers.


Edited by MythosAZ (2004-09-25 02:29 AM)