caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@ozemail.com.au>
To: Christian Rinderknecht <christian.rinderknecht@devinci.fr>
Cc: Ker Lutyn <ker527mail@yahoo.com>, caml-list@inria.fr
Subject: Re: [Caml-list] extending a type with Marshal
Date: 10 Oct 2003 20:38:15 +1000	[thread overview]
Message-ID: <1065782294.12729.87.camel@pelican> (raw)
In-Reply-To: <1065777556.21150.15.camel@lulu.devinci.fr>

On Fri, 2003-10-10 at 19:19, Christian Rinderknecht wrote:
> Hello Ker,
> 

> This kind of concept is already present (subtyping, versioning,
> relaying) in a specification language called Abstract Syntax Notation
> One (ASN.1), and, at least, easily supported by one of its encoding rule
> called Basic Encoding Rule (BER).

There is also a FFAU (free for any use) open source ASN 1.1 library
around somewhere for C++, and tools for compiling ASN specifications
(into C++ sources). I can't give a reference, sorry, I ran into
these beasts while working at a (now defunct) telco. I imagine
google can find it though :-)



-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2003-10-10 10:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08 21:22 Ker Lutyn
2003-10-08 21:38 ` Richard Jones
2003-10-08 21:54 ` Peter Jolly
2003-10-10  8:37 ` skaller
2003-10-10  9:19 ` Christian Rinderknecht
2003-10-10 10:38   ` skaller [this message]
2003-10-10 17:19   ` Martin Berger
2003-10-12  9:01   ` William Chesters
2003-10-12  9:06     ` William Chesters
2003-10-12 19:45     ` About ASN.1 and network encoding (was: Re: [Caml-list] extending a type with Marshal) David MENTRE

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=1065782294.12729.87.camel@pelican \
    --to=skaller@ozemail.com.au \
    --cc=caml-list@inria.fr \
    --cc=christian.rinderknecht@devinci.fr \
    --cc=ker527mail@yahoo.com \
    /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).