Sorry, I was being vague. Some how abstracting the function from what I was using for has made it less useful.

Where I use SafeURL() is for re-using input data as values in URL links as these values (as I've been using them) generally tend to be nothing more than simple text/email strings.

For example mycgi.pl was called as

http://mycgi.pl?sect=test
[download]

I would use SafeURL() on the value of 'sect' and use it to create new dynamic links

http://mycgi.pl?sect=test;page=22
[download]

So I guess the purpose of SafeURL() is to make the data safe to feed back into a new URL, but that appears to be specific to my use, and probably not of much use beyond.

Seemed like a good idea at the time :)

EscapeJavaScript() still has it's uses, unless CGI provides an equivalent function?