Hi Richard,
0.7 is a bit old at this point, I recommend using the latest release, 0.8.
This said, nightly builds have been pretty stable so far, so you may want to
try one too. This is basically what will be released as 0.9 very soon (this
week maybe!).
Laurent
On Jan 31, 2011, at 7:59 PM, Ri
> Is trunk ready for primetime? I noticed some problem reports with 0.9 in the
> mailing list lately and wasn't sure if that was a good idea.
For that I can't really answer, as I'm don't have any real application
using MacRuby. Other people on the mailing list can probably answer
that though.
How
Is trunk ready for primetime? I noticed some problem reports with 0.9 in the
mailing list lately
and wasn't sure if that was a good idea. And i haven't tested at all with 0.8
or 0.9. But I guess
you guys are primarily fixing things for the 1.0 release and only changing
things that are necessary
> Another question, my project is currently using the default 0.7 MacRuby
> framework included in XCode. I assume
> that I should include this fix in the latest 0.7 or 0.8 build and run all of
> the test suites to verify that I didn't
> break anything in the build process?
It looks like this part
Thanks for the rapid response to this problem. I will verify that it works with
my project as
soon as I can get MacRuby built. I also ran into some other strangeness in
32-bit mode but this may fix
those issues as well. I will give an update soon.
Another question, my project is currently using
Wow, now that's service! :-) Thanks, Vincent!
- Jordan
On Jan 31, 2011, at 3:22 PM, Vincent Isambart wrote:
> Sorry, I'm not patient so I filed the ticket:
> http://www.macruby.org/trac/ticket/1143
> And fixed it in r5215 :D
> http://www.macruby.org/trac/changeset/5215/
>
> On Feb 1, 2011, at
Sorry, I'm not patient so I filed the ticket:
http://www.macruby.org/trac/ticket/1143
And fixed it in r5215 :D
http://www.macruby.org/trac/changeset/5215/
On Feb 1, 2011, at 8:07 AM, Laurent Sansonetti wrote:
> Like Jordan said :)
>
> Please file a ticket and we will get this fixed in 0.9. Bugs
Like Jordan said :)
Please file a ticket and we will get this fixed in 0.9. Bugs breaking
applications are considered as a priority.
I think 0.9 should remain 32/64 bits, but the release after may drop 32-bit
support (unless people really need it). I can add a note in the 0.9 release
notes and
Fair enough, I did not realize that you'd already deployed an app based on
MacRuby and had already received bug reports (which suggests that the number of
32 bit users is clearly non-zero, at least!). Have you filed a ticket in trac
with a reduction (e.g. the minimum code necessary to demonstra
Forget my previous mail, I found a better workaround: in objc.m replace:
VALUE arg = DBL2NUM(time + CF_REFERENCE_DATE);
by
VALUE arg = LONG2NUM(time + CF_REFERENCE_DATE);
With this, you will lose sub-second precision but it will still be
better than what you have currently.
I can add microseconds p
Hi,
> That makes perfectly good sense but i unfortunately started selling a MacRuby
> app on the App Store
> for i386 and 64 bit machines. And a few people are experiencing this issue. I
> was just hoping
> for a quick workaround to make them happy. And I would discontinue selling
> the 32 bit
That makes perfectly good sense but i unfortunately started selling a MacRuby
app on the App Store
for i386 and 64 bit machines. And a few people are experiencing this issue. I
was just hoping
for a quick workaround to make them happy. And I would discontinue selling the
32 bit version
on the n
12 matches
Mail list logo
