Hi,
I've looked into the issue some more, and it turns out the backtraces created
by MacRuby nightly are much more similar to the 1.9.2 ones. The backtrace still
misses the line referring to the actual execution of the spec though, so the
problem hasn't been completely solved yet.
It seems thi
I believe this is a known issue that needs to be addressed. Can you please
check if there is already an open ticket, if not, please open one.
Thx
- Matt
Sent from my iPhone
On Nov 14, 2010, at 3:05, Martijn Walraven wrote:
> Hi,
>
> I've looked into the issue some more, and it turns out the
I've added a ticket (#996) describing the issue. I wish I could do more to help
fix it, but I'm afraid I don't know enough about the implementation of the VM.
On Nov 14, 2010, at 15:22 , Matt Aimonetti wrote:
> I believe this is a known issue that needs to be addressed. Can you please
> check i
Thx for reporting the problem you encountered.
- Matt
Sent from my iPhone
On Nov 14, 2010, at 9:27, Martijn Walraven wrote:
> I've added a ticket (#996) describing the issue. I wish I could do more to
> help fix it, but I'm afraid I don't know enough about the implementation of
> the VM.
>
Hello,
Both JRuby and IronRuby support translation from 'native' CamelCase method
names to the
lowercase_with_underscores naming convention in idiomatic Ruby.
They IronRuby guys call this "name-mangling":
http://ironruby.net/Documentation/.NET/Names
I had an expectation that this would be the ca
Hi Scott,
MacRuby's spiritual predecessor RubyCocoa did this sort of substitution of
camelCase for under_case. However, I don't foresee this name-mangling being a
part of MacRuby's near future for one very important reason: MacRuby methods
*are* Objective-C methods.
I'm not aware of the partic
Hey Leigh,
I don't (currently) have much of an opinion about HotCocoa, but regarding the
specific example you give, there has been some talk about implementing the Ruby
net/* libraries on top of NSURLConnection and friends. In the past, the problem
has been that NSURLConnection is inherently as
It actually is also helpful to quickly see the difference between Obj-c/C
methods/functions & Ruby methods.
It also helps with documentation.
I agree with Joshua, I don't see that change happening anytime soon either.
- Matt
Sent from my iPhone
On Nov 14, 2010, at 12:49, Joshua Ballanco wrote
You can look at the wrapper I wrote and usually use in my apps:
https://github.com/mattetti/macruby-httpwrapper/blob/master/macruby_http.rb
It's not perfect but it might help you.
- Matt
Sent from my iPhone
On Nov 14, 2010, at 13:14, Joshua Ballanco wrote:
> Hey Leigh,
>
> I don't (currently
>* I'm not aware of the particulars of the IronRuby or JRuby bridges, but in
>the case of RubyCocoa, there is a translation step to get from a Ruby method
>name to an Objective-Cselector. In MacRuby, there is no transation step.
>MacRuby method names are Objective-C selectors and vice versa. So,
Hi,
I was wondering if there is any way to formally indicate a MacRuby class
conforms to an Objective-C protocol. I encountered some code that uses
conformsToProtocol: instead of respondsToSelector: as a check before invoking
delegate methods, and the only way I could get a delegate written in
Hey,
I wrote a line of code that I thought was correct (but maybe not so pretty) and
in one case it was giving me a weird error. I was wondering if someone could
explain to me what is wrong with it; I suspect there is some behaviour of
MacRuby that I am not understanding. Here are a few example
I had digest mode turned on, so this reply might be orphaned. Sorry in advance
if that's the case.
Thanks Matt for showing me your HTTP wrapper... there are some good ideas there.
In reply to Josh, what would be the advantages of using NSURLConnection as the
transport for the net/* libraries? I
13 matches
Mail list logo
