saying its a "question of professionalism, and of respect for customers" just because it isnt included in each download isnt fair
Heh, I'm being unclear. Mea culpa. To clarify: I find the lack of a truly comprehensive, updated help file to be a question of professionalism and respect for customers.
In the example I gave about the me prefix in remote definitions, it was necessary to go back to notes on version 3.8 (released in November 1995!!) to find documentation of a feature which works in version 6.12.
I challenge anyone to find another piece of software (excluding operating systems) in which it is necessary to review documentation for an eight-year-old version to learn not only how to use a feature that is still current, but that the feature exists at all!
Things mentioned on these fora as not documented in the help file within the last 6 months (see especially
this thread) include:
$*, $beta, $pnick, $nickmode, 'Flush files', $lof, /action, $colour(), $iaddress, $naddress, $raddress, $token(), $mp3(), $shoe(), $r(), $yes, $no, $cancel, !===, /setlayer, $pi, $evalnext(), /registration (!!!!!), $nopnick(#, N), $nvnick(#, N)...
There are of course others.
While there may be reasons for non-inclusion, the fact is that they're there and they work (for the time being, at least). So why not document them, including where necessary a note that a particular feature is present for backwards compatibility only or is slated for removal?
I just do not see how anyone can argue that this is a satisfactory situation. It's not going to stop me from using mIRC, which I registered years ago - but neither do I believe that mIRC is up to scratch in this regard. And these forums are in part here to provide user feedback, yes?
PastMaster