[
https://issues.apache.org/jira/browse/THRIFT-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844167#action_12844167
]
Bryan Duxbury commented on THRIFT-434:
--------------------------------------
I can see why you're torn. I think we need to make a decision if we're going to
be making exceptions for various languages, or if instead we should be making
sure that we have a compiler that produces code that works in all of our target
languages.
Personally, I'd opt to have my vocabulary restricted if I knew it meant that I
could actually compile the code in any of the supported languages without
running into goofball stuff like this. Maybe we should make a compiler switch
to warn instead of break about reserved words.
> ruby compiler should warn when a reserved word is used
> ------------------------------------------------------
>
> Key: THRIFT-434
> URL: https://issues.apache.org/jira/browse/THRIFT-434
> Project: Thrift
> Issue Type: Improvement
> Components: Compiler (General), Compiler (Ruby)
> Reporter: Michael Stockton
> Assignee: Michael Stockton
> Priority: Minor
> Fix For: 0.3
>
> Attachments: thrift-434-v2.patch, thrift-434-v3.patch,
> thrift-434.patch
>
>
> It would be nice if the compiler would warn or fail when a reserved word is
> used as a struct name, service name or field name. The following names should
> be avoided:
> __FILE__
> and
> def
> end
> in
> or
> self
> unless
> __LINE__
> begin
> defined?
> ensure
> module
> redo
> super
> until
> BEGIN
> break
> do
> false
> next
> rescue
> then
> when
> END
> case
> else
> for
> nil
> retry
> true
> while
> alias
> class
> elsif
> if
> not
> return
> undef
> yield
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
