caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Basile STARYNKEVITCH <basile@starynkevitch.net>
To: Eric Merritt <cyberlync@yahoo.com>
Cc: Dan Andersson <rhq093s@tninet.se>, caml-list@inria.fr
Subject: Re: [Caml-list] ocaml embedded scripting language
Date: Tue, 17 Dec 2002 09:37:17 +0100	[thread overview]
Message-ID: <15870.57917.942590.759421@hector.lesours> (raw)
In-Reply-To: <20021217030244.64549.qmail@web40803.mail.yahoo.com>

>>>>> "Eric" == Eric Merritt <cyberlync@yahoo.com> writes:

    Eric> Everyone, Well I decided to take dans advice and do a simple
    Eric> forth like implementation. 

I still suggest carefully looking at N.Ramsey's Lua implementation

    Eric> Overall it doesn't seem like its
    Eric> going to be difficult at all. I have run into a small
    Eric> snag. As a side note I have already decided that this is
    Eric> note possible, this is just a last ditch to see if there is
    Eric> a solution.

    Eric>  It has to do with the type system more then anything
    Eric> else. I use a stack to handle data that the interpreted
    Eric> process is manipulating. I provide a specific set of words
    Eric> that this forth like language will use to manipulate the
    Eric> stack. Of course, stacks may only be of a single type 'a. So
    Eric> if declare a new type to be

    Eric>  type some_type = Int of int | Float of float | Word of
    Eric> string

    Eric> Them my stack is some_type Stack.t

    Eric>  Ok this is all fine and dandy, until a few months from now
    Eric> when I want to add a new type say File of
    Eric> Unix.file_descr. 

Did you consider using variant or classes?

-- 

Basile STARYNKEVITCH         http://starynkevitch.net/Basile/ 
email: basile<at>starynkevitch<dot>net 
alias: basile<at>tunes<dot>org 
8, rue de la Faïencerie, 92340 Bourg La Reine, France
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2002-12-17  8:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10  8:30 [Caml-list] [Q] opengl bindings without tcl/tk SooHyoung Oh
2002-12-10  8:37 ` Jacques Garrigue
2002-12-10 11:17   ` Olivier Andrieu
2002-12-10 13:37     ` Jean-Christophe Filliatre
2002-12-10 14:54   ` Eric Merritt
2002-12-13 20:02     ` Issac Trotts
2002-12-13 21:06       ` Eric Merritt
2002-12-14  1:52       ` [Caml-list] ocaml embedded scripting language Eric Merritt
2002-12-14 18:56         ` Norman Ramsey
2002-12-16 14:49           ` Eric Merritt
2002-12-15 15:08         ` Dan Andersson
2002-12-16 14:51           ` Eric Merritt
2002-12-17  3:02           ` Eric Merritt
2002-12-17  8:37             ` Basile STARYNKEVITCH [this message]
2002-12-17 14:26               ` Eric Merritt
2002-12-17 21:27                 ` Dan Andersson
2002-12-18 19:51                   ` Norman Ramsey
2002-12-17 20:26             ` Issac Trotts
2002-12-18 19:55               ` Norman Ramsey
2002-12-10  8:38 ` [Caml-list] [Q] opengl bindings without tcl/tk Sven Luther
2002-12-10 10:32 ` Nickolay Semyonov-Kolchin

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=15870.57917.942590.759421@hector.lesours \
    --to=basile@starynkevitch.net \
    --cc=caml-list@inria.fr \
    --cc=cyberlync@yahoo.com \
    --cc=rhq093s@tninet.se \
    /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).