From: Richard Jones <rich@annexia.org>
To: Jonathan Roewen <jonathan.roewen@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] enumerations & ioctls
Date: Thu, 30 Jun 2005 14:06:47 +0100 [thread overview]
Message-ID: <20050630130647.GA27372@furbychan.cocan.org> (raw)
In-Reply-To: <ad8cfe7e05063004144fa2b2ff@mail.gmail.com>
On Thu, Jun 30, 2005 at 11:14:07PM +1200, Jonathan Roewen wrote:
> Is the best way to achieve this with those polymorphic variants? And
> how much does this affect type safety?
A bigger worry is how this is all going to get linked together. Do
you link your device drivers, OS and programs together into a static
binary? Does the ioctl call cross over a memory/program boundary? Do
you want to add variants later, after the programs have been compiled,
or when you load new device drivers?
Rich.
--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com
next prev parent reply other threads:[~2005-06-30 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 11:14 Jonathan Roewen
2005-06-30 13:06 ` Richard Jones [this message]
2005-07-01 3:18 ` Jonathan Roewen
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=20050630130647.GA27372@furbychan.cocan.org \
--to=rich@annexia.org \
--cc=caml-list@yquem.inria.fr \
--cc=jonathan.roewen@gmail.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).