From: Martin Jambon <martin.jambon@ens-lyon.org>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Bug? Constraints get ignored in methods
Date: Wed, 01 Apr 2009 20:45:31 +0200 [thread overview]
Message-ID: <49D3B64B.6070505@ens-lyon.org> (raw)
In-Reply-To: <87wsa49xjr.fsf@frosties.localdomain>
Goswin von Brederlow wrote:
> Martin Jambon <martin.jambon@ens-lyon.org> writes:
>
>> Would the following work for you:
>
> No. Not just like this.
>
>> type 'a linked = {
>> data : 'a;
>> mutable next : < > linked option
>> }
>> (* constraint 'a = < .. > *)
>>
>> let create data next = {
>> data = data;
>> next = (next :> < > linked option)
>> }
>>
>> let set_next x y =
>> x.next <- (y :> < > linked option)
>>
>>
>> class s =
>> object
>> method s = "abc"
>> end
>>
>> class i =
>> object
>> method i = 123
>> end
>
> class s and i have no access to the linked type.
Yes, that's exactly what I'm trying to achieve.
They are contained in cells of the list.
You need to handle cells if you want to change the linkage.
> You could not remove
> a class s or i from the linked structure in O(1) from within class s
> or i. So linked would have to handle any function that might require
> altering the linked structure and pass parts of it to its data. But
> data is an unknown type so no method of it can be called.
< > is your base class. Replace it by whatever you like.
Martin
--
http://mjambon.com/
next prev parent reply other threads:[~2009-04-01 18:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 22:05 Goswin von Brederlow
2009-03-31 23:01 ` [Caml-list] " Martin Jambon
2009-03-31 23:12 ` Martin Jambon
2009-03-31 23:52 ` Goswin von Brederlow
2009-04-01 0:08 ` Goswin von Brederlow
2009-04-01 11:41 ` Martin Jambon
2009-04-01 15:57 ` Goswin von Brederlow
2009-04-01 18:45 ` Martin Jambon [this message]
2009-04-01 1:24 ` Peng Zang
2009-04-01 3:25 ` Goswin von Brederlow
2009-04-02 8:39 ` Jacques GARRIGUE
2009-04-03 20:53 ` Goswin von Brederlow
2009-04-06 4:30 ` Jacques Garrigue
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=49D3B64B.6070505@ens-lyon.org \
--to=martin.jambon@ens-lyon.org \
--cc=caml-list@yquem.inria.fr \
--cc=goswin-v-b@web.de \
/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