Re: [lisp-snmp] Patch to asn.1 to change from parsergen to a modified cl-yacc

[John F. <jf...@ms...>]

Dear Chun Tian,

"Chun Tian (binghe)" <bin...@gm...> writes:
[...]
> To respect your wishes and still keep the implementation of OID
> function simple, I has changed the behavior (short-package-name) into
> a compile-time option.
>
> If you update both ASN.1 and SNMP package to newest SVN trunk, you'll
> find file "features.lisp-expr" in both packages. There's
> one option in #p"ASN1:features.lisp-expr":
>
>  ;;; Short package name of MIB packages, disable for expert only.
>  short-package-name
>
> If you disable it (either prefix a #+ignre or comment it), and
> recompile the compiler part of ASN.1 packages, next time when you
> compile MIB files or just use (snmp:update-mib) to regenerate all
> MIBs, the new generated files will NOT have short nicknames at all.
>
> As before I don't think it's necessary to disable the short package
> names since it's quite convenient. But if you really don't like it, I
> hope you would like above solution.

Most of the short MIB package names are fine. If they are validated by
you at compile time that is doubly fine.

The problem is in loading in user defined package names at runtime. It
is important that we don't cause name collisions if the user for some
reason wants to load in an MIB which might, for example, have the same
name as our application (which is already a Lisp package).

Perhaps having an option to avoid polluting the global package namespace
is a good idea. I guess we should rewrite the runtime loading in of MIB
files anyway (unless you've already done that?), but after asking for
this feature the customer has shown absolutely no interest in it
whatsoever so I guess it isn't important.

[...]