Same here. 

And while I'm all too curious about the case conversion implementations, I'm in 
agreement it'd be a bad fit for the official distribution, and a major 
annoyance with clashing styles in shared code. 

Sent from my iPhone

On 12 Feb 2011, at 23:06, Matt Aimonetti <mattaimone...@gmail.com> wrote:

> It is not, we are just talking about conventions here. Personally I like to 
> use both casing approaches  so I can see the difference between obj-c APIs 
> and Ruby's.
> 
> - Matt
> 
> Sent from my iPhone
> 
> On Feb 12, 2011, at 16:44, Robert Payne <robertpa...@me.com> wrote:
> 
>> Is it extremely bad practice to use Camel Case in Ruby? At least for 
>> MacRuby? I have been mostly because I'm an Objective-C developer and it's 
>> what I'm used to as well as all of the Apple API are Camel Case and I didn't 
>> want to make the code spaghetti between the two.
>> 
>> -Robert
>> 
>> On 13/02/2011, at 1:41 PM, Matt Aimonetti wrote:
>> 
>>> Ok so I will play the mean team member and tell you that we are seriously 
>>> not considering supporting something like that as part of the base 
>>> implementation. Now that doesn't mean that you guys can't create a gem to 
>>> support that.
>>> 
>>> - Matt
>>> 
>>> Sent from my iPhone
>>> 
>>> On Feb 12, 2011, at 16:35, Rich Morin <r...@cfcl.com> wrote:
>>> 
>>>> At 11:01 AM +1300 2/13/11, Arthur Gunn wrote:
>>>>>> Ruby is extremely flexible.  I'm quite sure that some
>>>>>> metaprogramming  could be used to prototype something
>>>>>> for experimentation.
>>>>> 
>>>>> For the sake of experimentation then, here's some ruby
>>>>> code that does that: https://gist.github.com/824163
>>>>> 
>>>>> I don't think that implementing this in macruby would
>>>>> be a terrible idea. ...
>>>> 
>>>> I certainly don't think it's a terrible idea to TRY.  If
>>>> the results are uglier and/or more confusing than normal
>>>> MacRuby, we'll have learned something and can move on.
>>>> 
>>>> The next step, for someone with the time and energy, is
>>>> to pick a working MacRuby example and transliterate the
>>>> code to use this hack.  That will allow folks to assess
>>>> both the performance and the appearance of the hack.
>>>> 
>>>> -r
>>>> -- 
>>>> http://www.cfcl.com/rdm            Rich Morin
>>>> http://www.cfcl.com/rdm/resume     r...@cfcl.com
>>>> http://www.cfcl.com/rdm/weblog     +1 650-873-7841
>>>> 
>>>> Software system design, development, and documentation
>>>> _______________________________________________
>>>> MacRuby-devel mailing list
>>>> MacRuby-devel@lists.macosforge.org
>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>> 
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Reply via email to