caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: John Max Skaller <skaller@ozemail.com.au>
To: Pierre Weis <Pierre.Weis@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: compilation of lablgl examples.
Date: Fri, 09 Feb 2001 03:33:07 +1100	[thread overview]
Message-ID: <3A82CA43.797E84C@ozemail.com.au> (raw)
In-Reply-To: <200102072202.XAA05588@pauillac.inria.fr>

Pierre Weis wrote:

> May be it is my understanding of English which is bad, not your way to
> write it :(

	I tend to write abbreviated idiomatic script flavoured by
my native language (Strine :-)
 
> >       For example, something like this happens:
> > the type of a function declaration in the Abstract Syntax Tree is:
> >
> >   | AST_function of id_t * parameter_t list * typecode_t * statement_t
> > list
> >
> > which is converted to:

[]

> > which is converted to:
> >
> >   | BBDCL_function of   bparameter_t list * btypecode_t * int list *
> > bexe_t list * name_map_t
> 
> This is very often considered good practice. However, I agree with you
> that is can be heavy to code. 

	Static typing today is not strong enough to express the actual
typing, so there is always some compromise/balance between static and
dynamic checking. I find it is difficult to engineer a good balance.
Ideally, I could change that balance easily, however it is even harder
to 'meta-engineer' code so that it is easy to change.

> Sometimes you can use polymorphism to
> help for instance defining
> 
> | Function of 'parameter list * typecode_t * 'b
> 
> could be used to modelize both
> | DCL_function of   parameter_t list * typecode_t * asm_t list
> | BDCL_function of   bparameter_t list * btypecode_t * int list *
>  exe_t list * name_map_t

	I'm not sure how: these two declarations are for variant 
components of _distinct_ types.

[Try using variants .. ]
 
> You should try on a small example, not on a huge optimizing compiler
> for a full fledged language!

	Thats a good idea .. although I must say that Felix is not (yet)
a 'huge' or  'optimising' compiler :-)

-- 
John (Max) Skaller, mailto:skaller@maxtal.com.au
10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850
checkout Vyper http://Vyper.sourceforge.net
download Interscript http://Interscript.sourceforge.net



  parent reply	other threads:[~2001-02-08 19:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-03 22:35 Peter Ronnquist
2001-02-05 17:41 ` John Max Skaller
2001-02-06 15:55   ` Pierre Weis
2001-02-07  1:28     ` John Max Skaller
2001-02-07 22:02       ` Pierre Weis
2001-02-08  5:55         ` Patrick M Doane
2001-02-08 16:33         ` John Max Skaller [this message]
2001-02-08 19:15           ` Pierre Weis
2001-02-08  2:06       ` Jacques Garrigue
2001-02-06  2:34 ` Jacques Garrigue
2001-02-06 18:00   ` Sven LUTHER
2001-02-07 12:09   ` Peter Ronnquist
2001-02-08  7:22     ` Sven

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=3A82CA43.797E84C@ozemail.com.au \
    --to=skaller@ozemail.com.au \
    --cc=Pierre.Weis@inria.fr \
    --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).