Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Matt Gushee <mgushee@havenrock.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Snd question
Date: Tue, 16 Aug 2005 23:17:44 +1000	[thread overview]
Message-ID: <1124198264.13635.25.camel@localhost.localdomain> (raw)
In-Reply-To: <43011A10.4090108@havenrock.com>

[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]

On Mon, 2005-08-15 at 16:41 -0600, Matt Gushee wrote:
> Anu Engineer wrote:
> 
>  > Please forgive me if my question is very naïve, I am very new to 
> Ocaml. I was
> 
>  > wondering why snd returns an  error when I use it with more than 2 
> elements, why
> 
>  > not return the rest of the list when I apply to something larger than 
> a pair ?
> 
> 
> Your question shows your misunderstanding: snd operates on tuples, not 
> lists. 

I think the original question really meant:

Why aren't "fst" and "snd" properly generic??

For example this simply *should* work:

	snd (1,2,3)

and even pattern matching can't handle it:

	match e with (h,t,...) -> 

also should work. Felix actually supports this ugly generic
tuple projection operator:

	(1,2.1).(1)   // generic n'th of tuple
	(1,2.1,3).(1) // n must be compile time constant

and even:

var i:int;
for_each {i=0;} {i<3} {++i;} {
  print (1,2,3).[i]; // run time indexing
  endl;
};

because a tuple of all the same type is an array,
but as yet I haven't found a way to make ... work in 
pattern matches. 

It would actually be nice to have more general support
for polyadic tuple management: for example thinking about
obtaining a slice of a tuple, or concatenating two tuples,
suggests that just getting the n'th component is special case.

This kind of thing can actually be done in a hacky way
within limits with C++ template meta-programming.

A more general mapping from a list of types (at compile time)
representing tuples should be possible: any list operation
on types is a run-time operation on values. Unfortunately
I doubt camlp4 can handle that, since it is dealing with untyped
terms. Perhaps MetaOcaml can do it?

I would love to do this in Felix .. but it requires dynamic loading.

-- 
John Skaller <skaller at users dot sourceforge dot net>


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-08-16 13:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 22:05 Anu Engineer
2005-08-15 22:41 ` [Caml-list] " Matt Gushee
2005-08-16  8:08   ` sejourne kevin
2005-08-16 13:17   ` skaller [this message]
2005-08-16 16:16     ` Julian Brown
2005-08-16 17:18       ` [Caml-list] " Alan Falloon
2005-08-17  6:15       ` skaller
2005-08-16 16:34     ` [Caml-list] " Jon Harrop
2005-08-16 18:16       ` Richard Jones
2005-08-16 21:42         ` Jon Harrop
2005-08-17  6:55           ` skaller
2005-08-18  8:20             ` Andrej Bauer
2005-08-18 17:51               ` skaller
2005-08-19  7:50                 ` Andrej Bauer
2005-08-17 12:19         ` Alain Frisch
2005-08-17 17:21           ` skaller
2005-08-17 23:08           ` Martin Jambon
2005-08-17  6:28       ` skaller
2005-08-20 14:31     ` Brian Hurt

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=1124198264.13635.25.camel@localhost.localdomain \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@inria.fr \
    --cc=mgushee@havenrock.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