| RFC: Can we remove these quirky grammar rules? [message #1402866] |
Fri, 18 July 2014 00:58  |
 Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Hi,
Boolean Attributes
---
The current grammar (and future parser) accepts an attribute operation
with the name being a Boolean value. Have you ever seen $true or $false
as parameters in a class, define or type?
i.e.
define foo ($true) {
}
foo { the_foo: true => false }
Can we get rid of this, it is bad enough that all other keywords can be
used (if, unless, case, class, define, etc. etc.)
Exported with whitespace
---
The grammar allows the two @@ in an exported resource expression
to be separated by whitepsace. (Both current and future parser).
i.e.
@
# yes, this works
#
@
notify { exported1: message => 'wat' }
@ /* its a little bit odd... */ @
notify { exported2: message => 'wat' }
This creates two exported notify resources.
Can we disallow whitespace between the two @ ?
- henrik
|
|
|
|
Powered by
FUDForum. Page generated in 0.03949 seconds
] 
Search
Help
Register
Login
Home
