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

directory misuse hangs ocamlwin #2741

Closed
vicuna opened this issue Apr 9, 2001 · 3 comments
Closed

directory misuse hangs ocamlwin #2741

vicuna opened this issue Apr 9, 2001 · 3 comments
Labels

Comments

@vicuna
Copy link

vicuna commented Apr 9, 2001

Original bug ID: 333
Reporter: administrator
Status: closed
Resolution: not a bug
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)

Bug description

Full_Name: Sean Levin
Version: 3.01
OS: Win2000 Server
Submission from: 24-168-82-233.nyc.rr.com (24.168.82.233)

I type:
#directory "d:\ocaml\lib\labltk";;
and things work fine.

I type:
#directory "d:\ocaml\lib\labltk";;
with that extra backslash at the end and ocamlwin stops interperating.
I can still use menus and type, but I am no longer able to do anything or
#quit;;

I must kill the application in order to exit.

@vicuna
Copy link
Author

vicuna commented Apr 9, 2001

Comment author: administrator

just an open string.

@vicuna vicuna closed this as completed Apr 9, 2001
@vicuna
Copy link
Author

vicuna commented Apr 9, 2001

Comment author: administrator

Full_Name: Sean Levin

I type:
#directory "d:\ocaml\lib\labltk";;
with that extra backslash at the end and ocamlwin stops interperating.

That's just another instance of the (*) problem:
'"' is an escape sequence for the character double-quote.
The interpreter is not stuck. It is just waiting for you to close your
string.

Would this need another special prompt, like for comments?
Also, is it really a good idea to parse "\l" as '\' and 'l', while
"\n" is parsed as the newline character?

Jacques Garrigue

@vicuna
Copy link
Author

vicuna commented Apr 10, 2001

Comment author: administrator

Would this need another special prompt, like for comments?
Also, is it really a good idea to parse "\l" as '\' and 'l', while
"\n" is parsed as the newline character?

I don't know. ANSI C leaves this undefined; gcc accepts it but emits
a warning; Java disallows it entirely...

  • Xavier Leroy

@vicuna vicuna added the bug label Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant