Re: [MacRuby-devel] Subject: Re: Strange NSDate behavior building 32 bit v 64 bit
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 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? Thanks again, Richard 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 8:07 AM, Laurent Sansonetti wrote:
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 then we can see if people complain.
Laurent
On Jan 31, 2011, at 12:07 PM, Jordan K. Hubbard wrote:
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 demonstrate the problem) yet? That will allow us to track and prioritize the work for possible inclusion in 0.9 (or later, depending on how things go).
Thanks,
- Jordan
On Jan 31, 2011, at 2:41 AM, Richard Sepulveda wrote:
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 next release.
But i can't see anything obvious other than rewriting all of my NSDate based code in Objective-C or waiting for a fix. i include the MacRuby framework in my Pkg so that is possible.
Richard
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 of the code did not change between 0.7 and my change, so applying it to 0.7 should work fine. Unfortunately I don't think you will be able to run the specs in 32-bit mode. I tried this morning on trunk at it crashed (and it's probably nothing new).... If possible I would even recommend using trunk over 0.7/0.8 because they have a bug (fixed in r5191 http://www.macruby.org/trac/changeset/5191/ ) that could make MacRuby crash randomly.
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, Richard Sepulveda wrote:
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 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?
Thanks again,
Richard
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 8:07 AM, Laurent Sansonetti wrote:
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 then we can see if people complain.
Laurent
On Jan 31, 2011, at 12:07 PM, Jordan K. Hubbard wrote:
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 demonstrate the problem) yet? That will allow us to track and prioritize the work for possible inclusion in 0.9 (or later, depending on how things go).
Thanks,
- Jordan
On Jan 31, 2011, at 2:41 AM, Richard Sepulveda wrote:
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 next release.
But i can't see anything obvious other than rewriting all of my NSDate based code in Objective-C or waiting for a fix. i include the MacRuby framework in my Pkg so that is possible.
Richard
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
participants (3)
-
Laurent Sansonetti
-
Richard Sepulveda
-
Vincent Isambart