On Fri, Feb 11, 2011 at 4:08 PM, Rich Morin wrote:
> At 6:09 PM -0200 2/11/11, Caio Chassot wrote:
>> On 2011-02-11, at 15:25 , Matt Aimonetti wrote:
>>>
>>> Magically converting a snake_case method call to a
>>> CamelCase method dispatch is bad for peformance
>>> and documentation.
>
> It's not c
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 wrote:
> It is not,
Robert Payne 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
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 wrote:
> Is it extremely bad practice to use Camel Case in Rub
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
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
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
>
> 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 wou
On Feb 11, 2011, at 2:08 PM, Rich Morin wrote:
> The question of documentation is also somewhat iffy.
> There is already a difference in appearance between
> the ObjC and MacRuby calling syntaxes. Would merely
> allowing (ie, not requiring) the use of snake_case
> make this much problem much wor
At 6:09 PM -0200 2/11/11, Caio Chassot wrote:
> On 2011-02-11, at 15:25 , Matt Aimonetti wrote:
>>
>> Magically converting a snake_case method call to a
>> CamelCase method dispatch is bad for peformance
>> and documentation.
It's not clear to me that there would be a significant
performance impac
On 2011-02-11, at 15:25 , Matt Aimonetti wrote:
>
> Magically converting a snake_case method call to a CamelCase method dispatch
> is bad for peformance and documentation.
I'm not suggesting that this be done as part of MacRuby, but should one want to
go ahead on their on…
Wouldn't it be possib
Magically converting a snake_case method call to a CamelCase method dispatch
is bad for peformance and documentation.
I believe that Laurent addressed that topic a few times already but I might
be wrong.
There is currently no plan to support that approach in MacRuby.
- Matt
On Fri, Feb 4, 2011 at
At 6:57 PM -0200 2/4/11, Caio Chassot wrote:
> On 2011-02-04, at 01:26 , Rich Morin wrote:
> I'm sure the situation in JRuby land is worse, but
> generally, using Cocoa stuff from MacRuby feels
> enough like ruby, save for the HorridCamelCase,
> but I've gotten used to that.
Interestingly, JRuby d
I am a newbie when it comes to using Cocoa (and by no means a Ruby expert), so
I've only seen a few patterns in Cocoa stuff.
A pattern I tried the other day was to use a procs where Cocoa wants a callback
object/method for delegation. This is as close to using blocks as I can get
when they don'
On 2011-02-04, at 01:26 , Rich Morin wrote:
>
> One of my concerns with both MacRuby and JRuby is
> that the resulting code doesn't look much like Ruby.
I'm sure the situation in JRuby land is worse, but generally, using Cocoa stuff
from MacRuby feels enough like ruby, save for the HorridCamelCa
One of my concerns with both MacRuby and JRuby is
that the resulting code doesn't look much like Ruby.
As Mark Twain put it:
... If man could be crossed with the cat it would
improve man, but it would deteriorate the cat.
While skimming "Using JRuby", I saw a few suggestions
about ways to ali
16 matches
Mail list logo
