It is up to the script writer to set the path correctly, not me. I make sure my files and paths are accurate. If someone else makes their own script and names a file the same as an existing file of mine, yes it will overwrite it. It is up to them to script smartly.
At the risk of pointing out the ridiculously obvious, you're the script writer in the scenario I just described. There's you and another scripter involved. To say that your paths are more valid than any other script is simply wrong. The point is that you
and the other scripter should
both be writing your scripts to co-exist with each other-- this means not using $mircdir and risking name collision. Why you can't understand this probably has to do with your inability to read the one line help topic regarding $mircdir in mirc.hlp. Try /help $mircdir.
However, your point doesn't apply. If I write a script that uses $mircdirquotes.txt, then it will write to the quotes.txt file in the same directory as mirc.exe.
You really need to step back and read the docs. $mircdir does
not guarantee, I repeat,
NOT GUARANTEE that it will be the same dir as mirc.exe. This depends heavily on the users setup. $mircdir in a default install
DOES NOT return the same path as mirc.exe. You really need to comprehend this.
Secondly, again, read the docs. Here, I'll help you by showing you the docs for you:
$scriptdir
Returns the directory of the currently executing remote script.
This means that $scriptdir returns $nofile($script), NOT $mircdir\scripts.
If someone is so worried about this they can make another directory
This is
exactly why you use $scriptdir. Because with it, you can have the following scripts co-existing peacefully:
- myscript\
|-- myscript.ini
\-- quotes.txt
- yourscript\
|-- yourscript.ini
\-- quotes.txt
Personally I use neither though I guess it's $mircdir by default.
This is an idiotic justification to advocate poorly written scripts.
The idea that there is one and only one way to do anything in mIRC is horribly inaccurate.
The fact that you're wrong about FACTUAL information regarding how mIRC handles $mircdir and $scriptdir is, however, an absolute. Again, get your facts straight, because you're making a mess of this thread.
If you read the readme.txt that comes with mysql.dll it will tell you that it will only work if the dll is in the same directory as mirc.exe.
===============================================================================================
= Installation =
===============================================================================================
libmysql.dll must be placed in the same directory as mIRC's program. mysql.dll can be placed
anywhere.
Once again, wrong.
