From: Mathieu B. <ma...@ar...> - 2006-02-19 03:45:58
|
On Thu, 9 Feb 2006, Charlie Savage wrote: > By the way, is there any order to the list of keywords in rubykw.swg? =20 > It would be much easier if it was alphabetized. I've done that, but > don't want to check in anything that might break something. Also the > file treats BEGIN/END as keywords and begin/end as builtins. Not sure > what the difference really is, but it should probably be reversed. I don't understand why SWIG should bother about keywords, builtins, and=20 the difference between them. In all cases, what it means is that I can't=20 omit the "self." prefix for special names. I don't think that Ruby's parsers make much of a difference between=20 BEGIN/begin/END/end as far as allowed method-names go. Or is it about class names and other "constants"? Then I agree it's more=20 complicated to have constants named like reserved words, because you have= =20 to call Module#const_set and #const_get and then you've got to know=20 which Module to call them on and the shortest way to do this in a=20 position independent way is Module.nesting[0]||::Object, which sort of=20 explains why generally people avoid naming constants like reserved words=20 in Ruby... > def under > puts 'unless' > end Double typo. That should have been: def undef; puts 'undef' end _ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - t=E9l:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montr=E9al QC Canada |