Re: (CL Net SNMP) class precedence issue with SNMP + USOCKET-UDP
Brought to you by:
binghe
|
From: Chun T. (binghe) <bin...@gm...> - 2008-04-23 15:35:08
|
Hi, W. A. > >> And during these weeks, I have moved usocket-udp dir out of the snmp >> directory. The author of USOCKET seems forget my post or do not want >> to merge my UDP patch at this time. I think it OK. It's him who >> define >> a DATAGRAM-USOCKET in his own tree, not me. So I think in the future >> there will be a UDP support, if not from me, must from himself. > > Ok. I'll keep a closer eye on those libraries, too. > >> I tested it in SBCL, seems OK now. Try it and tell me your new >> result. > > I've updated everything - including SBCL to current - and I'm > back in business. Good. > > > In a somewhat different matter, I recently used CL-YACC on a > project of my own (http://code.google.com/p/cl-period/). It seems a > lot less esoteric than ZEBU. Is it capable of handling ASN.1, or did > you already decide against it for particular faults? Thank you for your notes. Actually I do use cl-yacc and cl-lexer on earlier version, and soon find too many conflicts which cannot shift by cl-yacc and then turn to ZEBU. There's a ASN.1 Book which talk about the parse of ASN.1: http://www.oss.com/asn1/dubuisson.html In this book, author said the ASN.1 BNF, when using a LALR parser, can produce hundred of conflicts. And this book suggest that, to parse full ASN.1, LALR parser isn't fit to use. Maybe LL parser is better. I'm still reading this book. I decide to finish reading first, then continue to think about my ASN.1 parse job. I think I need more knowledge of ASN.1, it's quite complex. Regards, Chun Tian (binghe) |