From: Remi VANICAT <vanicat@labri.u-bordeaux.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] 1) "open" in modules, 2) buffer enhancement.
Date: 17 Sep 2002 11:52:00 +0200 [thread overview]
Message-ID: <ya3wupl54fz.dlv@serveur5.labri.fr> (raw)
In-Reply-To: <Pine.LNX.4.21.0209171212350.15831-100000@vestra.bendery.md>
dmitry grebeniuk <gds@vestra.bendery.md> writes:
> hi
>
> 1)
> When I'm trying to compile such file:
> =============================================
> module M =
> struct
> let open () = print_string "open called\n"
>
> end;;
>
> M.open ();;
> =============================================
> I get errors like
>
> File "somefile.ml", line 3, characters 6-10:
> Syntax error
>
> It is the location of "open" function. I think it's a parser's bug - am
> I right?
No, you aren't : open is a reserved word in ocaml, you can't use it
as a name for something else.
> 2)
> I have modified standart buffer.ml and buffer.mli - I've added
> functions "get_line" (gets next line from buffer or raises Not_found
> if there's no line) and "get_block" (gets specified number of characters
> to pre-allocated string). I think these functions will be useful not only
> for me - can you add them (or their analogs) to standart distribution as
> Buffer's modification or as some new module (Fifobuff, for example)?
You should submit a feature wish bug with a patch to caml-bugs@inria.fr
--
Rémi Vanicat
vanicat@labri.u-bordeaux.fr
http://dept-info.labri.u-bordeaux.fr/~vanicat
-------------------
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
prev parent reply other threads:[~2002-09-17 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 9:32 dmitry grebeniuk
2002-09-17 9:52 ` Remi VANICAT [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=ya3wupl54fz.dlv@serveur5.labri.fr \
--to=vanicat@labri.u-bordeaux.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