Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tokens ignored in top level command line after ';;' #6472

Closed
vicuna opened this issue Jun 27, 2014 · 5 comments
Closed

tokens ignored in top level command line after ';;' #6472

vicuna opened this issue Jun 27, 2014 · 5 comments

Comments

@vicuna
Copy link

vicuna commented Jun 27, 2014

Original bug ID: 6472
Reporter: jrrk101
Status: confirmed (set by @damiendoligez on 2014-07-08T08:49:30Z)
Resolution: open
Priority: low
Severity: tweak
Platform: x86_64
OS: OSX
OS Version: 10.9
Version: 3.12.1
Target version: later
Category: toplevel
Monitored by: @gasche

Bug description

After a certain statement ending in ;; the next tokens are ignored to end of line

Steps to reproduce

Jonathans-MacBook-Air:~ jrrk$ ocaml
        Objective Caml version 3.12.1

# let x = 65;; print_char (char_of_int x);;
val x : int = 65
# let x = 65;; hello xavier;;
val x : int = 65
#

Additional information

4.0 series seems affected. Seems to be a parser bug.

@vicuna
Copy link
Author

vicuna commented Jul 8, 2014

Comment author: @damiendoligez

It's been there for decades. Most people don't ever notice it.

@github-actions
Copy link

This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.

@github-actions github-actions bot added the Stale label May 11, 2020
@Octachron
Copy link
Member

This is more of a specification: The double semicolon ;; marks the end of the phrase sent to the toplevel.

@dbuenzli
Copy link
Contributor

It seems the same was reported in the still open #8813.

Personally I see it as an issue since you cannot cut and paste code from a script into a toplevel prompt and expect the same as if you had run the script.

@pw374
Copy link

pw374 commented Sep 17, 2020

This is more of a specification: The double semicolon ;; marks the end of the phrase sent to the toplevel.

How about we finally change this broken specification? :p

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants