-
Notifications
You must be signed in to change notification settings - Fork 11
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
[Issue] Asdoc bug treats "/" within RegExp literals incorrectly as a RegExp delimiter #3246
Comments
I would say this works as expected... the specification here is ECMA-262, 3rd Ed, so if you look at section 7.8.5 you get the grammar for a regular expression literal:
So https://www.ecma-international.org/wp-content/uploads/ECMA-262_3rd_edition_december_1999.pdf |
I see… But there's a matter that there is a behavioral inconsistency between the ActionScript 3 compiler and asdoc here. Shouldn't asdoc as an annotation tool, prioritize the language itself? Thanks. |
Ah, I may have misunderstood what you were originally reporting then... I wasn't referring to asdoc, just looking at the regular expression / ActionScript code that you posted. And oddly, that RegExp compiles fine (well, in terms of the AS3 compiler) when I try that..? Will need to check what should happen here from the compiler perspective as well as from the asdoc side.. |
Problem Description
AIR SDK version: 51.0.1.1
When generating document using asdoc, the forward slash character
/
withinRegExp
literals is mistakenly treated as the delimiter for theRegExp
, which leads to a compilation failure.Steps to Reproduce
Code Example:
(This example is because the bug found when I'm developing a email client library…)
Known Workarounds
Escape the slash
/
with a backslash\
in RegExp literals, although this should not be necessary according to standards.The text was updated successfully, but these errors were encountered: