From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <397b504b58a5f6c5ff602c2f19c4463a@plan9.bell-labs.com> To: 9fans@cse.psu.edu Subject: Re: [9fans] asn.1 alternatives Date: Sat, 11 Feb 2006 09:54:01 -0500 From: Sape Mullender In-Reply-To: <541ac7952476f11c319d81a7b9f7d516@terzarima.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: fbe913b0-ead0-11e9-9d60-3106f5b1d025 >>> > What are the alternatives? My pick is ASN.1, any time. Ha. I'm working on a UMTS base station (another, interesting tale of hard real time in Plan 9) and we're using an ASN.1 compiler that typically takes 30-bytes ASN.1 packed messages and decompresses them into 5 megabyte (yes, MEGA byte) C structs. Amazing. In the defense of ASN.1 I must say that this is not so much caused by ASN.1 as by the incredible amount of configurational possibilities in UMTS connections (almost none of which are or will be implemented by anybody), and by the insistence of the comiler to code anything that has a known maximum length by a static array of that length. Sape