Everyone knows that this solution will not solve the problem. If you make NUL global it will override a NUL alias.
You're possibly confusing parameters and/or switches? Nul is not nor would it be treated as a command/alias.
Consistency is key to scripting. Consistency of the language and how it performs in every situation. This goes against that.
Again, nul is not a command/alias, but a device used in place of [device\]filename parameter. A device allowed in mIRC for years.
If you are concerned about speed then don't use /filter for reading files. And speed is pretty irrelevant these days...
You apparently either don't know about the efficiency and versatility of /filter, or you didn't have to parse/manipulate
large text files as yet.
What is more, one does not put NUL as outfile of a /filter command only to save a few bits of code ("/remove outfile"-command), but mostly because it's the
fastest way to get $filtered. It's fast as it's not writing anything to the disk while reading the file.
@drum and hixxyA switch could preserve the functionality for the future. But it would break a lot of
existing scripts if the support for nul as
parameter ("outfile") would stop.
While I wouldn't mind a new switch, I hope mIRC is keeping up the support of nul as "outfile"
parameter where it's apparently safe to - like in filter and fopen. Heck, mIRC still supports "$readini filename section item" and the like for compatibility reasons...
