Feature suggestion: Non-null command args

[Jason Martin]

One idea for a new feature would be to allow the $ARGx$
arguments to be defined as not-null, and error on preflight if
they are.  This is to prevent defining a command that expects 4
arguments, but the service definition only has 3 defined. This
can cause unexpected behavior from the plugin, depending on
which argument was missing and in what order.

I'd think it could be implemented as a attribute to the "define
command", or instead creating a seperate set of macros called
$NARGx$, where N indicates not-null.

-Jason Martin
-- 
Only cosmetologists give make-up exams.
This message is PGP/MIME signed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 211 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/developers/attachments/20050510/f8c187fb/attachment.sig>