9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] asn.1 alternatives
Date: Sat, 11 Feb 2006 18:13:58 +0200	[thread overview]
Message-ID: <d5b3a737b170d017342c903924019112@proxima.alt.za> (raw)
In-Reply-To: <397b504b58a5f6c5ff602c2f19c4463a@plan9.bell-labs.com>

> and by the insistence of the comiler to code anything that
> has a known maximum length by a static array of that length.

I've never seen any of these mythical monsters, what do they really
look like?  Looking at the innumerable implementations of ASN.1
libraries, one is tempted to believe that enough effort has been
deployed in that direction.  Does any of the Open Source stuff
(Heimdal, OpenLDAP, OpenSSL, rdesktop, to name but a few) actually
ever re-use someone else's ASN.1 libraries?

++L



  reply	other threads:[~2006-02-11 16:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-11  0:10 [9fans] More 'Sam I am' quanstro
2006-02-11  3:01 ` jmk
2006-02-11 14:29   ` [9fans] asn.1 alternatives Charles Forsyth
2006-02-11 14:54     ` Sape Mullender
2006-02-11 16:13       ` lucio [this message]
2006-02-11 16:57       ` Skip Tavakkolian
2006-02-11 16:05     ` lucio
2006-02-11 17:52       ` Marina Brown
2006-02-11 16:28     ` Dan Cross
2006-02-11 16:53       ` Charles Forsyth
2006-02-11 22:47       ` Brantley Coile
2006-02-20  0:04     ` Harri Haataja
2006-02-11  6:04 ` ASN.1 (Was: [9fans] More 'Sam I am') lucio
2006-02-11  6:54   ` geoff
2006-02-11  8:06     ` lucio
2006-02-11  8:44       ` geoff
2006-02-11 12:10         ` lucio
2006-02-11  8:55     ` Steve Simon
2006-02-11  9:16       ` Bruce Ellis
2006-02-11  7:04   ` Skip Tavakkolian
2006-02-11  7:09     ` geoff
2006-02-11  7:53       ` lucio
2006-02-11  7:53       ` Skip Tavakkolian
2006-02-11 16:37 [9fans] asn.1 alternatives quanstro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d5b3a737b170d017342c903924019112@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).