Well, I agree it could be a daunting task, but it seems whenever
people start talking about the programming of new features,
they all react like its impossible and too complex. Some of us
can imagine what the mIRC programming might currently look like,
but does anyone know for certain what it actually is like?
I considered the parallel executing and yeah you would need to
address the commands/identifiers/events in specific manners, but
is by no means impossible.
Example:
thread -G <Name> {
/set %var 1
}
thread -P <Name> {
/set %var 2
}
Events are probably a no-go with multi-threading, or could be
left out until it could be sorted out properly.
but why not just have it encapsulate whether a scripting thread
is global or private? Global takes priority over public, so if
both threads executed simultaneously %var would be 1. Its a
simple example, and I'm sure others have many more difficult
executions they were thinking about when they discussed this,
but thats why I believe some commands or identifiers should be
left out of the threading loop if necessary.
So maybe if everyone showed increasing support for it, it might
move up the list on potential enhancements. Just a thought.
