caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Tom <tom.primozic@gmail.com>
To: skaller <skaller@users.sourceforge.net>
Cc: "Philippe Wang" <lists@philippewang.info>,
	caml-list@inria.fr, brogoff <brogoff@speakeasy.net>
Subject: Re: [Caml-list] About the O'Reilly book on the web
Date: Thu, 30 Nov 2006 19:20:44 +0100	[thread overview]
Message-ID: <c1490a380611301020j3e8e8d9et1ed48173ec22fca6@mail.gmail.com> (raw)
In-Reply-To: <1164853811.9646.2.camel@rosella.wigram>

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

>
>
> I wonder how far that could go? Is there anything in SML that
> you can't do in Ocaml with similar enough syntax that Camlp4
> could cope with it?
>

For me, personally, the question is not whether it can be done, but whether
I want it or not!

I am used to OCaml and don't want to switch to the unfamiliar, somewhat
strange syntax of SML. The webpage
http://www.ps.uni-sb.de/~rossberg/SMLvsOcaml.html<http://www.ps.uni-sb.de/%7Erossberg/SMLvsOcaml.html>gives
a (seemingly) thorough comparision between SML and OCaml (both syntax
and language features are compared). The following are only some of the
things I would only hardly be able to cope with:

characters written as #"J" instead of 'J',
fn x => e instead of fun x -> e
case of instead of match with
different declarations for values and functions (val, fun, in OCaml only
let)
datatype instead of type, plus eqtypes
strance multiple values definition

These are only minor differences, but if one is accustumed to one taste, one
would suffer when forcefully introduced to another one.

By the way, there are also some strange syntax structures introduced by
camlp4 that I don't like...

- Tom

[-- Attachment #2: Type: text/html, Size: 1404 bytes --]

  reply	other threads:[~2006-11-30 18:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-25 18:38 Francois Colonna
2006-11-27  9:07 ` [Caml-list] " Sebastien Ferre
2006-11-28 21:01   ` Philippe Wang
2006-11-28 22:33     ` Till Varoquaux
2006-11-28 22:47       ` Martin Jambon
2006-11-29  0:18         ` Philippe Wang
2006-11-29  1:48           ` Martin Jambon
2006-11-29 15:26             ` Philippe Wang
2006-11-29 17:52             ` Diego Olivier FERNANDEZ PONS
2006-11-29 17:25           ` brogoff
2006-11-29 18:10             ` Philippe Wang
2006-11-30  2:30               ` skaller
2006-11-30 18:20                 ` Tom [this message]
2006-12-01  3:21                   ` skaller
2006-12-01  6:48                     ` Tom
2006-11-29 21:20             ` Jon Harrop
2006-11-29 21:25               ` Till Varoquaux
2006-12-01  0:12               ` brogoff
2006-11-28 23:07       ` Philippe Wang

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=c1490a380611301020j3e8e8d9et1ed48173ec22fca6@mail.gmail.com \
    --to=tom.primozic@gmail.com \
    --cc=brogoff@speakeasy.net \
    --cc=caml-list@inria.fr \
    --cc=lists@philippewang.info \
    --cc=skaller@users.sourceforge.net \
    /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).