Opened 11 years ago
Closed 10 years ago
#593 closed defect (fixed)
WCPS not case sensitive on some keywords
Reported by: | Piero Campalani | Owned by: | Bidesh Thapaliya |
---|---|---|---|
Priority: | major | Milestone: | 9.0.x |
Component: | petascope | Version: | development |
Keywords: | case sensitivity metadataexpr | Cc: | mantovani@…, Vlad Merticariu, Alex Dumitru |
Complexity: | Easy |
Description
Despite the correct grammar definition in petascope.wcps.grammar.wcps.g
, some WCPS keywords are case-sensitive:
for c in (eobstest) return crsset(c) -> Invalid coverage Expression, next node: crsset for c in (eobstest) return crsSet(c) -> OK for c in (eobstest) return ideNTifier(c) -> Invalid coverage Expression, next node: ideNTifier for c in (eobstest) return ideNTifier(c) -> OK
This is apparently affecting metadata expressions only, but I did not make an exhaustive test.
for c in (eobstest) return encode( - add (c[Lat(0), Long(51)]) + aDd (c[Lat(0), Long(51)]) , "csv") -> OK
Case-sensitivity to all keywords should be evaluated, and test(s) added.
Change History (5)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Yes exactly, this ticket must be all about some replacement of equals
to .equalsIgnoreCase
.
comment:3 by , 11 years ago
Cc: | added |
---|
comment:4 by , 10 years ago
Milestone: | Future → 9.0.x |
---|---|
Owner: | changed from | to
Status: | new → assigned |
comment:5 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
patch submited.
changeset:0ca548
Note:
See TracTickets
for help on using tickets.
There is most probably an
equals
test somewhere in the WCPS code itself, rather than in the parser.