From: skaller <skaller@users.sourceforge.net>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] proposed extenion to patterns
Date: Fri, 09 Mar 2007 22:19:41 +1100 [thread overview]
Message-ID: <1173439181.22738.28.camel@rosella.wigram> (raw)
In-Reply-To: <200703091008.03855.jon@ffconsultancy.com>
On Fri, 2007-03-09 at 10:08 +0000, Jon Harrop wrote:
> On Friday 09 March 2007 02:02, skaller wrote:
> > Any comments on this idea?
>
> Every now and again I want that, but I think there are much bigger gains to be
> had elsewhere
Agreed.
> and I'd rather those were addressed first.
Development in sequence of importance isn't the only model.
When working with Stroustrup and the C++ extensions subgroup,
on the (long list) of proposals, we'd vote.
Then we'd deal with the 3 proposals at the top of the list --
and the three at the bottom :)
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
prev parent reply other threads:[~2007-03-09 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 2:02 skaller
2007-03-09 7:34 ` [Caml-list] " Tom
2007-03-09 10:08 ` Jon Harrop
2007-03-09 11:19 ` skaller [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=1173439181.22738.28.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.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).