caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Michael Wohlwend <micha-1@fantasymail.de>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] state pattern...
Date: Tue, 28 Jun 2005 01:23:54 +0200	[thread overview]
Message-ID: <200506280123.55251.micha-1@fantasymail.de> (raw)
In-Reply-To: <3fce1487ee8fd9f28edbe70276980346@wetware.com>

On Monday 27 June 2005 00:13, james woodyatt wrote:
> I tend to work in the functional style first, then transfer what I've
> done into imperative style if there is a performance gain to be had by
> it.  Here's what I would do to make something like what you want:
> ...

I have modified the code, so that some method(s) of the state classes get the 
context class as parameter; I think it took me 3 hour to get the type 
definitions working :-)

Can this be done simpler? It works, although I don't completly understand all 
of it :-) 
-------------------------
class type param =
 object 
 method name : string
 end

class type state =
 object('self)
  method show: 'a. (#param as 'a) -> unit
  method next: 'self
 end

class ['state] context s =
 object (this:'self)
 val name = "context"
 val state_: #state = s 
 method name = name
 method show: unit = state_#show this
 method run = {< state_ = state_#next >}
 end

class state1 = object (this)
 method show: 'a. (#param as 'a) -> unit = fun c -> print_endline ("state1 of 
" ^ c#name)
 method next = new state2 
end
and state2 = object (this)
 method show: 'a. (#param  as 'a) -> unit = fun c -> print_endline ("state2 of 
" ^ c#name) 
 method next = new state1 
end;;

let c = new context (new state1) in
c#show;
let c = c#run in
c#show

----------------------------


thanks,
 Michael


  parent reply	other threads:[~2005-06-27 23:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-26 19:57 Michael Wohlwend
2005-06-26 22:13 ` [Caml-list] " james woodyatt
2005-06-26 22:45   ` Michael Wohlwend
2005-06-27 23:23   ` Michael Wohlwend [this message]
2005-06-28  0:54     ` Jacques Garrigue
2005-06-28 12:24       ` Michael Wohlwend
2005-06-28 13:20         ` 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=200506280123.55251.micha-1@fantasymail.de \
    --to=micha-1@fantasymail.de \
    --cc=caml-list@yquem.inria.fr \
    /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).