caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Milan Stanojević" <milanst@gmail.com>
To: Benoit Vaugon <benoit.vaugon@gmail.com>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] scanf question
Date: Mon, 23 Feb 2015 14:08:54 -0500	[thread overview]
Message-ID: <CAKR7PS9hEqFTfqFvANgzc5KHVCWdoHsq==1K9kEQF+HEp2W5Bw@mail.gmail.com> (raw)
In-Reply-To: <54E8E5C0.8070208@gmail.com>

Sorry for the delay, I just created the issue.
http://caml.inria.fr/mantis/view.php?id=6791

Benoit, can you attach your patch there?

On Sat, Feb 21, 2015 at 3:08 PM, Benoit Vaugon <benoit.vaugon@gmail.com> wrote:
> Oups, I confirm it is a bug appearing when we have separated formatting_gen
> to formatting_lit in the implementation of formats to handle Format
> constructions like "@{<%s>" and "@[<hov %d>" that collides with scanf
> constructions like "%s@{" and "%s@[". I attach a patch (+ 6 lines) that fix
> the problem, if somebody have time to integrate it...
>
> Sorry.
> Benoît.
>
>
>
> Le 21/02/2015 10:55, Gabriel Scherer a écrit :
>
> This seems to be a regression caused by the reimplementation of format
> strings in 4.02; some "stop after this character" indications are supported,
> but some other fail (when they correspond to valid Format specifications).
> Would you mind opening a but report ( http://caml.inria.fr/mantis/ )?
>
> On Fri, Feb 20, 2015 at 8:28 PM, Milan Stanojević <milanst@gmail.com> wrote:
>>
>> I want to parse a bash like sequence string, for example
>> "some-thing{1..20}", and extract the string before first { and then
>> two numbers inside.
>>
>> I tried this first
>> utop # Scanf.sscanf "some-thing{1..3}" "%s{%d..%d}" (fun s n1 n2 ->
>> s,n1,n2);;
>> Exception: End_of_file.
>>
>> Then I realized %s is special and needs scanning indication (character @).
>>
>> So I tried that but I get the same error
>> utop # Scanf.sscanf "some-thing{1..3}" "%s@{%d..%d}" (fun s n1 n2 ->
>> s,n1,n2);;
>> Exception: End_of_file.
>>
>> But if I use some other character as end of string indication then it
>> works.
>> utop # Scanf.sscanf "some-thingI{1..3}" "%s@I{%d..%d}" (fun s n1 n2 ->
>> s,n1,n2);;
>> - : bytes * int * int = ("some-thing", 1, 3)
>>
>> It seems '{' is somehow special but I can't find anything in the docs
>> about this.
>> Can someone explain what is going on here?
>>
>> Thanks!
>>
>>
>> p.s. At the end I solved my thing by using a range
>>
>> utop # Scanf.sscanf "some-thing{1..3}" "%[a-z-]{%d..%d}" (fun s n1 n2
>> -> s,n1,n2);;
>> - : bytes * int * int = ("some-thing", 1, 3)
>>
>> --
>> Caml-list mailing list.  Subscription management and archives:
>> https://sympa.inria.fr/sympa/arc/caml-list
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
>

      reply	other threads:[~2015-02-23 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 19:28 Milan Stanojević
2015-02-21  9:55 ` Gabriel Scherer
2015-02-21 20:08   ` Benoit Vaugon
2015-02-23 19:08     ` Milan Stanojević [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='CAKR7PS9hEqFTfqFvANgzc5KHVCWdoHsq==1K9kEQF+HEp2W5Bw@mail.gmail.com' \
    --to=milanst@gmail.com \
    --cc=benoit.vaugon@gmail.com \
    --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).