At 03:14 PM 3/25/00 -0600, Dave Wolfe wrote:
>Abbreviations cause a similar problem. Future command set extensions
>can cause abbreviations that worked yesterday to now fail because new
>commands now share leading character sequences
I know - that's why I wanted to return either a list of ALL
commands, or more elegantly the list of commands that start
with the abbreviation supplied. Problem solved! The user is
educated instead of slapped, and fixes the problem in one
iteration. How often are keywords added? Is this a real concern?
>A fixed, documented command keyword set lets both users and
>developers know where they stand.
Then why have aliases at all? It's just for convenience, and
to support commands from other server software, not functionality.
>Your proposal is attractive but it's a slippery
>slope to start down. After all, you don't see the internationalization
>or abbreviation of C or Perl keywords, do you?
Actually, "#define" in various (system and user) include files
is used for precisely that! I'm not familiar enough with Perl
to make the same statement, but I bet it's also true.
|
|
