Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Lauri Alanko <la@iki.fi>
To: caml-list@inria.fr
Subject: [Caml-list] What are "Language extensions"?
Date: Sat, 26 Mar 2011 03:12:09 +0200	[thread overview]
Message-ID: <20110326011208.GA3915@melkinpaasi.cs.helsinki.fi> (raw)

In the O'Caml reference manual, the actual language specification is
split into two parts, "The Objective Caml language" and "Language
extensions". I'm curious as to what this division indicates about the
status of different features of the language. The manual itself
doesn't help much, since the extensions chapter only opens with:

	This chapter describes language extensions and convenience
	features that are implemented in Objective Caml, but not
	described in the Objective Caml reference manual.

In other words, "this chapter is for the stuff that isn't in the
previous chapter". Not very informative.

What, then, does it mean for something to be an extension instead of a
part of the "basic" language? Is it about backwards compatibility
(e.g. the basic language is guaranteed to work with every 3.x
release)? Or about forward compatibility (e.g. some extensions might
not be supported in a future 3.x release)? Or about stability? Will
some of the extensions eventually be incorporated into the "basic"
language?

The structure of the manual clearly implies that I as a programmer
should take into account that a feature is an "extension". I just
have no idea what I should do with that knowledge.


Lauri

             reply	other threads:[~2011-03-26  1:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26  1:12 Lauri Alanko [this message]
2011-03-26  4:07 ` Mike Lin
2011-03-26  4:30   ` Steven Shaw
2011-03-26  7:23     ` Martin Jambon
2011-03-27 18:13 ` Xavier Leroy

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=20110326011208.GA3915@melkinpaasi.cs.helsinki.fi \
    --to=la@iki.fi \
    --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