caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: issac@ucdavis.edu (Issac Trotts)
To: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] ocaml embedded scripting language
Date: Tue, 17 Dec 2002 12:26:18 -0800	[thread overview]
Message-ID: <20021217202618.GA491@boson.ucdavis.edu> (raw)
In-Reply-To: <20021217030244.64549.qmail@web40803.mail.yahoo.com>

Eric Merritt wrote:
> Everyone,
> 
> 
>  Well I decided to take dans advice and do a simple
> forth like implementation. Overall it doesn't seem
> like its going to be difficult at all. I have run into
> a small snag. As a side note I have already decided
> that this is note possible, this is just a last ditch
> to see if there is a solution. 
> 
>  It has to do with the type system more then anything
> else. I use a stack to handle data that the
> interpreted process is manipulating. I provide a
> specific set of words that this forth like language
> will use to manipulate the stack. Of course, stacks
> may only be of a single type 'a. So if declare a new
> type to be
> 
>  type some_type = Int of int | Float of float | Word
> of string 
> 
> Them my stack is some_type Stack.t 
> 
>  Ok this is all fine and dandy, until a few months
> from now when I want to add a new type say File of
> Unix.file_descr. The word implementations to support
> the new type wouldn't actually be a problem. However,
> extending the type seems to be impossible.
> 
>  The only way I can see to do this at the moment is to
> modify the type and recompile the whole system. That

OCaml can be used as a scripting language, so this doesn't
have to be a problem.  Just use the #load, #directory, and
#use toplevel directives, and little or no compiling is 
necessary.  However this seems to require restructuring the
program, so maybe it won't be worth it.

Another way would be to have a facility for adding 
new types within your extension language.
If you add a start-up file (something like ~/.my_extension_lang_rc)
then you can load all your favorite types whenever it runs.

Issac
-------------------
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


  parent reply	other threads:[~2002-12-18 12:41 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
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 [this message]
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=20021217202618.GA491@boson.ucdavis.edu \
    --to=issac@ucdavis.edu \
    --cc=caml-list@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).