Re: read_objid() capability to interpret strings

[Wes H. <wjh...@uc...>]

>>>>> On Wed, 22 Nov 2000 23:28:34 +0100, Juergen Schoenwaelder <sc...@ib...> said:

Juergen> I strongly disagree. A program which simply converts

Juergen> SNMP-COMMUNITY-MIB::snmpCommunityName."foo" 

Juergen> to 1.3.6.1.6.3.18.1.1.1.2.3.102.111.111 is broken.

You're obviously not a hacker!

Juergen> A program which converts 1.3.6.1.6.3.18.1.1.1.2."foo" to
Juergen> either

Juergen> 1.3.6.1.6.3.18.1.1.1.2.3.102.111.111
Juergen> or
Juergen> 1.3.6.1.6.3.18.1.1.1.2.102.111.111

It would pick the first.  We reserve the other quote marks ('') for
the non-prefixed case.

I'm not saying its a good thing for general practice, but typing
\"foo\" is much easier than typing .102.111.111 since I don't have the
ascii table memorized.

Anyway, would you apply the same strictness to other tools like chown
(picking one at random), not allowing it to accept a number and
forcing the user to have the user name in the password file for
translation?

Anyway, my goal is always to provide the ultimate in flexibility.  99%
of the world won't need the functionality, but the rest of us might.
-- 
Wes Hardaker
Please mail all replies to net...@li...