From: Jeremy Fincher <fincher.8@osu.edu>
To: Luc Maranget <luc.maranget@inria.fr>
Cc: malc <malc@pulsesoft.com>, caml-list@inria.fr
Subject: Re: [Caml-list] Is it really a non issue?
Date: Sat, 12 Jan 2002 00:31:50 -0500 [thread overview]
Message-ID: <20020112003150.A14334@functor.resnet.ohio-state.edu> (raw)
In-Reply-To: <200201111951.UAA0000013614@beaune.inria.fr>; from luc.maranget@inria.fr on Fri, Jan 11, 2002 at 08:51:12PM +0100
> > file a.mli:
> > val a : int \
> > val a : int |
> > ........... | n times
> > val a : int |
> > val a : int /
>
> At least, we should get those nasty 12 bytes back !
Wouldn't the most appropriate way to get those 12 bytes back be to remove the redundant data from the .mli file?
Jeremy
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
prev parent reply other threads:[~2002-01-12 5:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 21:57 malc
2002-01-11 15:42 ` Xavier Leroy
2002-01-11 19:51 ` Luc Maranget
2002-01-12 5:31 ` Jeremy Fincher [this message]
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=20020112003150.A14334@functor.resnet.ohio-state.edu \
--to=fincher.8@osu.edu \
--cc=caml-list@inria.fr \
--cc=luc.maranget@inria.fr \
--cc=malc@pulsesoft.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).