-
Notifications
You must be signed in to change notification settings - Fork 274
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
"case-sensitive" and "case-insensitive" are easy to mix up #265
Comments
Using "not case-sensitive" is probably better, but note that this language spec is severely out of date and does not cover any recent changes/additions to the language. |
@Girgias But it is still the official language specification? So I would create a pull request for this change. |
This language specification is, AFAIK, unmaintained. From what I seem to remember from things I've been told, this was mainly created by Facebook to come up with some common ground for their implementation of HHVM to be compatible with PHP. So this is probably only going to be good for parsing requirements up to PHP 7.0 maybe 7.1, and thus you won't have things like |
Hi,
I am following the specification to implement a PHP lexer.
I noticed that there is a mix of the wording "not case-sensitive" and "case-insensitive".
Would it make sense to just use "not case-sensitive" so that it is more clear?
In my opinion "case-sensitive" and "case-insensitive" is easier to accidentally mix it up.
Examples:
php-langspec/spec/09-lexical-structure.md
Line 417 in ca697b4
php-langspec/spec/06-constants.md
Line 37 in ca697b4
The text was updated successfully, but these errors were encountered: