You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 7267 Reporter:@bobzhang Status: acknowledged (set by @damiendoligez on 2016-09-27T14:12:28Z) Resolution: open Priority: normal Severity: feature Target version: later Category: lexing and parsing Related to:#7296 Monitored by:@yallop
Bug description
The use case is that when compile OCaml to JS backend via bucklescript(I think it applies to js_of_ocaml too), some JS objects are not expressible due to some superficial issues (not a valid syntax)
for example in method name, you can not start with capital letter
object method Capital_is_not_legal_name : xx end
Another part is that in JS, hypen operator (-) is also used a lot.
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.
Original bug ID: 7267
Reporter: @bobzhang
Status: acknowledged (set by @damiendoligez on 2016-09-27T14:12:28Z)
Resolution: open
Priority: normal
Severity: feature
Target version: later
Category: lexing and parsing
Related to: #7296
Monitored by: @yallop
Bug description
The use case is that when compile OCaml to JS backend via bucklescript(I think it applies to js_of_ocaml too), some JS objects are not expressible due to some superficial issues (not a valid syntax)
for example in method name, you can not start with capital letter
object method Capital_is_not_legal_name : xx end
Another part is that in JS, hypen operator (-) is also used a lot.
It would be nice that in OCaml, we introduce a special token like common lisp does(http://www.lispworks.com/documentation/lw70/CLHS/Body/02_cd.htm)
so you can have |Content-Type| as a valid method name
The text was updated successfully, but these errors were encountered: