caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: CREGUT Pierre FTRD/DTL/LAN <pierre.cregut@rd.francetelecom.fr>
To: caml-list@inria.fr
Subject: Re: Help with toplevel
Date: Fri, 9 Feb 2001 15:55:33 +0100	[thread overview]
Message-ID: <20010209155533.A16985@lat4149.ftrd> (raw)
In-Reply-To: =?iso-8859-1?Q?=3C200102081840=2ETAA09086=40pauillac=2Einria=2Efr=3E=3B_?= =?iso-8859-1?Q?from_Pierre=2EWeis=40inria=2Efr_on_jeu=2C_f=E9v_08=2C_200?= =?iso-8859-1?Q?1_at_07:40:46_+0100?=

> 
> Then type in (don't forget the initial # sign, that
> indicates a directive)
> 

Yes but all beginers do the same mistake. May be the toplevel prompt should be
changed to something else (different from #). This would not change our life
but there would be less newcommers asking where is the use, cd, quit and al
function.

On a similar topic, the behaviour of printf that cannot be used in a partial
application should be pointed out more strongly in the manual (red huge bold font)
and more explicitely than the cryptic sentence :

If too few arguments are provided, printing stops just before converting the 
first missing argument. 

Again a student lost a day this week trying to understand why he did not get parts of
his results on the screen. Sure he will not do the mistake again !
 
Another solution would be to eta expand printf functions after it has been typed
This would be externaly cleaner but may be not internaly. But, the code for 
supporting this function in  the compiler is already so bloated anyway.

Pierre Crégut

-- 
Pierre Cregut - pierre.cregut@rd.francetelecom.fr - +33 2 96 05 16 28
FTR&D - DTL/MSV - 2 avenue Pierre Marzin - 22307 Lannion Cedex - France



      reply	other threads:[~2001-02-09 16:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-07 21:51 Bauer, Robert
2001-02-08 18:40 ` Pierre Weis
2001-02-09 14:55   ` CREGUT Pierre FTRD/DTL/LAN [this message]

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=20010209155533.A16985@lat4149.ftrd \
    --to=pierre.cregut@rd.francetelecom.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).