[ https://issues.apache.org/jira/browse/THRIFT-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839017#comment-15839017 ]
James E. King, III commented on THRIFT-472: ------------------------------------------- Do you think this still occurs? > Don't allow unquoted strings at all > ----------------------------------- > > Key: THRIFT-472 > URL: https://issues.apache.org/jira/browse/THRIFT-472 > Project: Thrift > Issue Type: Improvement > Components: Compiler (General) > Affects Versions: 0.1 > Reporter: Bryan Duxbury > Priority: Minor > > If you are working with constants in Thrift and happen to write a string > without quotes, the compiler will warn you about using unquoted strings, but > it's not an error. This can lead to some confusing debugging if you actually > mistyped an enum value's constant or the like. > I propose that rather than having such a thing as an "unquoted string", we > just check if it's a constant, and if not error out. It seems like it would > decrease the potential complexities without really sacrificing any > functionality. -- This message was sent by Atlassian JIRA (v6.3.4#6332)