From ruby-noreply at macosforge.org  Thu Oct  1 16:05:43 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 01 Oct 2009 23:05:43 -0000
Subject: [MacRuby-devel] [MacRuby] #361: Embed MacRuby Target Adds 60+ MB to
	.app
Message-ID: <050.572b3571708c100e8e310b9c06e29519@macosforge.org>

#361: Embed MacRuby Target Adds 60+ MB to .app
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------
 Expected:

 Between 17(mentioned in presentation, not verified) MB and 30 MB (size of
 .dylib file) to be added to the output .app file on build from Xcode of
 the 'Embed MacRuby' target.

 Observed:

 The actual output file is over 69 mb, even with a base project with no
 code.

 Steps to reproduce:

 1.) open the attached project in Xcode
 2.) select the embed macruby target in the Active Target box
 3.) build
 4.) check the file size of the resulting .app file

 This embeds the whole framework, including all of the installed gems
 (including gems installed by the user!), tools, etc.

 Work around:

 Manually embedding the 'libmacruby.1.9.0.dylib' and using a copy files
 build step seems to work, but I haven't tested on systems without MacRuby
 yet.

 Even with this 30mb seems a bit on the large side.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/361>
MacRuby <http://macruby.org/>


From dylan at ideaswarm.com  Thu Oct  1 16:26:01 2009
From: dylan at ideaswarm.com (Dylan Bruzenak)
Date: Thu, 1 Oct 2009 18:26:01 -0500
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
Message-ID: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>

So, I've been mucking about with MacRuby lately. It's been fun so far.
Thanks to all the devs for this great project.
I'm a pretty firm believer in unit testing my Ruby code. I love how Ruby on
Rails and similar frameworks nudge you in the right direction by baking in
an existing testing infrastructure.

I've got testing pretty much figured out and was wondering if the team would
be open to modifying the basic Xcode project template to add unit testing,
with a stub test and test_suite file to get started. This would also involve
creating a framework for any objective-c code that the user writes so that
it can be included in both the .app and the test files.

In addition it might be useful to include the 'embed mac ruby' and possibly
a macrubyc target as well by default. These can always be removed if a user
doesn't want them.

I can supply preliminary patches if this seems like a good route to go.

- Dylan Bruzenak
www.ideaswarm.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091001/5477963a/attachment.html>

From mattaimonetti at gmail.com  Thu Oct  1 16:31:24 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Thu, 1 Oct 2009 16:31:24 -0700
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
Message-ID: <20fefa50910011631s79d9121bqa385c347f790f267@mail.gmail.com>

Hi Dylan,

Why don't you you post your template so people can look at it and give their
feedback? People like Eloy would probably give their feedback ;)

- Matt



On Thu, Oct 1, 2009 at 4:26 PM, Dylan Bruzenak <dylan at ideaswarm.com> wrote:

> So, I've been mucking about with MacRuby lately. It's been fun so far.
> Thanks to all the devs for this great project.
> I'm a pretty firm believer in unit testing my Ruby code. I love how Ruby on
> Rails and similar frameworks nudge you in the right direction by baking in
> an existing testing infrastructure.
>
> I've got testing pretty much figured out and was wondering if the team
> would be open to modifying the basic Xcode project template to add unit
> testing, with a stub test and test_suite file to get started. This would
> also involve creating a framework for any objective-c code that the user
> writes so that it can be included in both the .app and the test files.
>
> In addition it might be useful to include the 'embed mac ruby' and possibly
> a macrubyc target as well by default. These can always be removed if a user
> doesn't want them.
>
> I can supply preliminary patches if this seems like a good route to go.
>
> - Dylan Bruzenak
> www.ideaswarm.com
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091001/47c0e918/attachment.html>

From dylan at ideaswarm.com  Thu Oct  1 19:50:36 2009
From: dylan at ideaswarm.com (Dylan Bruzenak)
Date: Thu, 1 Oct 2009 21:50:36 -0500
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <aea090980910011948k7c5e24e6ue5dba7901833ebf8@mail.gmail.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<20fefa50910011631s79d9121bqa385c347f790f267@mail.gmail.com>
	<aea090980910011948k7c5e24e6ue5dba7901833ebf8@mail.gmail.com>
Message-ID: <aea090980910011950v114b2715tb6848791fd7a6d5e@mail.gmail.com>

Message is being held pending moderator approval; let me know if I should
post the actual file somewhere else :)

- Dylan

On Thu, Oct 1, 2009 at 9:48 PM, Dylan Bruzenak <dylan at ideaswarm.com> wrote:

> Good idea. I've attached it here. I may have accidentally added the build
> directory as well; this should be deleted from the template.
>
> To test you can copy it to one of the template directories such as :
> ~/Library/Application Support/Developer/Shared/Xcode/Project
> Templates/Application/MacRuby Application With Testing
>
> Differences:
>
> - Embed MacRuby target is included by default to easy deployment for first
> time users
> - Tests directory has been added for tests
> - test_stub.rb has been added with a starting test::unit case
> - Unit Tests target has been added to run the tests
> - test_suite.rb has been added to load up all tests from the Tests
> directory. This can easily be made recursive using Dir.glob.
>
> I've left out the framework/obj-c testing stuff because it is difficult to
> get it working in cases where there is no objective-c; building the
> framework requires at least one class. A better way to handle that would be
> to write up a blog post on how to do this; mainly:
>
> 1.) Create a new Cocoa -> Framework target
> 2.) add the new framework to your unit test and .app targets so that it
> gets built when either target is run
> 3.) add a copy files step, targeting frameworks, to your .app target
> 4.) add the new framework(drag from the products folder) to both the link
> and copy steps of your .app target to include it with your .app file
> 5.) add "framework 'newframeworkname'" to your rb_main.rb file
> 6.) add "framework 'build/Debug/newframeworkname.framework' to your
> test_suite.rb file
>
> After following these steps you can test any Obj-c classes added to the
> framework from Ruby, as well as any Ruby classes that depend on these custom
> classes.
>
> - Dylan
>
>
> On Thu, Oct 1, 2009 at 6:31 PM, Matt Aimonetti <mattaimonetti at gmail.com>wrote:
>
>> Hi Dylan,
>>
>> Why don't you you post your template so people can look at it and give
>> their feedback? People like Eloy would probably give their feedback ;)
>>
>> - Matt
>>
>>
>>
>> On Thu, Oct 1, 2009 at 4:26 PM, Dylan Bruzenak <dylan at ideaswarm.com>wrote:
>>
>>> So, I've been mucking about with MacRuby lately. It's been fun so far.
>>> Thanks to all the devs for this great project.
>>> I'm a pretty firm believer in unit testing my Ruby code. I love how Ruby
>>> on Rails and similar frameworks nudge you in the right direction by baking
>>> in an existing testing infrastructure.
>>>
>>> I've got testing pretty much figured out and was wondering if the team
>>> would be open to modifying the basic Xcode project template to add unit
>>> testing, with a stub test and test_suite file to get started. This would
>>> also involve creating a framework for any objective-c code that the user
>>> writes so that it can be included in both the .app and the test files.
>>>
>>> In addition it might be useful to include the 'embed mac ruby' and
>>> possibly a macrubyc target as well by default. These can always be removed
>>> if a user doesn't want them.
>>>
>>> I can supply preliminary patches if this seems like a good route to go.
>>>
>>> - Dylan Bruzenak
>>> www.ideaswarm.com
>>>
>>>
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091001/a12790ed/attachment.html>

From ruby-noreply at macosforge.org  Thu Oct  1 21:05:08 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 02 Oct 2009 04:05:08 -0000
Subject: [MacRuby-devel] [MacRuby] #361: Embed MacRuby Target Adds 60+
	MB to .app
In-Reply-To: <050.572b3571708c100e8e310b9c06e29519@macosforge.org>
References: <050.572b3571708c100e8e310b9c06e29519@macosforge.org>
Message-ID: <059.1c6276ab248e9efcdbbc505d89ae06a8@macosforge.org>

#361: Embed MacRuby Target Adds 60+ MB to .app
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------

Comment(by lsansonetti@?):

 Are you using 0.4 or 0.5 (trunk)? The rewrite of the new VM in C++ plus
 the static inclusion of LLVM unfortunately grew up the size of MacRuby in
 trunk. The dylib is about 28MB here (which contains code for both i386 and
 x86_64, so it can be cut in half if necessary). Due to heavy STL inlining
 certain object files are very big, this is a shame. We have a plan to put
 some object files on diet and also move the LLVM stuff we need into a
 shared library.

 Also, the Embed MacRuby target embeds everything, including the standard
 library, gems, and so on as you may have noticed. Most programs probably
 only need libmacruby.dylib. The target could potentially be changed to
 allow 2 modes, one that embeds everything and one that only embeds the
 dylib.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/361#comment:1>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Thu Oct  1 21:07:16 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 01 Oct 2009 21:07:16 -0700
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <aea090980910011950v114b2715tb6848791fd7a6d5e@mail.gmail.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<20fefa50910011631s79d9121bqa385c347f790f267@mail.gmail.com>
	<aea090980910011948k7c5e24e6ue5dba7901833ebf8@mail.gmail.com>
	<aea090980910011950v114b2715tb6848791fd7a6d5e@mail.gmail.com>
Message-ID: <8B29771A-9D50-45FB-AD74-9BE722DD1537@apple.com>

Hi Dylan,

Could you open a trac ticket and attach your new template there? It  
would be a better idea I guess, and we can also track its inclusion to  
trunk from there.

Thanks for the work, it looks great :)

Laurent

On Oct 1, 2009, at 7:50 PM, Dylan Bruzenak wrote:

> Message is being held pending moderator approval; let me know if I  
> should post the actual file somewhere else :)
>
> - Dylan
>
> On Thu, Oct 1, 2009 at 9:48 PM, Dylan Bruzenak <dylan at ideaswarm.com>  
> wrote:
> Good idea. I've attached it here. I may have accidentally added the  
> build directory as well; this should be deleted from the template.
>
> To test you can copy it to one of the template directories such as :  
> ~/Library/Application Support/Developer/Shared/Xcode/Project  
> Templates/Application/MacRuby Application With Testing
>
> Differences:
>
> - Embed MacRuby target is included by default to easy deployment for  
> first time users
> - Tests directory has been added for tests
> - test_stub.rb has been added with a starting test::unit case
> - Unit Tests target has been added to run the tests
> - test_suite.rb has been added to load up all tests from the Tests  
> directory. This can easily be made recursive using Dir.glob.
>
> I've left out the framework/obj-c testing stuff because it is  
> difficult to get it working in cases where there is no objective-c;  
> building the framework requires at least one class. A better way to  
> handle that would be to write up a blog post on how to do this;  
> mainly:
>
> 1.) Create a new Cocoa -> Framework target
> 2.) add the new framework to your unit test and .app targets so that  
> it gets built when either target is run
> 3.) add a copy files step, targeting frameworks, to your .app target
> 4.) add the new framework(drag from the products folder) to both the  
> link and copy steps of your .app target to include it with your .app  
> file
> 5.) add "framework 'newframeworkname'" to your rb_main.rb file
> 6.) add "framework 'build/Debug/newframeworkname.framework' to your  
> test_suite.rb file
>
> After following these steps you can test any Obj-c classes added to  
> the framework from Ruby, as well as any Ruby classes that depend on  
> these custom classes.
>
> - Dylan
>
>
> On Thu, Oct 1, 2009 at 6:31 PM, Matt Aimonetti <mattaimonetti at gmail.com 
> > wrote:
> Hi Dylan,
>
> Why don't you you post your template so people can look at it and  
> give their feedback? People like Eloy would probably give their  
> feedback ;)
>
> - Matt
>
>
>
> On Thu, Oct 1, 2009 at 4:26 PM, Dylan Bruzenak <dylan at ideaswarm.com>  
> wrote:
> So, I've been mucking about with MacRuby lately. It's been fun so  
> far. Thanks to all the devs for this great project.
>
> I'm a pretty firm believer in unit testing my Ruby code. I love how  
> Ruby on Rails and similar frameworks nudge you in the right  
> direction by baking in an existing testing infrastructure.
>
> I've got testing pretty much figured out and was wondering if the  
> team would be open to modifying the basic Xcode project template to  
> add unit testing, with a stub test and test_suite file to get  
> started. This would also involve creating a framework for any  
> objective-c code that the user writes so that it can be included in  
> both the .app and the test files.
>
> In addition it might be useful to include the 'embed mac ruby' and  
> possibly a macrubyc target as well by default. These can always be  
> removed if a user doesn't want them.
>
> I can supply preliminary patches if this seems like a good route to  
> go.
>
> - Dylan Bruzenak
> www.ideaswarm.com
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ben.schwarz at gmail.com  Thu Oct  1 23:01:47 2009
From: ben.schwarz at gmail.com (Ben Schwarz)
Date: Fri, 2 Oct 2009 16:01:47 +1000
Subject: [MacRuby-devel] Supported classes & methods diagram fed from
	rubyspec
Message-ID: <E148045D-99B5-4CB6-9542-2973197873A4@gmail.com>

Hi all,


I've had some loose discussions with @lrz regarding a visual  
representation of classes and methods that are working via the rubyspec.
This would enable developers to find an area of development to focus  
on and also for end-users to understand what they might face before
conducting any development using macruby (bringing real applications  
closer to tuition, rather than a start/stop experience)

I'm happy to offer some hours to get something together that is styled  
like macruby.org but I obviously need to:

	A) consult the group
	B) work out a spec
	C) have something setup on the macruby.org infrastructure.


Discuss.


Cheers,

-

Ben Schwarz
Web architect

Web:		http://www.germanforblack.com
Mobile: 		+61 407 339 418

-- 
Please consider your environment before printing or distributing this  
material.
--

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/94fd978a/attachment.html>

From ruby-noreply at macosforge.org  Thu Oct  1 23:02:52 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 02 Oct 2009 06:02:52 -0000
Subject: [MacRuby-devel] [MacRuby] #362: Add Unit Testing and Embed MacRuby
 to Project Template
Message-ID: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>

#362: Add Unit Testing and Embed MacRuby to Project Template
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |       Owner:  lsansonetti@?        
     Type:  enhancement          |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------
 I'm attaching a new version of the default project template.

 To test you can copy it to one of the template directories such as :
 ~/Library/Application Support/Developer/Shared/Xcode/Project
 Templates/Application/

 Differences:

 - Embed MacRuby target is included by default to easy deployment for first
 time users
 - Tests directory has been added for tests
 - test_stub.rb has been added with a starting test::unit case
 - Unit Tests target has been added to run the tests
 - test_suite.rb has been added to load up all tests from the Tests
 directory. This can easily be made recursive using Dir.glob.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/362>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct  1 23:06:24 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 02 Oct 2009 06:06:24 -0000
Subject: [MacRuby-devel] [MacRuby] #362: Add Unit Testing and Embed
 MacRuby to Project Template
In-Reply-To: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
References: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
Message-ID: <059.797e0961ea1e03feae2ffe011f70cf17@macosforge.org>

#362: Add Unit Testing and Embed MacRuby to Project Template
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |       Owner:  lsansonetti@?        
     Type:  enhancement          |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------

Comment(by dylan@?):

 If there's interest I can also port these changes to the other project
 templates.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/362#comment:1>
MacRuby <http://macruby.org/>


From dylan at ideaswarm.com  Thu Oct  1 23:06:44 2009
From: dylan at ideaswarm.com (Dylan Bruzenak)
Date: Fri, 2 Oct 2009 01:06:44 -0500
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <8B29771A-9D50-45FB-AD74-9BE722DD1537@apple.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<20fefa50910011631s79d9121bqa385c347f790f267@mail.gmail.com>
	<aea090980910011948k7c5e24e6ue5dba7901833ebf8@mail.gmail.com>
	<aea090980910011950v114b2715tb6848791fd7a6d5e@mail.gmail.com>
	<8B29771A-9D50-45FB-AD74-9BE722DD1537@apple.com>
Message-ID: <aea090980910012306hcc149bdk9c0b7e16e80b5d0f@mail.gmail.com>

Just opened https://www.macruby.org/trac/ticket/362 :)
As for the testing obj-c classes part, what is the best way to document that
? I'm not the best blogger in the world but I could write something up on my
personal blog or contribute a short how to somewhere in the documentation or
your website if that is preferred.

- Dylan

On Thu, Oct 1, 2009 at 11:07 PM, Laurent Sansonetti
<lsansonetti at apple.com>wrote:

> Hi Dylan,
>
> Could you open a trac ticket and attach your new template there? It would
> be a better idea I guess, and we can also track its inclusion to trunk from
> there.
>
> Thanks for the work, it looks great :)
>
> Laurent
>
>
> On Oct 1, 2009, at 7:50 PM, Dylan Bruzenak wrote:
>
>  Message is being held pending moderator approval; let me know if I should
>> post the actual file somewhere else :)
>>
>> - Dylan
>>
>> On Thu, Oct 1, 2009 at 9:48 PM, Dylan Bruzenak <dylan at ideaswarm.com>
>> wrote:
>> Good idea. I've attached it here. I may have accidentally added the build
>> directory as well; this should be deleted from the template.
>>
>> To test you can copy it to one of the template directories such as :
>> ~/Library/Application Support/Developer/Shared/Xcode/Project
>> Templates/Application/MacRuby Application With Testing
>>
>> Differences:
>>
>> - Embed MacRuby target is included by default to easy deployment for first
>> time users
>> - Tests directory has been added for tests
>> - test_stub.rb has been added with a starting test::unit case
>> - Unit Tests target has been added to run the tests
>> - test_suite.rb has been added to load up all tests from the Tests
>> directory. This can easily be made recursive using Dir.glob.
>>
>> I've left out the framework/obj-c testing stuff because it is difficult to
>> get it working in cases where there is no objective-c; building the
>> framework requires at least one class. A better way to handle that would be
>> to write up a blog post on how to do this; mainly:
>>
>> 1.) Create a new Cocoa -> Framework target
>> 2.) add the new framework to your unit test and .app targets so that it
>> gets built when either target is run
>> 3.) add a copy files step, targeting frameworks, to your .app target
>> 4.) add the new framework(drag from the products folder) to both the link
>> and copy steps of your .app target to include it with your .app file
>> 5.) add "framework 'newframeworkname'" to your rb_main.rb file
>> 6.) add "framework 'build/Debug/newframeworkname.framework' to your
>> test_suite.rb file
>>
>> After following these steps you can test any Obj-c classes added to the
>> framework from Ruby, as well as any Ruby classes that depend on these custom
>> classes.
>>
>> - Dylan
>>
>>
>> On Thu, Oct 1, 2009 at 6:31 PM, Matt Aimonetti <mattaimonetti at gmail.com>
>> wrote:
>> Hi Dylan,
>>
>> Why don't you you post your template so people can look at it and give
>> their feedback? People like Eloy would probably give their feedback ;)
>>
>> - Matt
>>
>>
>>
>> On Thu, Oct 1, 2009 at 4:26 PM, Dylan Bruzenak <dylan at ideaswarm.com>
>> wrote:
>> So, I've been mucking about with MacRuby lately. It's been fun so far.
>> Thanks to all the devs for this great project.
>>
>> I'm a pretty firm believer in unit testing my Ruby code. I love how Ruby
>> on Rails and similar frameworks nudge you in the right direction by baking
>> in an existing testing infrastructure.
>>
>> I've got testing pretty much figured out and was wondering if the team
>> would be open to modifying the basic Xcode project template to add unit
>> testing, with a stub test and test_suite file to get started. This would
>> also involve creating a framework for any objective-c code that the user
>> writes so that it can be included in both the .app and the test files.
>>
>> In addition it might be useful to include the 'embed mac ruby' and
>> possibly a macrubyc target as well by default. These can always be removed
>> if a user doesn't want them.
>>
>> I can supply preliminary patches if this seems like a good route to go.
>>
>> - Dylan Bruzenak
>> www.ideaswarm.com
>>
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/41190f75/attachment-0001.html>

From ruby-noreply at macosforge.org  Thu Oct  1 23:14:14 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 02 Oct 2009 06:14:14 -0000
Subject: [MacRuby-devel] [MacRuby] #362: Add Unit Testing and Embed
 MacRuby to Project Template
In-Reply-To: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
References: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
Message-ID: <059.a7b3a2d7b1b928a3369f68035c04d012@macosforge.org>

#362: Add Unit Testing and Embed MacRuby to Project Template
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |       Owner:  lsansonetti@?        
     Type:  enhancement          |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------

Comment(by lsansonetti@?):

 I just gave it a try, it's awesome!

 I think we should definitely port the changes to the other templates, but
 we may first want to go with the main one and iterate on it until we are
 good. It's always painful to manage Xcode templates so it may be easier if
 we port the changes all in once.

 Also, regarding the test stuff, I think Eloy might want to comment, since
 he's our local test expert :)

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/362#comment:2>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Thu Oct  1 23:23:50 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 01 Oct 2009 23:23:50 -0700
Subject: [MacRuby-devel] Supported classes & methods diagram fed
	from	rubyspec
In-Reply-To: <E148045D-99B5-4CB6-9542-2973197873A4@gmail.com>
References: <E148045D-99B5-4CB6-9542-2973197873A4@gmail.com>
Message-ID: <9939E537-6087-41E2-8EBD-A818C1C5B06F@apple.com>

Hi Ben,

That sounds like a good idea and looks like what I had in mind.

I was thinking of having a status page, that shows hitlist items  
(critical bugs / things to do for the upcoming release), some rubyspec  
progress, a link to the latest nighty build, etc.

The hitlist thing could be generated from a local file from the  
repository. We currently use TODO for that.

We wrote a special mspec formatter in order to know what percentage of  
a given spec category we do pass. But having a more detailed view  
(classes / methods as you suggested) might be more interesting, this  
way we know on what class / method to focus in priority. Assuming that  
the mspec formatter is altered a little bit, this information could  
also be generated after a spec:ci pass.

Is that what you had in mind?

I guess the challenge here is to write a program that generates a  
Webby page for our website, commit it to the repository every time a  
change is made, then we would re-deploy the site right after.

Laurent

On Oct 1, 2009, at 11:01 PM, Ben Schwarz wrote:

> Hi all,
>
>
> I've had some loose discussions with @lrz regarding a visual  
> representation of classes and methods that are working via the  
> rubyspec.
> This would enable developers to find an area of development to focus  
> on and also for end-users to understand what they might face before
> conducting any development using macruby (bringing real applications  
> closer to tuition, rather than a start/stop experience)
>
> I'm happy to offer some hours to get something together that is  
> styled like macruby.org but I obviously need to:
>
> 	A) consult the group
> 	B) work out a spec
> 	C) have something setup on the macruby.org infrastructure.
>
>
> Discuss.
>
>
> Cheers,
>
> -
>
> Ben Schwarz
> Web architect
>
> Web:		http://www.germanforblack.com
> Mobile: 		+61 407 339 418
>
> -- 
> Please consider your environment before printing or distributing  
> this material.
> --
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From lsansonetti at apple.com  Thu Oct  1 23:26:39 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 01 Oct 2009 23:26:39 -0700
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <aea090980910012306hcc149bdk9c0b7e16e80b5d0f@mail.gmail.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<20fefa50910011631s79d9121bqa385c347f790f267@mail.gmail.com>
	<aea090980910011948k7c5e24e6ue5dba7901833ebf8@mail.gmail.com>
	<aea090980910011950v114b2715tb6848791fd7a6d5e@mail.gmail.com>
	<8B29771A-9D50-45FB-AD74-9BE722DD1537@apple.com>
	<aea090980910012306hcc149bdk9c0b7e16e80b5d0f@mail.gmail.com>
Message-ID: <D4037AC8-7ED3-4E11-ADB2-75A378439AE2@apple.com>

Hi Dylan,

Ideally it would be awesome to have some documentation on the website  
(likely a tutorial):

http://www.macruby.org/documentation.html

The process of creating a website article is not trivial but Mike  
Sassak recently contributed a tutorial describing how to contribute to  
the website:

http://www.macruby.org/documentation/website-contributions.html

Laurent

On Oct 1, 2009, at 11:06 PM, Dylan Bruzenak wrote:

> Just opened https://www.macruby.org/trac/ticket/362 :)
>
> As for the testing obj-c classes part, what is the best way to  
> document that ? I'm not the best blogger in the world but I could  
> write something up on my personal blog or contribute a short how to  
> somewhere in the documentation or your website if that is preferred.
>
> - Dylan
>
> On Thu, Oct 1, 2009 at 11:07 PM, Laurent Sansonetti <lsansonetti at apple.com 
> > wrote:
> Hi Dylan,
>
> Could you open a trac ticket and attach your new template there? It  
> would be a better idea I guess, and we can also track its inclusion  
> to trunk from there.
>
> Thanks for the work, it looks great :)
>
> Laurent
>
>
> On Oct 1, 2009, at 7:50 PM, Dylan Bruzenak wrote:
>
> Message is being held pending moderator approval; let me know if I  
> should post the actual file somewhere else :)
>
> - Dylan
>
> On Thu, Oct 1, 2009 at 9:48 PM, Dylan Bruzenak <dylan at ideaswarm.com>  
> wrote:
> Good idea. I've attached it here. I may have accidentally added the  
> build directory as well; this should be deleted from the template.
>
> To test you can copy it to one of the template directories such as :  
> ~/Library/Application Support/Developer/Shared/Xcode/Project  
> Templates/Application/MacRuby Application With Testing
>
> Differences:
>
> - Embed MacRuby target is included by default to easy deployment for  
> first time users
> - Tests directory has been added for tests
> - test_stub.rb has been added with a starting test::unit case
> - Unit Tests target has been added to run the tests
> - test_suite.rb has been added to load up all tests from the Tests  
> directory. This can easily be made recursive using Dir.glob.
>
> I've left out the framework/obj-c testing stuff because it is  
> difficult to get it working in cases where there is no objective-c;  
> building the framework requires at least one class. A better way to  
> handle that would be to write up a blog post on how to do this;  
> mainly:
>
> 1.) Create a new Cocoa -> Framework target
> 2.) add the new framework to your unit test and .app targets so that  
> it gets built when either target is run
> 3.) add a copy files step, targeting frameworks, to your .app target
> 4.) add the new framework(drag from the products folder) to both the  
> link and copy steps of your .app target to include it with your .app  
> file
> 5.) add "framework 'newframeworkname'" to your rb_main.rb file
> 6.) add "framework 'build/Debug/newframeworkname.framework' to your  
> test_suite.rb file
>
> After following these steps you can test any Obj-c classes added to  
> the framework from Ruby, as well as any Ruby classes that depend on  
> these custom classes.
>
> - Dylan
>
>
> On Thu, Oct 1, 2009 at 6:31 PM, Matt Aimonetti <mattaimonetti at gmail.com 
> > wrote:
> Hi Dylan,
>
> Why don't you you post your template so people can look at it and  
> give their feedback? People like Eloy would probably give their  
> feedback ;)
>
> - Matt
>
>
>
> On Thu, Oct 1, 2009 at 4:26 PM, Dylan Bruzenak <dylan at ideaswarm.com>  
> wrote:
> So, I've been mucking about with MacRuby lately. It's been fun so  
> far. Thanks to all the devs for this great project.
>
> I'm a pretty firm believer in unit testing my Ruby code. I love how  
> Ruby on Rails and similar frameworks nudge you in the right  
> direction by baking in an existing testing infrastructure.
>
> I've got testing pretty much figured out and was wondering if the  
> team would be open to modifying the basic Xcode project template to  
> add unit testing, with a stub test and test_suite file to get  
> started. This would also involve creating a framework for any  
> objective-c code that the user writes so that it can be included in  
> both the .app and the test files.
>
> In addition it might be useful to include the 'embed mac ruby' and  
> possibly a macrubyc target as well by default. These can always be  
> removed if a user doesn't want them.
>
> I can supply preliminary patches if this seems like a good route to  
> go.
>
> - Dylan Bruzenak
> www.ideaswarm.com
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Thu Oct  1 23:32:58 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 02 Oct 2009 06:32:58 -0000
Subject: [MacRuby-devel] [MacRuby] #361: Embed MacRuby Target Adds 60+
	MB to .app
In-Reply-To: <050.572b3571708c100e8e310b9c06e29519@macosforge.org>
References: <050.572b3571708c100e8e310b9c06e29519@macosforge.org>
Message-ID: <059.b96980d27ba2affea74003e7a785678c@macosforge.org>

#361: Embed MacRuby Target Adds 60+ MB to .app
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------

Comment(by dylan@?):

 I'm using trunk, so that explains the size discrepancy.

 How would I go about cutting the runtime size in half ?

 Two ideas related to the embedding:

 1.) Modify HotCocoa::ApplicationBuilder.deploy to take another argument,
 full deploy, which is false by default. If backwards compatibility is
 important here this could be changed to partial_deploy instead and default
 to the old behavior.

 OR

 2.) Add libmacruby.dylib to the project templates and use the standard
 copy framework build phase to deploy instead of the embed step

 There are two primary problems with embedding as it currently stands:

 1.) It picks up gems and probably shouldn't. The user should probably
 vendor any gems that should be included, explicitly.
 2.) It picks up both the libmacruby-static.a and libmacruby.1.9.0.dylib
 files, which is why the size is doubled. The extra .rb scripts are very
 small in comparison.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/361#comment:2>
MacRuby <http://macruby.org/>


From dylan at ideaswarm.com  Thu Oct  1 23:35:24 2009
From: dylan at ideaswarm.com (Dylan Bruzenak)
Date: Fri, 2 Oct 2009 01:35:24 -0500
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <D4037AC8-7ED3-4E11-ADB2-75A378439AE2@apple.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<20fefa50910011631s79d9121bqa385c347f790f267@mail.gmail.com>
	<aea090980910011948k7c5e24e6ue5dba7901833ebf8@mail.gmail.com>
	<aea090980910011950v114b2715tb6848791fd7a6d5e@mail.gmail.com>
	<8B29771A-9D50-45FB-AD74-9BE722DD1537@apple.com>
	<aea090980910012306hcc149bdk9c0b7e16e80b5d0f@mail.gmail.com>
	<D4037AC8-7ED3-4E11-ADB2-75A378439AE2@apple.com>
Message-ID: <aea090980910012335g6a54f534xf25ee9f89725e075@mail.gmail.com>

How very self-referential; I love it :)
I'll have a look. Maybe wait until my fever goes away before I take a stab
at prose though.

- Dylan

On Fri, Oct 2, 2009 at 1:26 AM, Laurent Sansonetti <lsansonetti at apple.com>wrote:

> Hi Dylan,
>
> Ideally it would be awesome to have some documentation on the website
> (likely a tutorial):
>
> http://www.macruby.org/documentation.html
>
> The process of creating a website article is not trivial but Mike Sassak
> recently contributed a tutorial describing how to contribute to the website:
>
> http://www.macruby.org/documentation/website-contributions.html
>
> Laurent
>
>
> On Oct 1, 2009, at 11:06 PM, Dylan Bruzenak wrote:
>
>  Just opened https://www.macruby.org/trac/ticket/362 :)
>>
>> As for the testing obj-c classes part, what is the best way to document
>> that ? I'm not the best blogger in the world but I could write something up
>> on my personal blog or contribute a short how to somewhere in the
>> documentation or your website if that is preferred.
>>
>> - Dylan
>>
>> On Thu, Oct 1, 2009 at 11:07 PM, Laurent Sansonetti <
>> lsansonetti at apple.com> wrote:
>> Hi Dylan,
>>
>> Could you open a trac ticket and attach your new template there? It would
>> be a better idea I guess, and we can also track its inclusion to trunk from
>> there.
>>
>> Thanks for the work, it looks great :)
>>
>> Laurent
>>
>>
>> On Oct 1, 2009, at 7:50 PM, Dylan Bruzenak wrote:
>>
>> Message is being held pending moderator approval; let me know if I should
>> post the actual file somewhere else :)
>>
>> - Dylan
>>
>> On Thu, Oct 1, 2009 at 9:48 PM, Dylan Bruzenak <dylan at ideaswarm.com>
>> wrote:
>> Good idea. I've attached it here. I may have accidentally added the build
>> directory as well; this should be deleted from the template.
>>
>> To test you can copy it to one of the template directories such as :
>> ~/Library/Application Support/Developer/Shared/Xcode/Project
>> Templates/Application/MacRuby Application With Testing
>>
>> Differences:
>>
>> - Embed MacRuby target is included by default to easy deployment for first
>> time users
>> - Tests directory has been added for tests
>> - test_stub.rb has been added with a starting test::unit case
>> - Unit Tests target has been added to run the tests
>> - test_suite.rb has been added to load up all tests from the Tests
>> directory. This can easily be made recursive using Dir.glob.
>>
>> I've left out the framework/obj-c testing stuff because it is difficult to
>> get it working in cases where there is no objective-c; building the
>> framework requires at least one class. A better way to handle that would be
>> to write up a blog post on how to do this; mainly:
>>
>> 1.) Create a new Cocoa -> Framework target
>> 2.) add the new framework to your unit test and .app targets so that it
>> gets built when either target is run
>> 3.) add a copy files step, targeting frameworks, to your .app target
>> 4.) add the new framework(drag from the products folder) to both the link
>> and copy steps of your .app target to include it with your .app file
>> 5.) add "framework 'newframeworkname'" to your rb_main.rb file
>> 6.) add "framework 'build/Debug/newframeworkname.framework' to your
>> test_suite.rb file
>>
>> After following these steps you can test any Obj-c classes added to the
>> framework from Ruby, as well as any Ruby classes that depend on these custom
>> classes.
>>
>> - Dylan
>>
>>
>> On Thu, Oct 1, 2009 at 6:31 PM, Matt Aimonetti <mattaimonetti at gmail.com>
>> wrote:
>> Hi Dylan,
>>
>> Why don't you you post your template so people can look at it and give
>> their feedback? People like Eloy would probably give their feedback ;)
>>
>> - Matt
>>
>>
>>
>> On Thu, Oct 1, 2009 at 4:26 PM, Dylan Bruzenak <dylan at ideaswarm.com>
>> wrote:
>> So, I've been mucking about with MacRuby lately. It's been fun so far.
>> Thanks to all the devs for this great project.
>>
>> I'm a pretty firm believer in unit testing my Ruby code. I love how Ruby
>> on Rails and similar frameworks nudge you in the right direction by baking
>> in an existing testing infrastructure.
>>
>> I've got testing pretty much figured out and was wondering if the team
>> would be open to modifying the basic Xcode project template to add unit
>> testing, with a stub test and test_suite file to get started. This would
>> also involve creating a framework for any objective-c code that the user
>> writes so that it can be included in both the .app and the test files.
>>
>> In addition it might be useful to include the 'embed mac ruby' and
>> possibly a macrubyc target as well by default. These can always be removed
>> if a user doesn't want them.
>>
>> I can supply preliminary patches if this seems like a good route to go.
>>
>> - Dylan Bruzenak
>> www.ideaswarm.com
>>
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/e8cd2527/attachment-0001.html>

From dylan at ideaswarm.com  Thu Oct  1 23:39:40 2009
From: dylan at ideaswarm.com (Dylan Bruzenak)
Date: Fri, 2 Oct 2009 01:39:40 -0500
Subject: [MacRuby-devel] How to compile all ruby files in a project using
	macrubyc
Message-ID: <aea090980910012339k6d08a22agee1a8bcbebc88c36@mail.gmail.com>

I'm a bit of a newbie when it comes to command line compilation.
Is there an easy way for me to basically just say: compile everything
recursively, starting at this directory ? Given that, what would be the best
way to then integrate that with an Xcode project as part of a target ?

Also, is this far enough along to consider adding to the project templates
by default ?

thanks!

- Dylan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/83f89613/attachment.html>

From ben.schwarz at gmail.com  Thu Oct  1 23:48:39 2009
From: ben.schwarz at gmail.com (Ben Schwarz)
Date: Fri, 2 Oct 2009 16:48:39 +1000
Subject: [MacRuby-devel] Supported classes & methods diagram fed from
	rubyspec
In-Reply-To: <9939E537-6087-41E2-8EBD-A818C1C5B06F@apple.com>
References: <E148045D-99B5-4CB6-9542-2973197873A4@gmail.com>
	<9939E537-6087-41E2-8EBD-A818C1C5B06F@apple.com>
Message-ID: <D0AA1C17-5F29-42FB-A5B1-BD5611EF37FE@gmail.com>

Laurent,

I just had a quick chat with Brian Ford (Rubinius) apparently they're  
looking at using some incarnation of git://github.com/madriska/ 
unity.git (http://unity.madriska.com/)
Which uses a YAML formatter for mspec. (http://github.com/madriska/mspec/commit/36b8bce62c272d546bcbd8ab9f136576ff4701e5 
)

I think this might be the best way to get something that works  
running. I'm sure that all the ruby implementations would benefit from  
the shared work effort in this regard.
We could start by investigating unity, chatting to the author and  
seeing if we can make some contributions.




On 02/10/2009, at 4:23 PM, Laurent Sansonetti wrote:

> Hi Ben,
>
> That sounds like a good idea and looks like what I had in mind.
>
> I was thinking of having a status page, that shows hitlist items  
> (critical bugs / things to do for the upcoming release), some  
> rubyspec progress, a link to the latest nighty build, etc.
>
> The hitlist thing could be generated from a local file from the  
> repository. We currently use TODO for that.
>
> We wrote a special mspec formatter in order to know what percentage  
> of a given spec category we do pass. But having a more detailed view  
> (classes / methods as you suggested) might be more interesting, this  
> way we know on what class / method to focus in priority. Assuming  
> that the mspec formatter is altered a little bit, this information  
> could also be generated after a spec:ci pass.
>
> Is that what you had in mind?
>
> I guess the challenge here is to write a program that generates a  
> Webby page for our website, commit it to the repository every time a  
> change is made, then we would re-deploy the site right after.
>
> Laurent
>
> On Oct 1, 2009, at 11:01 PM, Ben Schwarz wrote:
>
>> Hi all,
>>
>>
>> I've had some loose discussions with @lrz regarding a visual  
>> representation of classes and methods that are working via the  
>> rubyspec.
>> This would enable developers to find an area of development to  
>> focus on and also for end-users to understand what they might face  
>> before
>> conducting any development using macruby (bringing real  
>> applications closer to tuition, rather than a start/stop experience)
>>
>> I'm happy to offer some hours to get something together that is  
>> styled like macruby.org but I obviously need to:
>>
>> 	A) consult the group
>> 	B) work out a spec
>> 	C) have something setup on the macruby.org infrastructure.
>>
>>
>> Discuss.
>>
>>
>> Cheers,
>>
>> -
>>
>> Ben Schwarz
>> Web architect
>>
>> Web:		http://www.germanforblack.com
>> Mobile: 		+61 407 339 418
>>
>> -- 
>> Please consider your environment before printing or distributing  
>> this material.
>> --
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Thu Oct  1 23:48:56 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 02 Oct 2009 06:48:56 -0000
Subject: [MacRuby-devel] [MacRuby] #362: Add Unit Testing and Embed
 MacRuby to Project Template
In-Reply-To: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
References: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
Message-ID: <059.34d6f63abae00adf19bf525ad82ba42a@macosforge.org>

#362: Add Unit Testing and Embed MacRuby to Project Template
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |       Owner:  lsansonetti@?        
     Type:  enhancement          |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------

Comment(by dylan@?):

 :)

 Good idea on the wait to merge part. I do so hate replicating work.

 I'm new to Ruby 1.9; looks like test::unit was pulled in favor of minitest
 and a thin interface layer wrapper around it to provide basic test::unit
 compatibility. I see a spec.rb in there as well; might be interesting to
 include a stub for that kind of test as well.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/362#comment:3>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Thu Oct  1 23:54:37 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 01 Oct 2009 23:54:37 -0700
Subject: [MacRuby-devel] How to compile all ruby files in a project
 using macrubyc
In-Reply-To: <aea090980910012339k6d08a22agee1a8bcbebc88c36@mail.gmail.com>
References: <aea090980910012339k6d08a22agee1a8bcbebc88c36@mail.gmail.com>
Message-ID: <22A9350F-694E-4AE2-A6A3-E58B6CDC60A7@apple.com>

Hi Dylan,

The AOT compilation of an Xcode project is still not finalized. It's  
technically possible to do it with the current macrubyc on the command  
line but it's kind of hard and we still have problems with #require  
statements. We will introduce an Xcode target that does it  
automatically for the 0.5 release.

I guess the target could indeed by added by default to the templates  
once it's functional :)

Laurent

On Oct 1, 2009, at 11:39 PM, Dylan Bruzenak wrote:

> I'm a bit of a newbie when it comes to command line compilation.
>
> Is there an easy way for me to basically just say: compile  
> everything recursively, starting at this directory ? Given that,  
> what would be the best way to then integrate that with an Xcode  
> project as part of a target ?
>
> Also, is this far enough along to consider adding to the project  
> templates by default ?
>
> thanks!
>
> - Dylan
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From dylan at ideaswarm.com  Fri Oct  2 00:02:54 2009
From: dylan at ideaswarm.com (Dylan)
Date: Fri, 2 Oct 2009 02:02:54 -0500
Subject: [MacRuby-devel] How to compile all ruby files in a project
	using macrubyc
In-Reply-To: <22A9350F-694E-4AE2-A6A3-E58B6CDC60A7@apple.com>
References: <aea090980910012339k6d08a22agee1a8bcbebc88c36@mail.gmail.com>
	<22A9350F-694E-4AE2-A6A3-E58B6CDC60A7@apple.com>
Message-ID: <951638E8-E69C-42C5-9CD1-125F763E0143@ideaswarm.com>

Good to know :)

Hate to ask since I can never answer this question myself: do you have  
a loose timeline for the release ?

-Dylan

On Oct 2, 2009, at 1:54 AM, Laurent Sansonetti <lsansonetti at apple.com>  
wrote:

> Hi Dylan,
>
> The AOT compilation of an Xcode project is still not finalized. It's  
> technically possible to do it with the current macrubyc on the  
> command line but it's kind of hard and we still have problems with  
> #require statements. We will introduce an Xcode target that does it  
> automatically for the 0.5 release.
>
> I guess the target could indeed by added by default to the templates  
> once it's functional :)
>
> Laurent
>
> On Oct 1, 2009, at 11:39 PM, Dylan Bruzenak wrote:
>
>> I'm a bit of a newbie when it comes to command line compilation.
>>
>> Is there an easy way for me to basically just say: compile  
>> everything recursively, starting at this directory ? Given that,  
>> what would be the best way to then integrate that with an Xcode  
>> project as part of a target ?
>>
>> Also, is this far enough along to consider adding to the project  
>> templates by default ?
>>
>> thanks!
>>
>> - Dylan
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

From hukl at berlin.ccc.de  Fri Oct  2 00:25:22 2009
From: hukl at berlin.ccc.de (John-Paul Bader)
Date: Fri, 2 Oct 2009 09:25:22 +0200
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <aea090980910012335g6a54f534xf25ee9f89725e075@mail.gmail.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<20fefa50910011631s79d9121bqa385c347f790f267@mail.gmail.com>
	<aea090980910011948k7c5e24e6ue5dba7901833ebf8@mail.gmail.com>
	<aea090980910011950v114b2715tb6848791fd7a6d5e@mail.gmail.com>
	<8B29771A-9D50-45FB-AD74-9BE722DD1537@apple.com>
	<aea090980910012306hcc149bdk9c0b7e16e80b5d0f@mail.gmail.com>
	<D4037AC8-7ED3-4E11-ADB2-75A378439AE2@apple.com>
	<aea090980910012335g6a54f534xf25ee9f89725e075@mail.gmail.com>
Message-ID: <61BEED36-99F0-47B1-A2E0-8371299E1138@berlin.ccc.de>

Hey,

how exactly can I run these tests? rake test would be great.

kind regards,

John



On 02.10.2009, at 08:35, Dylan Bruzenak wrote:

> How very self-referential; I love it :)
>
> I'll have a look. Maybe wait until my fever goes away before I take  
> a stab at prose though.
>
> - Dylan
>
> On Fri, Oct 2, 2009 at 1:26 AM, Laurent Sansonetti <lsansonetti at apple.com 
> > wrote:
> Hi Dylan,
>
> Ideally it would be awesome to have some documentation on the  
> website (likely a tutorial):
>
> http://www.macruby.org/documentation.html
>
> The process of creating a website article is not trivial but Mike  
> Sassak recently contributed a tutorial describing how to contribute  
> to the website:
>
> http://www.macruby.org/documentation/website-contributions.html
>
> Laurent
>
>
> On Oct 1, 2009, at 11:06 PM, Dylan Bruzenak wrote:
>
> Just opened https://www.macruby.org/trac/ticket/362 :)
>
> As for the testing obj-c classes part, what is the best way to  
> document that ? I'm not the best blogger in the world but I could  
> write something up on my personal blog or contribute a short how to  
> somewhere in the documentation or your website if that is preferred.
>
> - Dylan
>
> On Thu, Oct 1, 2009 at 11:07 PM, Laurent Sansonetti <lsansonetti at apple.com 
> > wrote:
> Hi Dylan,
>
> Could you open a trac ticket and attach your new template there? It  
> would be a better idea I guess, and we can also track its inclusion  
> to trunk from there.
>
> Thanks for the work, it looks great :)
>
> Laurent
>
>
> On Oct 1, 2009, at 7:50 PM, Dylan Bruzenak wrote:
>
> Message is being held pending moderator approval; let me know if I  
> should post the actual file somewhere else :)
>
> - Dylan
>
> On Thu, Oct 1, 2009 at 9:48 PM, Dylan Bruzenak <dylan at ideaswarm.com>  
> wrote:
> Good idea. I've attached it here. I may have accidentally added the  
> build directory as well; this should be deleted from the template.
>
> To test you can copy it to one of the template directories such as :  
> ~/Library/Application Support/Developer/Shared/Xcode/Project  
> Templates/Application/MacRuby Application With Testing
>
> Differences:
>
> - Embed MacRuby target is included by default to easy deployment for  
> first time users
> - Tests directory has been added for tests
> - test_stub.rb has been added with a starting test::unit case
> - Unit Tests target has been added to run the tests
> - test_suite.rb has been added to load up all tests from the Tests  
> directory. This can easily be made recursive using Dir.glob.
>
> I've left out the framework/obj-c testing stuff because it is  
> difficult to get it working in cases where there is no objective-c;  
> building the framework requires at least one class. A better way to  
> handle that would be to write up a blog post on how to do this;  
> mainly:
>
> 1.) Create a new Cocoa -> Framework target
> 2.) add the new framework to your unit test and .app targets so that  
> it gets built when either target is run
> 3.) add a copy files step, targeting frameworks, to your .app target
> 4.) add the new framework(drag from the products folder) to both the  
> link and copy steps of your .app target to include it with your .app  
> file
> 5.) add "framework 'newframeworkname'" to your rb_main.rb file
> 6.) add "framework 'build/Debug/newframeworkname.framework' to your  
> test_suite.rb file
>
> After following these steps you can test any Obj-c classes added to  
> the framework from Ruby, as well as any Ruby classes that depend on  
> these custom classes.
>
> - Dylan
>
>
> On Thu, Oct 1, 2009 at 6:31 PM, Matt Aimonetti <mattaimonetti at gmail.com 
> > wrote:
> Hi Dylan,
>
> Why don't you you post your template so people can look at it and  
> give their feedback? People like Eloy would probably give their  
> feedback ;)
>
> - Matt
>
>
>
> On Thu, Oct 1, 2009 at 4:26 PM, Dylan Bruzenak <dylan at ideaswarm.com>  
> wrote:
> So, I've been mucking about with MacRuby lately. It's been fun so  
> far. Thanks to all the devs for this great project.
>
> I'm a pretty firm believer in unit testing my Ruby code. I love how  
> Ruby on Rails and similar frameworks nudge you in the right  
> direction by baking in an existing testing infrastructure.
>
> I've got testing pretty much figured out and was wondering if the  
> team would be open to modifying the basic Xcode project template to  
> add unit testing, with a stub test and test_suite file to get  
> started. This would also involve creating a framework for any  
> objective-c code that the user writes so that it can be included in  
> both the .app and the test files.
>
> In addition it might be useful to include the 'embed mac ruby' and  
> possibly a macrubyc target as well by default. These can always be  
> removed if a user doesn't want them.
>
> I can supply preliminary patches if this seems like a good route to  
> go.
>
> - Dylan Bruzenak
> www.ideaswarm.com
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From dylan at ideaswarm.com  Fri Oct  2 00:42:53 2009
From: dylan at ideaswarm.com (Dylan)
Date: Fri, 2 Oct 2009 02:42:53 -0500
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <61BEED36-99F0-47B1-A2E0-8371299E1138@berlin.ccc.de>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<20fefa50910011631s79d9121bqa385c347f790f267@mail.gmail.com>
	<aea090980910011948k7c5e24e6ue5dba7901833ebf8@mail.gmail.com>
	<aea090980910011950v114b2715tb6848791fd7a6d5e@mail.gmail.com>
	<8B29771A-9D50-45FB-AD74-9BE722DD1537@apple.com>
	<aea090980910012306hcc149bdk9c0b7e16e80b5d0f@mail.gmail.com>
	<D4037AC8-7ED3-4E11-ADB2-75A378439AE2@apple.com>
	<aea090980910012335g6a54f534xf25ee9f89725e075@mail.gmail.com>
	<61BEED36-99F0-47B1-A2E0-8371299E1138@berlin.ccc.de>
Message-ID: <8885074B-22E4-4B98-8163-BF9C388AEE39@ideaswarm.com>

In the Xcode project select 'Unit Tests' from as the active target  
from tge tool bar. Then build :)

-Dylan



On Oct 2, 2009, at 2:25 AM, John-Paul Bader <hukl at berlin.ccc.de> wrote:

> Hey,
>
> how exactly can I run these tests? rake test would be great.
>
> kind regards,
>
> John
>
>
>
> On 02.10.2009, at 08:35, Dylan Bruzenak wrote:
>
>> How very self-referential; I love it :)
>>
>> I'll have a look. Maybe wait until my fever goes away before I take  
>> a stab at prose though.
>>
>> - Dylan
>>
>> On Fri, Oct 2, 2009 at 1:26 AM, Laurent Sansonetti <lsansonetti at apple.com 
>> > wrote:
>> Hi Dylan,
>>
>> Ideally it would be awesome to have some documentation on the  
>> website (likely a tutorial):
>>
>> http://www.macruby.org/documentation.html
>>
>> The process of creating a website article is not trivial but Mike  
>> Sassak recently contributed a tutorial describing how to contribute  
>> to the website:
>>
>> http://www.macruby.org/documentation/website-contributions.html
>>
>> Laurent
>>
>>
>> On Oct 1, 2009, at 11:06 PM, Dylan Bruzenak wrote:
>>
>> Just opened https://www.macruby.org/trac/ticket/362 :)
>>
>> As for the testing obj-c classes part, what is the best way to  
>> document that ? I'm not the best blogger in the world but I could  
>> write something up on my personal blog or contribute a short how to  
>> somewhere in the documentation or your website if that is preferred.
>>
>> - Dylan
>>
>> On Thu, Oct 1, 2009 at 11:07 PM, Laurent Sansonetti <lsansonetti at apple.com 
>> > wrote:
>> Hi Dylan,
>>
>> Could you open a trac ticket and attach your new template there? It  
>> would be a better idea I guess, and we can also track its inclusion  
>> to trunk from there.
>>
>> Thanks for the work, it looks great :)
>>
>> Laurent
>>
>>
>> On Oct 1, 2009, at 7:50 PM, Dylan Bruzenak wrote:
>>
>> Message is being held pending moderator approval; let me know if I  
>> should post the actual file somewhere else :)
>>
>> - Dylan
>>
>> On Thu, Oct 1, 2009 at 9:48 PM, Dylan Bruzenak  
>> <dylan at ideaswarm.com> wrote:
>> Good idea. I've attached it here. I may have accidentally added the  
>> build directory as well; this should be deleted from the template.
>>
>> To test you can copy it to one of the template directories such  
>> as : ~/Library/Application Support/Developer/Shared/Xcode/Project  
>> Templates/Application/MacRuby Application With Testing
>>
>> Differences:
>>
>> - Embed MacRuby target is included by default to easy deployment  
>> for first time users
>> - Tests directory has been added for tests
>> - test_stub.rb has been added with a starting test::unit case
>> - Unit Tests target has been added to run the tests
>> - test_suite.rb has been added to load up all tests from the Tests  
>> directory. This can easily be made recursive using Dir.glob.
>>
>> I've left out the framework/obj-c testing stuff because it is  
>> difficult to get it working in cases where there is no objective-c;  
>> building the framework requires at least one class. A better way to  
>> handle that would be to write up a blog post on how to do this;  
>> mainly:
>>
>> 1.) Create a new Cocoa -> Framework target
>> 2.) add the new framework to your unit test and .app targets so  
>> that it gets built when either target is run
>> 3.) add a copy files step, targeting frameworks, to your .app target
>> 4.) add the new framework(drag from the products folder) to both  
>> the link and copy steps of your .app target to include it with  
>> your .app file
>> 5.) add "framework 'newframeworkname'" to your rb_main.rb file
>> 6.) add "framework 'build/Debug/newframeworkname.framework' to your  
>> test_suite.rb file
>>
>> After following these steps you can test any Obj-c classes added to  
>> the framework from Ruby, as well as any Ruby classes that depend on  
>> these custom classes.
>>
>> - Dylan
>>
>>
>> On Thu, Oct 1, 2009 at 6:31 PM, Matt Aimonetti <mattaimonetti at gmail.com 
>> > wrote:
>> Hi Dylan,
>>
>> Why don't you you post your template so people can look at it and  
>> give their feedback? People like Eloy would probably give their  
>> feedback ;)
>>
>> - Matt
>>
>>
>>
>> On Thu, Oct 1, 2009 at 4:26 PM, Dylan Bruzenak  
>> <dylan at ideaswarm.com> wrote:
>> So, I've been mucking about with MacRuby lately. It's been fun so  
>> far. Thanks to all the devs for this great project.
>>
>> I'm a pretty firm believer in unit testing my Ruby code. I love how  
>> Ruby on Rails and similar frameworks nudge you in the right  
>> direction by baking in an existing testing infrastructure.
>>
>> I've got testing pretty much figured out and was wondering if the  
>> team would be open to modifying the basic Xcode project template to  
>> add unit testing, with a stub test and test_suite file to get  
>> started. This would also involve creating a framework for any  
>> objective-c code that the user writes so that it can be included in  
>> both the .app and the test files.
>>
>> In addition it might be useful to include the 'embed mac ruby' and  
>> possibly a macrubyc target as well by default. These can always be  
>> removed if a user doesn't want them.
>>
>> I can supply preliminary patches if this seems like a good route to  
>> go.
>>
>> - Dylan Bruzenak
>> www.ideaswarm.com
>>
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

From eloy.de.enige at gmail.com  Fri Oct  2 01:18:07 2009
From: eloy.de.enige at gmail.com (Eloy Duran)
Date: Fri, 2 Oct 2009 10:18:07 +0200
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
Message-ID: <D739ECF9-5C14-4979-A16E-545B86C3C769@gmail.com>

Hi Dylan,

> So, I've been mucking about with MacRuby lately. It's been fun so  
> far. Thanks to all the devs for this great project.

Welcome!

> I'm a pretty firm believer in unit testing my Ruby code. I love how  
> Ruby on Rails and similar frameworks nudge you in the right  
> direction by baking in an existing testing infrastructure.

Great, we agree! :)

> I've got testing pretty much figured out and was wondering if the  
> team would be open to modifying the basic Xcode project template to  
> add unit testing, with a stub test and test_suite file to get  
> started. This would also involve creating a framework for any  
> objective-c code that the user writes so that it can be included in  
> both the .app and the test files.

Well, unfortunately atm it's not that easy. Because we currently can't  
both run test::unit or minitest properly. I know the test::unit, which  
is currently in macruby's trunk, works work the greater part, but it's  
not ideal.

I have been working on this area for a while now, getting a little  
closer every time. This work is part of Rucola, which at some point  
will merge with HotCocoa and will provide a classic layout as you are  
accustomed to by frameworks such as Rails.

At this point, the test framework which we can fully run is Bacon,  
which is what I'm gonna base the rest of my current work on. However,  
once we can fully run minitest/test::unit we'll support that as well.  
More importantly right now is a working mocking and stubbing lib. My  
choice is Mocha, but MacRuby is not mature enough yet to do all the  
fancy meta stuff that is needed for this.

So for the time being, I'd say cool let's add it to the project  
template! But, on the long run this should all move to Rucola to  
provide one piece that pulls it all together. If you are interested on  
working on this, please contact me directly. Anyone can do that btw.

Cheers,
Eloy

From ruby-noreply at macosforge.org  Fri Oct  2 01:20:06 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 02 Oct 2009 08:20:06 -0000
Subject: [MacRuby-devel] [MacRuby] #362: Add Unit Testing and Embed
 MacRuby to Project Template
In-Reply-To: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
References: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
Message-ID: <059.419f756d5e90df620a98832ff7caadbb@macosforge.org>

#362: Add Unit Testing and Embed MacRuby to Project Template
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |       Owner:  lsansonetti@?        
     Type:  enhancement          |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------

Comment(by eloy.de.enige@?):

 As commented on the ML, for now I'd say it can go in the template, but on
 the long run this should be replaced by Rucola's testing support. If you
 want to use specs, skip the minitest one, you're better of using Bacon.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/362#comment:4>
MacRuby <http://macruby.org/>


From mattaimonetti at gmail.com  Fri Oct  2 01:24:31 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Fri, 2 Oct 2009 01:24:31 -0700
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <D739ECF9-5C14-4979-A16E-545B86C3C769@gmail.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<D739ECF9-5C14-4979-A16E-545B86C3C769@gmail.com>
Message-ID: <20fefa50910020124i3ee6325cva5380dc9b8dbe990@mail.gmail.com>

hmm for once I don't fully agree with Eloy :)

But, on the long run this should all move to Rucola to provide one piece
> that pulls it all together.
>

It's a small details but I think we do need a solid testing framework in
XCode too. Not everyone will use Rucola and therefore offering a great test
solution for both tools would be great.

I don't think Eloy was against such thing but I thought it was important to
mention it.

- Matt

On Fri, Oct 2, 2009 at 1:18 AM, Eloy Duran <eloy.de.enige at gmail.com> wrote:

> Hi Dylan,
>
>  So, I've been mucking about with MacRuby lately. It's been fun so far.
>> Thanks to all the devs for this great project.
>>
>
> Welcome!
>
>  I'm a pretty firm believer in unit testing my Ruby code. I love how Ruby
>> on Rails and similar frameworks nudge you in the right direction by baking
>> in an existing testing infrastructure.
>>
>
> Great, we agree! :)
>
>  I've got testing pretty much figured out and was wondering if the team
>> would be open to modifying the basic Xcode project template to add unit
>> testing, with a stub test and test_suite file to get started. This would
>> also involve creating a framework for any objective-c code that the user
>> writes so that it can be included in both the .app and the test files.
>>
>
> Well, unfortunately atm it's not that easy. Because we currently can't both
> run test::unit or minitest properly. I know the test::unit, which is
> currently in macruby's trunk, works work the greater part, but it's not
> ideal.
>
> I have been working on this area for a while now, getting a little closer
> every time. This work is part of Rucola, which at some point will merge with
> HotCocoa and will provide a classic layout as you are accustomed to by
> frameworks such as Rails.
>
> At this point, the test framework which we can fully run is Bacon, which is
> what I'm gonna base the rest of my current work on. However, once we can
> fully run minitest/test::unit we'll support that as well. More importantly
> right now is a working mocking and stubbing lib. My choice is Mocha, but
> MacRuby is not mature enough yet to do all the fancy meta stuff that is
> needed for this.
>
> So for the time being, I'd say cool let's add it to the project template!
> But, on the long run this should all move to Rucola to provide one piece
> that pulls it all together. If you are interested on working on this, please
> contact me directly. Anyone can do that btw.
>
> Cheers,
> Eloy
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/a1076d3c/attachment.html>

From ruby-noreply at macosforge.org  Fri Oct  2 01:26:57 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 02 Oct 2009 08:26:57 -0000
Subject: [MacRuby-devel] [MacRuby] #362: Add Unit Testing and Embed
 MacRuby to Project Template
In-Reply-To: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
References: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
Message-ID: <059.5231de3b1eeab44beab1584c5ae9d44b@macosforge.org>

#362: Add Unit Testing and Embed MacRuby to Project Template
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |       Owner:  eloy.de.enige@?        
     Type:  enhancement          |      Status:  new                    
 Priority:  trivial              |   Milestone:                         
Component:  MacRuby              |    Keywords:                         
---------------------------------+------------------------------------------
Changes (by eloy.de.enige@?):

  * owner:  lsansonetti@? => eloy.de.enige@?
  * priority:  blocker => trivial


Comment:

 Actually, after thinking about it a bit more, I'm still on the fence about
 adding it to the project templates now. Because A it doesn't work
 correctly yet and we would only be indicating to people that it is
 supported, which it isn't. And it might be weird for people that we add
 something and change it a month later? I personally don't have a big
 problem with the latter issue, but some might.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/362#comment:5>
MacRuby <http://macruby.org/>


From eloy.de.enige at gmail.com  Fri Oct  2 01:31:48 2009
From: eloy.de.enige at gmail.com (Eloy Duran)
Date: Fri, 2 Oct 2009 10:31:48 +0200
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <20fefa50910020124i3ee6325cva5380dc9b8dbe990@mail.gmail.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<D739ECF9-5C14-4979-A16E-545B86C3C769@gmail.com>
	<20fefa50910020124i3ee6325cva5380dc9b8dbe990@mail.gmail.com>
Message-ID: <3AE6C2C5-A9CC-4D5C-81E5-AAFABF90B1BC@gmail.com>

Hey Matt,

> hmm for once I don't fully agree with Eloy :)

I'm sure we've disagreed before ;-)

> But, on the long run this should all move to Rucola to provide one  
> piece that pulls it all together.
>
> It's a small details but I think we do need a solid testing  
> framework in XCode too. Not everyone will use Rucola and therefore  
> offering a great test solution for both tools would be great.

Rucola has always been about allowing Ruby devs _and_ xcode users to  
use it without knowing the difference. Also, Rucola/HotCocoa will come  
with MacRuby, so they can use it without knowing so.

> I don't think Eloy was against such thing but I thought it was  
> important to mention it.

I'm against maintaining duplicate stuff. People should just use the  
code which has been battle tested and has added facilities to make it  
easier, even if they don't know what it is their using in the  
bakcground. Ie, the test helper would just require the test case  
helper, the user doesn't need to know where it actually lives. Adding  
this to the project template makes people think they have to add  
facilities themselves imo.

Eloy

> On Fri, Oct 2, 2009 at 1:18 AM, Eloy Duran <eloy.de.enige at gmail.com>  
> wrote:
> Hi Dylan,
>
>
> So, I've been mucking about with MacRuby lately. It's been fun so  
> far. Thanks to all the devs for this great project.
>
> Welcome!
>
>
> I'm a pretty firm believer in unit testing my Ruby code. I love how  
> Ruby on Rails and similar frameworks nudge you in the right  
> direction by baking in an existing testing infrastructure.
>
> Great, we agree! :)
>
>
> I've got testing pretty much figured out and was wondering if the  
> team would be open to modifying the basic Xcode project template to  
> add unit testing, with a stub test and test_suite file to get  
> started. This would also involve creating a framework for any  
> objective-c code that the user writes so that it can be included in  
> both the .app and the test files.
>
> Well, unfortunately atm it's not that easy. Because we currently  
> can't both run test::unit or minitest properly. I know the  
> test::unit, which is currently in macruby's trunk, works work the  
> greater part, but it's not ideal.
>
> I have been working on this area for a while now, getting a little  
> closer every time. This work is part of Rucola, which at some point  
> will merge with HotCocoa and will provide a classic layout as you  
> are accustomed to by frameworks such as Rails.
>
> At this point, the test framework which we can fully run is Bacon,  
> which is what I'm gonna base the rest of my current work on.  
> However, once we can fully run minitest/test::unit we'll support  
> that as well. More importantly right now is a working mocking and  
> stubbing lib. My choice is Mocha, but MacRuby is not mature enough  
> yet to do all the fancy meta stuff that is needed for this.
>
> So for the time being, I'd say cool let's add it to the project  
> template! But, on the long run this should all move to Rucola to  
> provide one piece that pulls it all together. If you are interested  
> on working on this, please contact me directly. Anyone can do that  
> btw.
>
> Cheers,
> Eloy
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/a00c34d3/attachment-0001.html>

From dylan at ideaswarm.com  Fri Oct  2 10:44:36 2009
From: dylan at ideaswarm.com (Dylan Bruzenak)
Date: Fri, 2 Oct 2009 12:44:36 -0500
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <3AE6C2C5-A9CC-4D5C-81E5-AAFABF90B1BC@gmail.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<D739ECF9-5C14-4979-A16E-545B86C3C769@gmail.com>
	<20fefa50910020124i3ee6325cva5380dc9b8dbe990@mail.gmail.com>
	<3AE6C2C5-A9CC-4D5C-81E5-AAFABF90B1BC@gmail.com>
Message-ID: <aea090980910021044gab6d818o64f87044c30f4265@mail.gmail.com>

First, I completely agree on reducing duplicated effort, but I have a few
questions. Let me know if you want to move this discussion off list or feel
free to just answer these off list.

First, being new to the Ruby on Mac eco-system:

What is the timeline for merging rucola into HotCocoa vs extending HotCocoa
to have the functionality that is present in RubyCocoa rucola ?

What are the major blockers/good places to start looking to help out the
MacRubyification of the rucola framework ?

Is rucola a command line only generation framework, or will there be support
for creating projects in Xcode as well ? My current focus as a new user is
helping to smooth the transition for other new users from Obj-c to Ruby
development. Being able to stay in Xcode  and use standard templates and IB
for initial development really helps ease the transition. Command line
generation is fantastic from the 'coming from Rails' perspective, but not so
great for the coming from Xcode perspective, where you expect this to be
handled by targets and build steps.

I've been on both sides of this, even having written my own hotcocoa like
framework for ruby gtk at one point that never ended up getting released.
Now I'm a bit spoiled by IB and bindings and will tend to avoid hand coding
UI's unless they need to be dynamic, in which case projects like hotcocoa
provide a fantastic interface.

>From the testing perspective: I've only tried naive tests with the standard
test::unit style so far but everything seems to be working. What are the
missing/broken parts that I haven't run into yet ?

I understand re: including testing appearing to be supporting it. Could that
be reduced by adding comments to the effect that some things may not work to
the template or better documentation on what is supported ?

My main concern here is that people like me who would want to try out
MacRuby may have to replicate the admittedly limited integration work and
snooping that I've done here (since it is not obvious that it isn't
supported, so of course you go to try it out), replicating the effort and
running into a disheartening wall anyway. Or worse, they could choose not to
go beyond initial experiments with MacRuby due to the lack of apparent
support for testing. So either way, the current state of testing should
probably be addressed somewhere with a call to arms :)

- Dylan

On Fri, Oct 2, 2009 at 3:31 AM, Eloy Duran <eloy.de.enige at gmail.com> wrote:

> Hey Matt,
>
> hmm for once I don't fully agree with Eloy :)
>
>
> I'm sure we've disagreed before ;-)
>
> But, on the long run this should all move to Rucola to provide one piece
>> that pulls it all together.
>>
>
> It's a small details but I think we do need a solid testing framework in
> XCode too. Not everyone will use Rucola and therefore offering a great test
> solution for both tools would be great.
>
>
> Rucola has always been about allowing Ruby devs _and_ xcode users to use it
> without knowing the difference. Also, Rucola/HotCocoa will come with
> MacRuby, so they can use it without knowing so.
>
> I don't think Eloy was against such thing but I thought it was important to
> mention it.
>
>
> I'm against maintaining duplicate stuff. People should just use the code
> which has been battle tested and has added facilities to make it easier,
> even if they don't know what it is their using in the bakcground. Ie, the
> test helper would just require the test case helper, the user doesn't need
> to know where it actually lives. Adding this to the project template makes
> people think they have to add facilities themselves imo.
>
> Eloy
>
> On Fri, Oct 2, 2009 at 1:18 AM, Eloy Duran <eloy.de.enige at gmail.com>wrote:
>
>> Hi Dylan,
>>
>>  So, I've been mucking about with MacRuby lately. It's been fun so far.
>>> Thanks to all the devs for this great project.
>>>
>>
>> Welcome!
>>
>>  I'm a pretty firm believer in unit testing my Ruby code. I love how Ruby
>>> on Rails and similar frameworks nudge you in the right direction by baking
>>> in an existing testing infrastructure.
>>>
>>
>> Great, we agree! :)
>>
>>  I've got testing pretty much figured out and was wondering if the team
>>> would be open to modifying the basic Xcode project template to add unit
>>> testing, with a stub test and test_suite file to get started. This would
>>> also involve creating a framework for any objective-c code that the user
>>> writes so that it can be included in both the .app and the test files.
>>>
>>
>> Well, unfortunately atm it's not that easy. Because we currently can't
>> both run test::unit or minitest properly. I know the test::unit, which is
>> currently in macruby's trunk, works work the greater part, but it's not
>> ideal.
>>
>> I have been working on this area for a while now, getting a little closer
>> every time. This work is part of Rucola, which at some point will merge with
>> HotCocoa and will provide a classic layout as you are accustomed to by
>> frameworks such as Rails.
>>
>> At this point, the test framework which we can fully run is Bacon, which
>> is what I'm gonna base the rest of my current work on. However, once we can
>> fully run minitest/test::unit we'll support that as well. More importantly
>> right now is a working mocking and stubbing lib. My choice is Mocha, but
>> MacRuby is not mature enough yet to do all the fancy meta stuff that is
>> needed for this.
>>
>> So for the time being, I'd say cool let's add it to the project template!
>> But, on the long run this should all move to Rucola to provide one piece
>> that pulls it all together. If you are interested on working on this, please
>> contact me directly. Anyone can do that btw.
>>
>> Cheers,
>> Eloy
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/5d23585a/attachment.html>

From mattaimonetti at gmail.com  Fri Oct  2 10:59:33 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Fri, 2 Oct 2009 10:59:33 -0700
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <aea090980910021044gab6d818o64f87044c30f4265@mail.gmail.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<D739ECF9-5C14-4979-A16E-545B86C3C769@gmail.com>
	<20fefa50910020124i3ee6325cva5380dc9b8dbe990@mail.gmail.com>
	<3AE6C2C5-A9CC-4D5C-81E5-AAFABF90B1BC@gmail.com>
	<aea090980910021044gab6d818o64f87044c30f4265@mail.gmail.com>
Message-ID: <20fefa50910021059x31240abfqd5fd605b5aa2ec91@mail.gmail.com>

Hey Dylan,

Quick side note, let's not jump to conclusions here, nothing was decided yet
and we are just discussing options.
I think you have a valid point and it needs to be discussed, having the
feedback from someone coming from your side of your fence is very useful and
please don't stop arguing for what you think would be better for people
coming from the Xcode world, we really need that opinion to create a better
tool  :)

Thanks,

- Matt




On Fri, Oct 2, 2009 at 10:44 AM, Dylan Bruzenak <dylan at ideaswarm.com> wrote:

> First, I completely agree on reducing duplicated effort, but I have a few
> questions. Let me know if you want to move this discussion off list or feel
> free to just answer these off list.
>
> First, being new to the Ruby on Mac eco-system:
>
> What is the timeline for merging rucola into HotCocoa vs extending HotCocoa
> to have the functionality that is present in RubyCocoa rucola ?
>
> What are the major blockers/good places to start looking to help out the
> MacRubyification of the rucola framework ?
>
> Is rucola a command line only generation framework, or will there be
> support for creating projects in Xcode as well ? My current focus as a new
> user is helping to smooth the transition for other new users from Obj-c to
> Ruby development. Being able to stay in Xcode  and use standard templates
> and IB for initial development really helps ease the transition. Command
> line generation is fantastic from the 'coming from Rails' perspective, but
> not so great for the coming from Xcode perspective, where you expect this to
> be handled by targets and build steps.
>
> I've been on both sides of this, even having written my own hotcocoa like
> framework for ruby gtk at one point that never ended up getting released.
> Now I'm a bit spoiled by IB and bindings and will tend to avoid hand coding
> UI's unless they need to be dynamic, in which case projects like hotcocoa
> provide a fantastic interface.
>
> From the testing perspective: I've only tried naive tests with the standard
> test::unit style so far but everything seems to be working. What are the
> missing/broken parts that I haven't run into yet ?
>
> I understand re: including testing appearing to be supporting it. Could
> that be reduced by adding comments to the effect that some things may not
> work to the template or better documentation on what is supported ?
>
> My main concern here is that people like me who would want to try out
> MacRuby may have to replicate the admittedly limited integration work and
> snooping that I've done here (since it is not obvious that it isn't
> supported, so of course you go to try it out), replicating the effort and
> running into a disheartening wall anyway. Or worse, they could choose not to
> go beyond initial experiments with MacRuby due to the lack of apparent
> support for testing. So either way, the current state of testing should
> probably be addressed somewhere with a call to arms :)
>
> - Dylan
>
> On Fri, Oct 2, 2009 at 3:31 AM, Eloy Duran <eloy.de.enige at gmail.com>wrote:
>
>> Hey Matt,
>>
>> hmm for once I don't fully agree with Eloy :)
>>
>>
>> I'm sure we've disagreed before ;-)
>>
>> But, on the long run this should all move to Rucola to provide one piece
>>> that pulls it all together.
>>>
>>
>> It's a small details but I think we do need a solid testing framework in
>> XCode too. Not everyone will use Rucola and therefore offering a great test
>> solution for both tools would be great.
>>
>>
>> Rucola has always been about allowing Ruby devs _and_ xcode users to use
>> it without knowing the difference. Also, Rucola/HotCocoa will come with
>> MacRuby, so they can use it without knowing so.
>>
>> I don't think Eloy was against such thing but I thought it was important
>> to mention it.
>>
>>
>> I'm against maintaining duplicate stuff. People should just use the code
>> which has been battle tested and has added facilities to make it easier,
>> even if they don't know what it is their using in the bakcground. Ie, the
>> test helper would just require the test case helper, the user doesn't need
>> to know where it actually lives. Adding this to the project template makes
>> people think they have to add facilities themselves imo.
>>
>> Eloy
>>
>> On Fri, Oct 2, 2009 at 1:18 AM, Eloy Duran <eloy.de.enige at gmail.com>wrote:
>>
>>> Hi Dylan,
>>>
>>>  So, I've been mucking about with MacRuby lately. It's been fun so far.
>>>> Thanks to all the devs for this great project.
>>>>
>>>
>>> Welcome!
>>>
>>>  I'm a pretty firm believer in unit testing my Ruby code. I love how Ruby
>>>> on Rails and similar frameworks nudge you in the right direction by baking
>>>> in an existing testing infrastructure.
>>>>
>>>
>>> Great, we agree! :)
>>>
>>>  I've got testing pretty much figured out and was wondering if the team
>>>> would be open to modifying the basic Xcode project template to add unit
>>>> testing, with a stub test and test_suite file to get started. This would
>>>> also involve creating a framework for any objective-c code that the user
>>>> writes so that it can be included in both the .app and the test files.
>>>>
>>>
>>> Well, unfortunately atm it's not that easy. Because we currently can't
>>> both run test::unit or minitest properly. I know the test::unit, which is
>>> currently in macruby's trunk, works work the greater part, but it's not
>>> ideal.
>>>
>>> I have been working on this area for a while now, getting a little closer
>>> every time. This work is part of Rucola, which at some point will merge with
>>> HotCocoa and will provide a classic layout as you are accustomed to by
>>> frameworks such as Rails.
>>>
>>> At this point, the test framework which we can fully run is Bacon, which
>>> is what I'm gonna base the rest of my current work on. However, once we can
>>> fully run minitest/test::unit we'll support that as well. More importantly
>>> right now is a working mocking and stubbing lib. My choice is Mocha, but
>>> MacRuby is not mature enough yet to do all the fancy meta stuff that is
>>> needed for this.
>>>
>>> So for the time being, I'd say cool let's add it to the project template!
>>> But, on the long run this should all move to Rucola to provide one piece
>>> that pulls it all together. If you are interested on working on this, please
>>> contact me directly. Anyone can do that btw.
>>>
>>> Cheers,
>>> Eloy
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/6e52cd05/attachment-0001.html>

From dylan at ideaswarm.com  Fri Oct  2 11:30:15 2009
From: dylan at ideaswarm.com (Dylan Bruzenak)
Date: Fri, 2 Oct 2009 13:30:15 -0500
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <20fefa50910021059x31240abfqd5fd605b5aa2ec91@mail.gmail.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<D739ECF9-5C14-4979-A16E-545B86C3C769@gmail.com>
	<20fefa50910020124i3ee6325cva5380dc9b8dbe990@mail.gmail.com>
	<3AE6C2C5-A9CC-4D5C-81E5-AAFABF90B1BC@gmail.com>
	<aea090980910021044gab6d818o64f87044c30f4265@mail.gmail.com>
	<20fefa50910021059x31240abfqd5fd605b5aa2ec91@mail.gmail.com>
Message-ID: <aea090980910021130p5637140fjd254f5a721f515c0@mail.gmail.com>

I'm trying not to jump to conclusions, just feeling out the space and trying
to open up the discussion a bit. Not having as clear of a perspective as you
guys, obviously, I'm just stating a few rogue opinions and trying to come up
to speed, letting you know my current thoughts. I'm not married to many of
them.
Text can be brutal as you don't get the intonation. Please read the above
with a friendly/questioning tone rather than a confrontational one. At the
end of the day it isn't my project so I'm not about to start pushing my
ideas; that said I'm really excited about it and have a bajillion questions,
concerns, and little bumps I hit that I want to smooth out as much as is
feasible. Obviously I won't understand all the barriers yet as I'm learning
and I appreciate the 'well, duh' hand holding in the meantime.

- Dylan

On Fri, Oct 2, 2009 at 12:59 PM, Matt Aimonetti <mattaimonetti at gmail.com>wrote:

> Hey Dylan,
>
> Quick side note, let's not jump to conclusions here, nothing was decided
> yet and we are just discussing options.
> I think you have a valid point and it needs to be discussed, having the
> feedback from someone coming from your side of your fence is very useful and
> please don't stop arguing for what you think would be better for people
> coming from the Xcode world, we really need that opinion to create a better
> tool  :)
>
> Thanks,
>
> - Matt
>
>
>
>
>
> On Fri, Oct 2, 2009 at 10:44 AM, Dylan Bruzenak <dylan at ideaswarm.com>wrote:
>
>> First, I completely agree on reducing duplicated effort, but I have a few
>> questions. Let me know if you want to move this discussion off list or feel
>> free to just answer these off list.
>>
>> First, being new to the Ruby on Mac eco-system:
>>
>> What is the timeline for merging rucola into HotCocoa vs extending
>> HotCocoa to have the functionality that is present in RubyCocoa rucola ?
>>
>> What are the major blockers/good places to start looking to help out the
>> MacRubyification of the rucola framework ?
>>
>> Is rucola a command line only generation framework, or will there be
>> support for creating projects in Xcode as well ? My current focus as a new
>> user is helping to smooth the transition for other new users from Obj-c to
>> Ruby development. Being able to stay in Xcode  and use standard templates
>> and IB for initial development really helps ease the transition. Command
>> line generation is fantastic from the 'coming from Rails' perspective, but
>> not so great for the coming from Xcode perspective, where you expect this to
>> be handled by targets and build steps.
>>
>> I've been on both sides of this, even having written my own hotcocoa like
>> framework for ruby gtk at one point that never ended up getting released.
>> Now I'm a bit spoiled by IB and bindings and will tend to avoid hand coding
>> UI's unless they need to be dynamic, in which case projects like hotcocoa
>> provide a fantastic interface.
>>
>> From the testing perspective: I've only tried naive tests with the
>> standard test::unit style so far but everything seems to be working. What
>> are the missing/broken parts that I haven't run into yet ?
>>
>> I understand re: including testing appearing to be supporting it. Could
>> that be reduced by adding comments to the effect that some things may not
>> work to the template or better documentation on what is supported ?
>>
>> My main concern here is that people like me who would want to try out
>> MacRuby may have to replicate the admittedly limited integration work and
>> snooping that I've done here (since it is not obvious that it isn't
>> supported, so of course you go to try it out), replicating the effort and
>> running into a disheartening wall anyway. Or worse, they could choose not to
>> go beyond initial experiments with MacRuby due to the lack of apparent
>> support for testing. So either way, the current state of testing should
>> probably be addressed somewhere with a call to arms :)
>>
>> - Dylan
>>
>> On Fri, Oct 2, 2009 at 3:31 AM, Eloy Duran <eloy.de.enige at gmail.com>wrote:
>>
>>> Hey Matt,
>>>
>>> hmm for once I don't fully agree with Eloy :)
>>>
>>>
>>> I'm sure we've disagreed before ;-)
>>>
>>> But, on the long run this should all move to Rucola to provide one piece
>>>> that pulls it all together.
>>>>
>>>
>>> It's a small details but I think we do need a solid testing framework in
>>> XCode too. Not everyone will use Rucola and therefore offering a great test
>>> solution for both tools would be great.
>>>
>>>
>>> Rucola has always been about allowing Ruby devs _and_ xcode users to use
>>> it without knowing the difference. Also, Rucola/HotCocoa will come with
>>> MacRuby, so they can use it without knowing so.
>>>
>>> I don't think Eloy was against such thing but I thought it was important
>>> to mention it.
>>>
>>>
>>> I'm against maintaining duplicate stuff. People should just use the code
>>> which has been battle tested and has added facilities to make it easier,
>>> even if they don't know what it is their using in the bakcground. Ie, the
>>> test helper would just require the test case helper, the user doesn't need
>>> to know where it actually lives. Adding this to the project template makes
>>> people think they have to add facilities themselves imo.
>>>
>>> Eloy
>>>
>>> On Fri, Oct 2, 2009 at 1:18 AM, Eloy Duran <eloy.de.enige at gmail.com>wrote:
>>>
>>>> Hi Dylan,
>>>>
>>>>  So, I've been mucking about with MacRuby lately. It's been fun so far.
>>>>> Thanks to all the devs for this great project.
>>>>>
>>>>
>>>> Welcome!
>>>>
>>>>  I'm a pretty firm believer in unit testing my Ruby code. I love how
>>>>> Ruby on Rails and similar frameworks nudge you in the right direction by
>>>>> baking in an existing testing infrastructure.
>>>>>
>>>>
>>>> Great, we agree! :)
>>>>
>>>>  I've got testing pretty much figured out and was wondering if the team
>>>>> would be open to modifying the basic Xcode project template to add unit
>>>>> testing, with a stub test and test_suite file to get started. This would
>>>>> also involve creating a framework for any objective-c code that the user
>>>>> writes so that it can be included in both the .app and the test files.
>>>>>
>>>>
>>>> Well, unfortunately atm it's not that easy. Because we currently can't
>>>> both run test::unit or minitest properly. I know the test::unit, which is
>>>> currently in macruby's trunk, works work the greater part, but it's not
>>>> ideal.
>>>>
>>>> I have been working on this area for a while now, getting a little
>>>> closer every time. This work is part of Rucola, which at some point will
>>>> merge with HotCocoa and will provide a classic layout as you are accustomed
>>>> to by frameworks such as Rails.
>>>>
>>>> At this point, the test framework which we can fully run is Bacon, which
>>>> is what I'm gonna base the rest of my current work on. However, once we can
>>>> fully run minitest/test::unit we'll support that as well. More importantly
>>>> right now is a working mocking and stubbing lib. My choice is Mocha, but
>>>> MacRuby is not mature enough yet to do all the fancy meta stuff that is
>>>> needed for this.
>>>>
>>>> So for the time being, I'd say cool let's add it to the project
>>>> template! But, on the long run this should all move to Rucola to provide one
>>>> piece that pulls it all together. If you are interested on working on this,
>>>> please contact me directly. Anyone can do that btw.
>>>>
>>>> Cheers,
>>>> Eloy
>>>>
>>>> _______________________________________________
>>>> MacRuby-devel mailing list
>>>> MacRuby-devel at lists.macosforge.org
>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>>
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>>
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/3d154a03/attachment.html>

From dylan at ideaswarm.com  Fri Oct  2 11:46:55 2009
From: dylan at ideaswarm.com (Dylan Bruzenak)
Date: Fri, 2 Oct 2009 13:46:55 -0500
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <aea090980910021130p5637140fjd254f5a721f515c0@mail.gmail.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<D739ECF9-5C14-4979-A16E-545B86C3C769@gmail.com>
	<20fefa50910020124i3ee6325cva5380dc9b8dbe990@mail.gmail.com>
	<3AE6C2C5-A9CC-4D5C-81E5-AAFABF90B1BC@gmail.com>
	<aea090980910021044gab6d818o64f87044c30f4265@mail.gmail.com>
	<20fefa50910021059x31240abfqd5fd605b5aa2ec91@mail.gmail.com>
	<aea090980910021130p5637140fjd254f5a721f515c0@mail.gmail.com>
Message-ID: <aea090980910021146n6c6a75e7x6c20a5501d7d4e84@mail.gmail.com>

As for the Xcode templates, I think Eloy has great points, most of which I'm
too in the dark to really grok yet. I'm wondering first if we can come up
with a stop gap solution (or if it is wise to do so) to easy the transition
for some users now and then the rest of my questions basically revolve
around how things should be implemented, the right way, which sounds like
rucola integration.
- Dylan

On Fri, Oct 2, 2009 at 1:30 PM, Dylan Bruzenak <dylan at ideaswarm.com> wrote:

> I'm trying not to jump to conclusions, just feeling out the space and
> trying to open up the discussion a bit. Not having as clear of a perspective
> as you guys, obviously, I'm just stating a few rogue opinions and trying to
> come up to speed, letting you know my current thoughts. I'm not married to
> many of them.
> Text can be brutal as you don't get the intonation. Please read the above
> with a friendly/questioning tone rather than a confrontational one. At the
> end of the day it isn't my project so I'm not about to start pushing my
> ideas; that said I'm really excited about it and have a bajillion questions,
> concerns, and little bumps I hit that I want to smooth out as much as is
> feasible. Obviously I won't understand all the barriers yet as I'm learning
> and I appreciate the 'well, duh' hand holding in the meantime.
>
> - Dylan
>
>
> On Fri, Oct 2, 2009 at 12:59 PM, Matt Aimonetti <mattaimonetti at gmail.com>wrote:
>
>> Hey Dylan,
>>
>> Quick side note, let's not jump to conclusions here, nothing was decided
>> yet and we are just discussing options.
>> I think you have a valid point and it needs to be discussed, having the
>> feedback from someone coming from your side of your fence is very useful and
>> please don't stop arguing for what you think would be better for people
>> coming from the Xcode world, we really need that opinion to create a better
>> tool  :)
>>
>> Thanks,
>>
>> - Matt
>>
>>
>>
>>
>>
>> On Fri, Oct 2, 2009 at 10:44 AM, Dylan Bruzenak <dylan at ideaswarm.com>wrote:
>>
>>> First, I completely agree on reducing duplicated effort, but I have a few
>>> questions. Let me know if you want to move this discussion off list or feel
>>> free to just answer these off list.
>>>
>>> First, being new to the Ruby on Mac eco-system:
>>>
>>> What is the timeline for merging rucola into HotCocoa vs extending
>>> HotCocoa to have the functionality that is present in RubyCocoa rucola ?
>>>
>>> What are the major blockers/good places to start looking to help out the
>>> MacRubyification of the rucola framework ?
>>>
>>> Is rucola a command line only generation framework, or will there be
>>> support for creating projects in Xcode as well ? My current focus as a new
>>> user is helping to smooth the transition for other new users from Obj-c to
>>> Ruby development. Being able to stay in Xcode  and use standard templates
>>> and IB for initial development really helps ease the transition. Command
>>> line generation is fantastic from the 'coming from Rails' perspective, but
>>> not so great for the coming from Xcode perspective, where you expect this to
>>> be handled by targets and build steps.
>>>
>>> I've been on both sides of this, even having written my own hotcocoa like
>>> framework for ruby gtk at one point that never ended up getting released.
>>> Now I'm a bit spoiled by IB and bindings and will tend to avoid hand coding
>>> UI's unless they need to be dynamic, in which case projects like hotcocoa
>>> provide a fantastic interface.
>>>
>>> From the testing perspective: I've only tried naive tests with the
>>> standard test::unit style so far but everything seems to be working. What
>>> are the missing/broken parts that I haven't run into yet ?
>>>
>>> I understand re: including testing appearing to be supporting it. Could
>>> that be reduced by adding comments to the effect that some things may not
>>> work to the template or better documentation on what is supported ?
>>>
>>> My main concern here is that people like me who would want to try out
>>> MacRuby may have to replicate the admittedly limited integration work and
>>> snooping that I've done here (since it is not obvious that it isn't
>>> supported, so of course you go to try it out), replicating the effort and
>>> running into a disheartening wall anyway. Or worse, they could choose not to
>>> go beyond initial experiments with MacRuby due to the lack of apparent
>>> support for testing. So either way, the current state of testing should
>>> probably be addressed somewhere with a call to arms :)
>>>
>>> - Dylan
>>>
>>> On Fri, Oct 2, 2009 at 3:31 AM, Eloy Duran <eloy.de.enige at gmail.com>wrote:
>>>
>>>> Hey Matt,
>>>>
>>>> hmm for once I don't fully agree with Eloy :)
>>>>
>>>>
>>>> I'm sure we've disagreed before ;-)
>>>>
>>>> But, on the long run this should all move to Rucola to provide one piece
>>>>> that pulls it all together.
>>>>>
>>>>
>>>> It's a small details but I think we do need a solid testing framework in
>>>> XCode too. Not everyone will use Rucola and therefore offering a great test
>>>> solution for both tools would be great.
>>>>
>>>>
>>>> Rucola has always been about allowing Ruby devs _and_ xcode users to use
>>>> it without knowing the difference. Also, Rucola/HotCocoa will come with
>>>> MacRuby, so they can use it without knowing so.
>>>>
>>>> I don't think Eloy was against such thing but I thought it was important
>>>> to mention it.
>>>>
>>>>
>>>> I'm against maintaining duplicate stuff. People should just use the code
>>>> which has been battle tested and has added facilities to make it easier,
>>>> even if they don't know what it is their using in the bakcground. Ie, the
>>>> test helper would just require the test case helper, the user doesn't need
>>>> to know where it actually lives. Adding this to the project template makes
>>>> people think they have to add facilities themselves imo.
>>>>
>>>> Eloy
>>>>
>>>> On Fri, Oct 2, 2009 at 1:18 AM, Eloy Duran <eloy.de.enige at gmail.com>wrote:
>>>>
>>>>> Hi Dylan,
>>>>>
>>>>>  So, I've been mucking about with MacRuby lately. It's been fun so far.
>>>>>> Thanks to all the devs for this great project.
>>>>>>
>>>>>
>>>>> Welcome!
>>>>>
>>>>>  I'm a pretty firm believer in unit testing my Ruby code. I love how
>>>>>> Ruby on Rails and similar frameworks nudge you in the right direction by
>>>>>> baking in an existing testing infrastructure.
>>>>>>
>>>>>
>>>>> Great, we agree! :)
>>>>>
>>>>>  I've got testing pretty much figured out and was wondering if the team
>>>>>> would be open to modifying the basic Xcode project template to add unit
>>>>>> testing, with a stub test and test_suite file to get started. This would
>>>>>> also involve creating a framework for any objective-c code that the user
>>>>>> writes so that it can be included in both the .app and the test files.
>>>>>>
>>>>>
>>>>> Well, unfortunately atm it's not that easy. Because we currently can't
>>>>> both run test::unit or minitest properly. I know the test::unit, which is
>>>>> currently in macruby's trunk, works work the greater part, but it's not
>>>>> ideal.
>>>>>
>>>>> I have been working on this area for a while now, getting a little
>>>>> closer every time. This work is part of Rucola, which at some point will
>>>>> merge with HotCocoa and will provide a classic layout as you are accustomed
>>>>> to by frameworks such as Rails.
>>>>>
>>>>> At this point, the test framework which we can fully run is Bacon,
>>>>> which is what I'm gonna base the rest of my current work on. However, once
>>>>> we can fully run minitest/test::unit we'll support that as well. More
>>>>> importantly right now is a working mocking and stubbing lib. My choice is
>>>>> Mocha, but MacRuby is not mature enough yet to do all the fancy meta stuff
>>>>> that is needed for this.
>>>>>
>>>>> So for the time being, I'd say cool let's add it to the project
>>>>> template! But, on the long run this should all move to Rucola to provide one
>>>>> piece that pulls it all together. If you are interested on working on this,
>>>>> please contact me directly. Anyone can do that btw.
>>>>>
>>>>> Cheers,
>>>>> Eloy
>>>>>
>>>>> _______________________________________________
>>>>> MacRuby-devel mailing list
>>>>> MacRuby-devel at lists.macosforge.org
>>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>>>
>>>>
>>>> _______________________________________________
>>>> MacRuby-devel mailing list
>>>> MacRuby-devel at lists.macosforge.org
>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> MacRuby-devel mailing list
>>>> MacRuby-devel at lists.macosforge.org
>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>>
>>>>
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/40f9a2f9/attachment-0001.html>

From lsansonetti at apple.com  Fri Oct  2 11:48:07 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Fri, 02 Oct 2009 11:48:07 -0700
Subject: [MacRuby-devel] Supported classes & methods diagram fed from
 rubyspec
In-Reply-To: <D0AA1C17-5F29-42FB-A5B1-BD5611EF37FE@gmail.com>
References: <E148045D-99B5-4CB6-9542-2973197873A4@gmail.com>
	<9939E537-6087-41E2-8EBD-A818C1C5B06F@apple.com>
	<D0AA1C17-5F29-42FB-A5B1-BD5611EF37FE@gmail.com>
Message-ID: <E24BEB42-0CC6-48D1-B897-F2FF8A45CFD5@apple.com>

Hi Ben,

I wasn't aware of that project, it looks good indeed. And the fact  
that it can be reused for different implementations of Ruby is very  
cool too :)

Laurent

On Oct 1, 2009, at 11:48 PM, Ben Schwarz wrote:

> Laurent,
>
> I just had a quick chat with Brian Ford (Rubinius) apparently  
> they're looking at using some incarnation of git://github.com/madriska/unity.git 
>  (http://unity.madriska.com/)
> Which uses a YAML formatter for mspec. (http://github.com/madriska/mspec/commit/36b8bce62c272d546bcbd8ab9f136576ff4701e5 
> )
>
> I think this might be the best way to get something that works  
> running. I'm sure that all the ruby implementations would benefit  
> from the shared work effort in this regard.
> We could start by investigating unity, chatting to the author and  
> seeing if we can make some contributions.
>
>
>
>
> On 02/10/2009, at 4:23 PM, Laurent Sansonetti wrote:
>
>> Hi Ben,
>>
>> That sounds like a good idea and looks like what I had in mind.
>>
>> I was thinking of having a status page, that shows hitlist items  
>> (critical bugs / things to do for the upcoming release), some  
>> rubyspec progress, a link to the latest nighty build, etc.
>>
>> The hitlist thing could be generated from a local file from the  
>> repository. We currently use TODO for that.
>>
>> We wrote a special mspec formatter in order to know what percentage  
>> of a given spec category we do pass. But having a more detailed  
>> view (classes / methods as you suggested) might be more  
>> interesting, this way we know on what class / method to focus in  
>> priority. Assuming that the mspec formatter is altered a little  
>> bit, this information could also be generated after a spec:ci pass.
>>
>> Is that what you had in mind?
>>
>> I guess the challenge here is to write a program that generates a  
>> Webby page for our website, commit it to the repository every time  
>> a change is made, then we would re-deploy the site right after.
>>
>> Laurent
>>
>> On Oct 1, 2009, at 11:01 PM, Ben Schwarz wrote:
>>
>>> Hi all,
>>>
>>>
>>> I've had some loose discussions with @lrz regarding a visual  
>>> representation of classes and methods that are working via the  
>>> rubyspec.
>>> This would enable developers to find an area of development to  
>>> focus on and also for end-users to understand what they might face  
>>> before
>>> conducting any development using macruby (bringing real  
>>> applications closer to tuition, rather than a start/stop experience)
>>>
>>> I'm happy to offer some hours to get something together that is  
>>> styled like macruby.org but I obviously need to:
>>>
>>> 	A) consult the group
>>> 	B) work out a spec
>>> 	C) have something setup on the macruby.org infrastructure.
>>>
>>>
>>> Discuss.
>>>
>>>
>>> Cheers,
>>>
>>> -
>>>
>>> Ben Schwarz
>>> Web architect
>>>
>>> Web:		http://www.germanforblack.com
>>> Mobile: 		+61 407 339 418
>>>
>>> -- 
>>> Please consider your environment before printing or distributing  
>>> this material.
>>> --
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From lsansonetti at apple.com  Fri Oct  2 11:49:31 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Fri, 02 Oct 2009 11:49:31 -0700
Subject: [MacRuby-devel] How to compile all ruby files in a
 project	using macrubyc
In-Reply-To: <951638E8-E69C-42C5-9CD1-125F763E0143@ideaswarm.com>
References: <aea090980910012339k6d08a22agee1a8bcbebc88c36@mail.gmail.com>
	<22A9350F-694E-4AE2-A6A3-E58B6CDC60A7@apple.com>
	<951638E8-E69C-42C5-9CD1-125F763E0143@ideaswarm.com>
Message-ID: <6E4F1C8C-8984-483F-9544-656DA687B963@apple.com>

0.5 is scheduled for the end of the year, with a set of beta releases  
before. We didn't set a date in stone yet because we want to ship it  
when it's really ready :)

Laurent

On Oct 2, 2009, at 12:02 AM, Dylan wrote:

> Good to know :)
>
> Hate to ask since I can never answer this question myself: do you  
> have a loose timeline for the release ?
>
> -Dylan
>
> On Oct 2, 2009, at 1:54 AM, Laurent Sansonetti  
> <lsansonetti at apple.com> wrote:
>
>> Hi Dylan,
>>
>> The AOT compilation of an Xcode project is still not finalized.  
>> It's technically possible to do it with the current macrubyc on the  
>> command line but it's kind of hard and we still have problems with  
>> #require statements. We will introduce an Xcode target that does it  
>> automatically for the 0.5 release.
>>
>> I guess the target could indeed by added by default to the  
>> templates once it's functional :)
>>
>> Laurent
>>
>> On Oct 1, 2009, at 11:39 PM, Dylan Bruzenak wrote:
>>
>>> I'm a bit of a newbie when it comes to command line compilation.
>>>
>>> Is there an easy way for me to basically just say: compile  
>>> everything recursively, starting at this directory ? Given that,  
>>> what would be the best way to then integrate that with an Xcode  
>>> project as part of a target ?
>>>
>>> Also, is this far enough along to consider adding to the project  
>>> templates by default ?
>>>
>>> thanks!
>>>
>>> - Dylan
>>>
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From dylan at ideaswarm.com  Fri Oct  2 11:51:56 2009
From: dylan at ideaswarm.com (Dylan Bruzenak)
Date: Fri, 2 Oct 2009 13:51:56 -0500
Subject: [MacRuby-devel] How to compile all ruby files in a project
	using macrubyc
In-Reply-To: <6E4F1C8C-8984-483F-9544-656DA687B963@apple.com>
References: <aea090980910012339k6d08a22agee1a8bcbebc88c36@mail.gmail.com>
	<22A9350F-694E-4AE2-A6A3-E58B6CDC60A7@apple.com>
	<951638E8-E69C-42C5-9CD1-125F763E0143@ideaswarm.com>
	<6E4F1C8C-8984-483F-9544-656DA687B963@apple.com>
Message-ID: <aea090980910021151r17029c66m7d5c6d8c6242b59b@mail.gmail.com>

Thanks!
Mostly I'm looking at doing some real commercial development here and it
helps to know the timeline and how you feel about the stability. Certainly
beats the daylights out of bracket soup. But in order to do that I basically
need to keep my code from being editable and readable by anyone who chooses
'show package contents' :)

- Dylan

On Fri, Oct 2, 2009 at 1:49 PM, Laurent Sansonetti <lsansonetti at apple.com>wrote:

> 0.5 is scheduled for the end of the year, with a set of beta releases
> before. We didn't set a date in stone yet because we want to ship it when
> it's really ready :)
>
> Laurent
>
>
> On Oct 2, 2009, at 12:02 AM, Dylan wrote:
>
>  Good to know :)
>>
>> Hate to ask since I can never answer this question myself: do you have a
>> loose timeline for the release ?
>>
>> -Dylan
>>
>> On Oct 2, 2009, at 1:54 AM, Laurent Sansonetti <lsansonetti at apple.com>
>> wrote:
>>
>>  Hi Dylan,
>>>
>>> The AOT compilation of an Xcode project is still not finalized. It's
>>> technically possible to do it with the current macrubyc on the command line
>>> but it's kind of hard and we still have problems with #require statements.
>>> We will introduce an Xcode target that does it automatically for the 0.5
>>> release.
>>>
>>> I guess the target could indeed by added by default to the templates once
>>> it's functional :)
>>>
>>> Laurent
>>>
>>> On Oct 1, 2009, at 11:39 PM, Dylan Bruzenak wrote:
>>>
>>>  I'm a bit of a newbie when it comes to command line compilation.
>>>>
>>>> Is there an easy way for me to basically just say: compile everything
>>>> recursively, starting at this directory ? Given that, what would be the best
>>>> way to then integrate that with an Xcode project as part of a target ?
>>>>
>>>> Also, is this far enough along to consider adding to the project
>>>> templates by default ?
>>>>
>>>> thanks!
>>>>
>>>> - Dylan
>>>>
>>>>
>>>> _______________________________________________
>>>> MacRuby-devel mailing list
>>>> MacRuby-devel at lists.macosforge.org
>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>>
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/94723a85/attachment.html>

From eloy.de.enige at gmail.com  Fri Oct  2 12:01:24 2009
From: eloy.de.enige at gmail.com (Eloy Duran)
Date: Fri, 2 Oct 2009 21:01:24 +0200
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <aea090980910021044gab6d818o64f87044c30f4265@mail.gmail.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<D739ECF9-5C14-4979-A16E-545B86C3C769@gmail.com>
	<20fefa50910020124i3ee6325cva5380dc9b8dbe990@mail.gmail.com>
	<3AE6C2C5-A9CC-4D5C-81E5-AAFABF90B1BC@gmail.com>
	<aea090980910021044gab6d818o64f87044c30f4265@mail.gmail.com>
Message-ID: <F05F5378-C28A-4C91-BEE6-4F5F8CB648C1@gmail.com>

EPIC STORY ALERT:

> First, I completely agree on reducing duplicated effort, but I have  
> a few questions.

Sure thing, that's what we're here for :)

> Let me know if you want to move this discussion off list or feel  
> free to just answer these off list.

For details, I think it's best to discuss on IRC freenode #ruby-osx,  
or via IM. My email address is where you can reach me on gtalk/jabber.

> What is the timeline for merging rucola into HotCocoa vs extending  
> HotCocoa to have the functionality that is present in RubyCocoa  
> rucola ?

There wouldn't be much difference in total  development time, so we've  
discussed that for the time being they're gonna be developed  
separately. Because much has to be done on both the libraries core  
code, so it's not an ideal moment to devote time to merging them.

> What are the major blockers/good places to start looking to help out  
> the MacRubyification of the rucola framework ?

Discovering all bugs to be able to run Mocha and ERB (dunno the status  
of the latter).

> Is rucola a command line only generation framework, or will there be  
> support for creating projects in Xcode as well ? My current focus as  
> a new user is helping to smooth the transition for other new users  
> from Obj-c to Ruby development. Being able to stay in Xcode  and use  
> standard templates and IB for initial development really helps ease  
> the transition. Command line generation is fantastic from the  
> 'coming from Rails' perspective, but not so great for the coming  
> from Xcode perspective, where you expect this to be handled by  
> targets and build steps.

It already was possible to do most stuff from XCode. But, admittedly,  
not being a huge user of XCode has lead me to never create xcode  
templates. I would love input on this from users such as yourself,  
because it _should_ be completely transparent.

Also, I would like to clarify that I did _not_ mean that HotCocoa/ 
Rucola would be a standard dependency of an application. I simply  
meant that the test cases, which are run by devs anyways so not a  
problem afaik, would require the test case helpers form the HotCocoa/ 
Rucola gem. The gem will come with MacRuby pre-installed. (At least,  
that's what I remember the last discussion on this topic being  
concluded at.)

So with your additions to the templates, this would still run that  
way, we simply don't include any elaborate helper code. To summarize,  
a standard template created app, would look identically to what your  
additions do, with the exception from any test case helpers, these  
should go into a shared test case helper.

> From the testing perspective: I've only tried naive tests with the  
> standard test::unit style so far but everything seems to be working.  
> What are the missing/broken parts that I haven't run into yet ?

Too much to list actually, but it surrounds meta code mainly, which is  
probably why most simplere uses work. (Try running the test suites of  
test::unit and minitest, see the rake tasks). More importantly, as  
you've noted, test::unit is dropped by upstream in favor of minitest.  
We however still have it in the stdlib and it's unsure as of yet what  
and when this is going to change, so this could potentially make it  
"hard" for users. Although I must admit, I have no experience in  
porting test cases to minitest.

> I understand re: including testing appearing to be supporting it.  
> Could that be reduced by adding comments to the effect that some  
> things may not work to the template or better documentation on what  
> is supported ?

A comment, as a note that it's not stable yet, would already clarify a  
lot yes.

> My main concern here is that people like me who would want to try  
> out MacRuby may have to replicate the admittedly limited integration  
> work and snooping that I've done here (since it is not obvious that  
> it isn't supported, so of course you go to try it out), replicating  
> the effort and running into a disheartening wall anyway.

True, we don't want that.

> Or worse, they could choose not to go beyond initial experiments  
> with MacRuby due to the lack of apparent support for testing. So  
> either way, the current state of testing should probably be  
> addressed somewhere with a call to arms :)

Well, it _is_ being worked on. The reason that might not be apparent,  
is simply because it really _isn't_ stable yet and I always tend to  
wait giving the idea something is "supported" (ugh I hate the  
word ;) ) until we have something to show for it.

In other words, in my opinion, people should not expect everything to  
work yet on MacRuby. If they know this upfront, then there's also no  
reason to judge MacRuby on it and stop using MacRuby. Which is why I'm  
telling all of this in the first place :)

So, since I do wholeheartedly agree with you that we don't want users  
to bump into any walls, I'm gonna apply your patch right now, and we  
will discuss further on the test case helpers as we go :)

HTH.

Cheers,
Eloy

PS: Dylan, please do contact me off list to discuss details,  
preferably not by email, it takes me too much time to write them?

>
> - Dylan
>
> On Fri, Oct 2, 2009 at 3:31 AM, Eloy Duran <eloy.de.enige at gmail.com>  
> wrote:
> Hey Matt,
>
>> hmm for once I don't fully agree with Eloy :)
>
> I'm sure we've disagreed before ;-)
>
>> But, on the long run this should all move to Rucola to provide one  
>> piece that pulls it all together.
>>
>> It's a small details but I think we do need a solid testing  
>> framework in XCode too. Not everyone will use Rucola and therefore  
>> offering a great test solution for both tools would be great.
>
> Rucola has always been about allowing Ruby devs _and_ xcode users to  
> use it without knowing the difference. Also, Rucola/HotCocoa will  
> come with MacRuby, so they can use it without knowing so.
>
>> I don't think Eloy was against such thing but I thought it was  
>> important to mention it.
>
> I'm against maintaining duplicate stuff. People should just use the  
> code which has been battle tested and has added facilities to make  
> it easier, even if they don't know what it is their using in the  
> bakcground. Ie, the test helper would just require the test case  
> helper, the user doesn't need to know where it actually lives.  
> Adding this to the project template makes people think they have to  
> add facilities themselves imo.
>
> Eloy
>
>> On Fri, Oct 2, 2009 at 1:18 AM, Eloy Duran  
>> <eloy.de.enige at gmail.com> wrote:
>> Hi Dylan,
>>
>>
>> So, I've been mucking about with MacRuby lately. It's been fun so  
>> far. Thanks to all the devs for this great project.
>>
>> Welcome!
>>
>>
>> I'm a pretty firm believer in unit testing my Ruby code. I love how  
>> Ruby on Rails and similar frameworks nudge you in the right  
>> direction by baking in an existing testing infrastructure.
>>
>> Great, we agree! :)
>>
>>
>> I've got testing pretty much figured out and was wondering if the  
>> team would be open to modifying the basic Xcode project template to  
>> add unit testing, with a stub test and test_suite file to get  
>> started. This would also involve creating a framework for any  
>> objective-c code that the user writes so that it can be included in  
>> both the .app and the test files.
>>
>> Well, unfortunately atm it's not that easy. Because we currently  
>> can't both run test::unit or minitest properly. I know the  
>> test::unit, which is currently in macruby's trunk, works work the  
>> greater part, but it's not ideal.
>>
>> I have been working on this area for a while now, getting a little  
>> closer every time. This work is part of Rucola, which at some point  
>> will merge with HotCocoa and will provide a classic layout as you  
>> are accustomed to by frameworks such as Rails.
>>
>> At this point, the test framework which we can fully run is Bacon,  
>> which is what I'm gonna base the rest of my current work on.  
>> However, once we can fully run minitest/test::unit we'll support  
>> that as well. More importantly right now is a working mocking and  
>> stubbing lib. My choice is Mocha, but MacRuby is not mature enough  
>> yet to do all the fancy meta stuff that is needed for this.
>>
>> So for the time being, I'd say cool let's add it to the project  
>> template! But, on the long run this should all move to Rucola to  
>> provide one piece that pulls it all together. If you are interested  
>> on working on this, please contact me directly. Anyone can do that  
>> btw.
>>
>> Cheers,
>> Eloy
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/b6a994dc/attachment-0001.html>

From eloy.de.enige at gmail.com  Fri Oct  2 12:05:08 2009
From: eloy.de.enige at gmail.com (Eloy Duran)
Date: Fri, 2 Oct 2009 21:05:08 +0200
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <aea090980910021130p5637140fjd254f5a721f515c0@mail.gmail.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<D739ECF9-5C14-4979-A16E-545B86C3C769@gmail.com>
	<20fefa50910020124i3ee6325cva5380dc9b8dbe990@mail.gmail.com>
	<3AE6C2C5-A9CC-4D5C-81E5-AAFABF90B1BC@gmail.com>
	<aea090980910021044gab6d818o64f87044c30f4265@mail.gmail.com>
	<20fefa50910021059x31240abfqd5fd605b5aa2ec91@mail.gmail.com>
	<aea090980910021130p5637140fjd254f5a721f515c0@mail.gmail.com>
Message-ID: <E799D7A3-5B78-463D-B881-28D559639783@gmail.com>

> I'm trying not to jump to conclusions, just feeling out the space  
> and trying to open up the discussion a bit. Not having as clear of a  
> perspective as you guys, obviously, I'm just stating a few rogue  
> opinions and trying to come up to speed, letting you know my current  
> thoughts. I'm not married to many of them.
>
> Text can be brutal as you don't get the intonation. Please read the  
> above with a friendly/questioning tone rather than a confrontational  
> one.

> At the end of the day it isn't my project so I'm not about to start  
> pushing my ideas; that said I'm really excited about it and have a  
> bajillion questions, concerns, and little bumps I hit that I want to  
> smooth out as much as is feasible. Obviously I won't understand all  
> the barriers yet as I'm learning and I appreciate the 'well, duh'  
> hand holding in the meantime.

FWIW I agree completely with you, the same applies to my emails :).

No different tone came across to me (and I assume others) then good  
stuff. Keep it up!

Eloy


From lsansonetti at apple.com  Fri Oct  2 12:06:15 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Fri, 02 Oct 2009 12:06:15 -0700
Subject: [MacRuby-devel] How to compile all ruby files in a
 project	using macrubyc
In-Reply-To: <aea090980910021151r17029c66m7d5c6d8c6242b59b@mail.gmail.com>
References: <aea090980910012339k6d08a22agee1a8bcbebc88c36@mail.gmail.com>
	<22A9350F-694E-4AE2-A6A3-E58B6CDC60A7@apple.com>
	<951638E8-E69C-42C5-9CD1-125F763E0143@ideaswarm.com>
	<6E4F1C8C-8984-483F-9544-656DA687B963@apple.com>
	<aea090980910021151r17029c66m7d5c6d8c6242b59b@mail.gmail.com>
Message-ID: <9BC99B58-0815-4038-8158-C25DFC912619@apple.com>

Hi Dylan,

You can still start your project today and use the JIT during  
development, then once the template is in place, you can activate it.  
If you need to ship your product before the template is available we  
can help you compiling your app (but it will require some command-line  
magic) :)

Laurent

On Oct 2, 2009, at 11:51 AM, Dylan Bruzenak wrote:

> Thanks!
>
> Mostly I'm looking at doing some real commercial development here  
> and it helps to know the timeline and how you feel about the  
> stability. Certainly beats the daylights out of bracket soup. But in  
> order to do that I basically need to keep my code from being  
> editable and readable by anyone who chooses 'show package contents' :)
>
> - Dylan
>
> On Fri, Oct 2, 2009 at 1:49 PM, Laurent Sansonetti <lsansonetti at apple.com 
> > wrote:
> 0.5 is scheduled for the end of the year, with a set of beta  
> releases before. We didn't set a date in stone yet because we want  
> to ship it when it's really ready :)
>
> Laurent
>
>
> On Oct 2, 2009, at 12:02 AM, Dylan wrote:
>
> Good to know :)
>
> Hate to ask since I can never answer this question myself: do you  
> have a loose timeline for the release ?
>
> -Dylan
>
> On Oct 2, 2009, at 1:54 AM, Laurent Sansonetti  
> <lsansonetti at apple.com> wrote:
>
> Hi Dylan,
>
> The AOT compilation of an Xcode project is still not finalized. It's  
> technically possible to do it with the current macrubyc on the  
> command line but it's kind of hard and we still have problems with  
> #require statements. We will introduce an Xcode target that does it  
> automatically for the 0.5 release.
>
> I guess the target could indeed by added by default to the templates  
> once it's functional :)
>
> Laurent
>
> On Oct 1, 2009, at 11:39 PM, Dylan Bruzenak wrote:
>
> I'm a bit of a newbie when it comes to command line compilation.
>
> Is there an easy way for me to basically just say: compile  
> everything recursively, starting at this directory ? Given that,  
> what would be the best way to then integrate that with an Xcode  
> project as part of a target ?
>
> Also, is this far enough along to consider adding to the project  
> templates by default ?
>
> thanks!
>
> - Dylan
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From dylan at ideaswarm.com  Fri Oct  2 12:09:00 2009
From: dylan at ideaswarm.com (Dylan Bruzenak)
Date: Fri, 2 Oct 2009 14:09:00 -0500
Subject: [MacRuby-devel] How to compile all ruby files in a project
	using macrubyc
In-Reply-To: <9BC99B58-0815-4038-8158-C25DFC912619@apple.com>
References: <aea090980910012339k6d08a22agee1a8bcbebc88c36@mail.gmail.com>
	<22A9350F-694E-4AE2-A6A3-E58B6CDC60A7@apple.com>
	<951638E8-E69C-42C5-9CD1-125F763E0143@ideaswarm.com>
	<6E4F1C8C-8984-483F-9544-656DA687B963@apple.com>
	<aea090980910021151r17029c66m7d5c6d8c6242b59b@mail.gmail.com>
	<9BC99B58-0815-4038-8158-C25DFC912619@apple.com>
Message-ID: <aea090980910021209o7151cb99ybc558a636387b9f4@mail.gmail.com>

I'll buy maracas and some voodoo/pixie dust then :)
- Dylan

On Fri, Oct 2, 2009 at 2:06 PM, Laurent Sansonetti <lsansonetti at apple.com>wrote:

> Hi Dylan,
>
> You can still start your project today and use the JIT during development,
> then once the template is in place, you can activate it. If you need to ship
> your product before the template is available we can help you compiling your
> app (but it will require some command-line magic) :)
>
> Laurent
>
>
> On Oct 2, 2009, at 11:51 AM, Dylan Bruzenak wrote:
>
>  Thanks!
>>
>> Mostly I'm looking at doing some real commercial development here and it
>> helps to know the timeline and how you feel about the stability. Certainly
>> beats the daylights out of bracket soup. But in order to do that I basically
>> need to keep my code from being editable and readable by anyone who chooses
>> 'show package contents' :)
>>
>> - Dylan
>>
>> On Fri, Oct 2, 2009 at 1:49 PM, Laurent Sansonetti <lsansonetti at apple.com>
>> wrote:
>> 0.5 is scheduled for the end of the year, with a set of beta releases
>> before. We didn't set a date in stone yet because we want to ship it when
>> it's really ready :)
>>
>> Laurent
>>
>>
>> On Oct 2, 2009, at 12:02 AM, Dylan wrote:
>>
>> Good to know :)
>>
>> Hate to ask since I can never answer this question myself: do you have a
>> loose timeline for the release ?
>>
>> -Dylan
>>
>> On Oct 2, 2009, at 1:54 AM, Laurent Sansonetti <lsansonetti at apple.com>
>> wrote:
>>
>> Hi Dylan,
>>
>> The AOT compilation of an Xcode project is still not finalized. It's
>> technically possible to do it with the current macrubyc on the command line
>> but it's kind of hard and we still have problems with #require statements.
>> We will introduce an Xcode target that does it automatically for the 0.5
>> release.
>>
>> I guess the target could indeed by added by default to the templates once
>> it's functional :)
>>
>> Laurent
>>
>> On Oct 1, 2009, at 11:39 PM, Dylan Bruzenak wrote:
>>
>> I'm a bit of a newbie when it comes to command line compilation.
>>
>> Is there an easy way for me to basically just say: compile everything
>> recursively, starting at this directory ? Given that, what would be the best
>> way to then integrate that with an Xcode project as part of a target ?
>>
>> Also, is this far enough along to consider adding to the project templates
>> by default ?
>>
>> thanks!
>>
>> - Dylan
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/042ec24f/attachment.html>

From eloy.de.enige at gmail.com  Fri Oct  2 12:11:06 2009
From: eloy.de.enige at gmail.com (Eloy Duran)
Date: Fri, 2 Oct 2009 21:11:06 +0200
Subject: [MacRuby-devel] Supported classes & methods diagram fed from
	rubyspec
In-Reply-To: <E24BEB42-0CC6-48D1-B897-F2FF8A45CFD5@apple.com>
References: <E148045D-99B5-4CB6-9542-2973197873A4@gmail.com>
	<9939E537-6087-41E2-8EBD-A818C1C5B06F@apple.com>
	<D0AA1C17-5F29-42FB-A5B1-BD5611EF37FE@gmail.com>
	<E24BEB42-0CC6-48D1-B897-F2FF8A45CFD5@apple.com>
Message-ID: <07A34B0C-48FC-4705-9133-E7898818F213@gmail.com>

That looks great indeed Ben, much better than what my investigation in  
exiting solutions resulted in :)

It would be great if we'd have a osx machine that would automatically  
run the suite at night and generate this from it. Any idea if that  
would become a possibility in the near future Laurent?

Eloy

On 2 okt 2009, at 20:48, Laurent Sansonetti wrote:

> Hi Ben,
>
> I wasn't aware of that project, it looks good indeed. And the fact  
> that it can be reused for different implementations of Ruby is very  
> cool too :)
>
> Laurent
>
> On Oct 1, 2009, at 11:48 PM, Ben Schwarz wrote:
>
>> Laurent,
>>
>> I just had a quick chat with Brian Ford (Rubinius) apparently  
>> they're looking at using some incarnation of git://github.com/madriska/unity.git 
>>  (http://unity.madriska.com/)
>> Which uses a YAML formatter for mspec. (http://github.com/madriska/mspec/commit/36b8bce62c272d546bcbd8ab9f136576ff4701e5 
>> )
>>
>> I think this might be the best way to get something that works  
>> running. I'm sure that all the ruby implementations would benefit  
>> from the shared work effort in this regard.
>> We could start by investigating unity, chatting to the author and  
>> seeing if we can make some contributions.
>>
>>
>>
>>
>> On 02/10/2009, at 4:23 PM, Laurent Sansonetti wrote:
>>
>>> Hi Ben,
>>>
>>> That sounds like a good idea and looks like what I had in mind.
>>>
>>> I was thinking of having a status page, that shows hitlist items  
>>> (critical bugs / things to do for the upcoming release), some  
>>> rubyspec progress, a link to the latest nighty build, etc.
>>>
>>> The hitlist thing could be generated from a local file from the  
>>> repository. We currently use TODO for that.
>>>
>>> We wrote a special mspec formatter in order to know what  
>>> percentage of a given spec category we do pass. But having a more  
>>> detailed view (classes / methods as you suggested) might be more  
>>> interesting, this way we know on what class / method to focus in  
>>> priority. Assuming that the mspec formatter is altered a little  
>>> bit, this information could also be generated after a spec:ci pass.
>>>
>>> Is that what you had in mind?
>>>
>>> I guess the challenge here is to write a program that generates a  
>>> Webby page for our website, commit it to the repository every time  
>>> a change is made, then we would re-deploy the site right after.
>>>
>>> Laurent
>>>
>>> On Oct 1, 2009, at 11:01 PM, Ben Schwarz wrote:
>>>
>>>> Hi all,
>>>>
>>>>
>>>> I've had some loose discussions with @lrz regarding a visual  
>>>> representation of classes and methods that are working via the  
>>>> rubyspec.
>>>> This would enable developers to find an area of development to  
>>>> focus on and also for end-users to understand what they might  
>>>> face before
>>>> conducting any development using macruby (bringing real  
>>>> applications closer to tuition, rather than a start/stop  
>>>> experience)
>>>>
>>>> I'm happy to offer some hours to get something together that is  
>>>> styled like macruby.org but I obviously need to:
>>>>
>>>> 	A) consult the group
>>>> 	B) work out a spec
>>>> 	C) have something setup on the macruby.org infrastructure.
>>>>
>>>>
>>>> Discuss.
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> -
>>>>
>>>> Ben Schwarz
>>>> Web architect
>>>>
>>>> Web:		http://www.germanforblack.com
>>>> Mobile: 		+61 407 339 418
>>>>
>>>> -- 
>>>> Please consider your environment before printing or distributing  
>>>> this material.
>>>> --
>>>>
>>>> _______________________________________________
>>>> MacRuby-devel mailing list
>>>> MacRuby-devel at lists.macosforge.org
>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From mattaimonetti at gmail.com  Fri Oct  2 12:16:53 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Fri, 2 Oct 2009 12:16:53 -0700
Subject: [MacRuby-devel] Supported classes & methods diagram fed from
	rubyspec
In-Reply-To: <07A34B0C-48FC-4705-9133-E7898818F213@gmail.com>
References: <E148045D-99B5-4CB6-9542-2973197873A4@gmail.com>
	<9939E537-6087-41E2-8EBD-A818C1C5B06F@apple.com>
	<D0AA1C17-5F29-42FB-A5B1-BD5611EF37FE@gmail.com>
	<E24BEB42-0CC6-48D1-B897-F2FF8A45CFD5@apple.com>
	<07A34B0C-48FC-4705-9133-E7898818F213@gmail.com>
Message-ID: <20fefa50910021216y2b2cd6ebn222c57b21097fa01@mail.gmail.com>

Actually.... Claudio is doing that already ;) He might as well add one more
step to his nightly building app.

- Matt

On Fri, Oct 2, 2009 at 12:11 PM, Eloy Duran <eloy.de.enige at gmail.com> wrote:

> That looks great indeed Ben, much better than what my investigation in
> exiting solutions resulted in :)
>
> It would be great if we'd have a osx machine that would automatically run
> the suite at night and generate this from it. Any idea if that would become
> a possibility in the near future Laurent?
>
> Eloy
>
>
> On 2 okt 2009, at 20:48, Laurent Sansonetti wrote:
>
>  Hi Ben,
>>
>> I wasn't aware of that project, it looks good indeed. And the fact that it
>> can be reused for different implementations of Ruby is very cool too :)
>>
>> Laurent
>>
>> On Oct 1, 2009, at 11:48 PM, Ben Schwarz wrote:
>>
>>  Laurent,
>>>
>>> I just had a quick chat with Brian Ford (Rubinius) apparently they're
>>> looking at using some incarnation of git://github.com/madriska/unity.git
>>>  (http://unity.madriska.com/)
>>> Which uses a YAML formatter for mspec. (
>>> http://github.com/madriska/mspec/commit/36b8bce62c272d546bcbd8ab9f136576ff4701e5
>>> )
>>>
>>> I think this might be the best way to get something that works running.
>>> I'm sure that all the ruby implementations would benefit from the shared
>>> work effort in this regard.
>>> We could start by investigating unity, chatting to the author and seeing
>>> if we can make some contributions.
>>>
>>>
>>>
>>>
>>> On 02/10/2009, at 4:23 PM, Laurent Sansonetti wrote:
>>>
>>>  Hi Ben,
>>>>
>>>> That sounds like a good idea and looks like what I had in mind.
>>>>
>>>> I was thinking of having a status page, that shows hitlist items
>>>> (critical bugs / things to do for the upcoming release), some rubyspec
>>>> progress, a link to the latest nighty build, etc.
>>>>
>>>> The hitlist thing could be generated from a local file from the
>>>> repository. We currently use TODO for that.
>>>>
>>>> We wrote a special mspec formatter in order to know what percentage of a
>>>> given spec category we do pass. But having a more detailed view (classes /
>>>> methods as you suggested) might be more interesting, this way we know on
>>>> what class / method to focus in priority. Assuming that the mspec formatter
>>>> is altered a little bit, this information could also be generated after a
>>>> spec:ci pass.
>>>>
>>>> Is that what you had in mind?
>>>>
>>>> I guess the challenge here is to write a program that generates a Webby
>>>> page for our website, commit it to the repository every time a change is
>>>> made, then we would re-deploy the site right after.
>>>>
>>>> Laurent
>>>>
>>>> On Oct 1, 2009, at 11:01 PM, Ben Schwarz wrote:
>>>>
>>>>  Hi all,
>>>>>
>>>>>
>>>>> I've had some loose discussions with @lrz regarding a visual
>>>>> representation of classes and methods that are working via the rubyspec.
>>>>> This would enable developers to find an area of development to focus on
>>>>> and also for end-users to understand what they might face before
>>>>> conducting any development using macruby (bringing real applications
>>>>> closer to tuition, rather than a start/stop experience)
>>>>>
>>>>> I'm happy to offer some hours to get something together that is styled
>>>>> like macruby.org but I obviously need to:
>>>>>
>>>>>        A) consult the group
>>>>>        B) work out a spec
>>>>>        C) have something setup on the macruby.org infrastructure.
>>>>>
>>>>>
>>>>> Discuss.
>>>>>
>>>>>
>>>>> Cheers,
>>>>>
>>>>> -
>>>>>
>>>>> Ben Schwarz
>>>>> Web architect
>>>>>
>>>>> Web:            http://www.germanforblack.com
>>>>> Mobile:                 +61 407 339 418
>>>>>
>>>>> --
>>>>> Please consider your environment before printing or distributing this
>>>>> material.
>>>>> --
>>>>>
>>>>> _______________________________________________
>>>>> MacRuby-devel mailing list
>>>>> MacRuby-devel at lists.macosforge.org
>>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>>>
>>>>
>>>> _______________________________________________
>>>> MacRuby-devel mailing list
>>>> MacRuby-devel at lists.macosforge.org
>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>>
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/b2727772/attachment-0001.html>

From eloy.de.enige at gmail.com  Fri Oct  2 12:19:14 2009
From: eloy.de.enige at gmail.com (Eloy Duran)
Date: Fri, 2 Oct 2009 21:19:14 +0200
Subject: [MacRuby-devel] Supported classes & methods diagram fed from
	rubyspec
In-Reply-To: <20fefa50910021216y2b2cd6ebn222c57b21097fa01@mail.gmail.com>
References: <E148045D-99B5-4CB6-9542-2973197873A4@gmail.com>
	<9939E537-6087-41E2-8EBD-A818C1C5B06F@apple.com>
	<D0AA1C17-5F29-42FB-A5B1-BD5611EF37FE@gmail.com>
	<E24BEB42-0CC6-48D1-B897-F2FF8A45CFD5@apple.com>
	<07A34B0C-48FC-4705-9133-E7898818F213@gmail.com>
	<20fefa50910021216y2b2cd6ebn222c57b21097fa01@mail.gmail.com>
Message-ID: <2A915063-5955-46F6-BA62-A8241DC9182D@gmail.com>

Oh serious?! I didn't know, awesome! Thanks Claudio, your my hero of  
the day!
Sorry Laurent, there will be plenty of other days left for you to  
shine again ;-)

Eloy

On 2 okt 2009, at 21:16, Matt Aimonetti wrote:

> Actually.... Claudio is doing that already ;) He might as well add  
> one more step to his nightly building app.
>
> - Matt
>
> On Fri, Oct 2, 2009 at 12:11 PM, Eloy Duran  
> <eloy.de.enige at gmail.com> wrote:
> That looks great indeed Ben, much better than what my investigation  
> in exiting solutions resulted in :)
>
> It would be great if we'd have a osx machine that would  
> automatically run the suite at night and generate this from it. Any  
> idea if that would become a possibility in the near future Laurent?
>
> Eloy
>
>
> On 2 okt 2009, at 20:48, Laurent Sansonetti wrote:
>
> Hi Ben,
>
> I wasn't aware of that project, it looks good indeed. And the fact  
> that it can be reused for different implementations of Ruby is very  
> cool too :)
>
> Laurent
>
> On Oct 1, 2009, at 11:48 PM, Ben Schwarz wrote:
>
> Laurent,
>
> I just had a quick chat with Brian Ford (Rubinius) apparently  
> they're looking at using some incarnation of git://github.com/madriska/unity.git 
>  (http://unity.madriska.com/)
> Which uses a YAML formatter for mspec. (http://github.com/madriska/mspec/commit/36b8bce62c272d546bcbd8ab9f136576ff4701e5 
> )
>
> I think this might be the best way to get something that works  
> running. I'm sure that all the ruby implementations would benefit  
> from the shared work effort in this regard.
> We could start by investigating unity, chatting to the author and  
> seeing if we can make some contributions.
>
>
>
>
> On 02/10/2009, at 4:23 PM, Laurent Sansonetti wrote:
>
> Hi Ben,
>
> That sounds like a good idea and looks like what I had in mind.
>
> I was thinking of having a status page, that shows hitlist items  
> (critical bugs / things to do for the upcoming release), some  
> rubyspec progress, a link to the latest nighty build, etc.
>
> The hitlist thing could be generated from a local file from the  
> repository. We currently use TODO for that.
>
> We wrote a special mspec formatter in order to know what percentage  
> of a given spec category we do pass. But having a more detailed view  
> (classes / methods as you suggested) might be more interesting, this  
> way we know on what class / method to focus in priority. Assuming  
> that the mspec formatter is altered a little bit, this information  
> could also be generated after a spec:ci pass.
>
> Is that what you had in mind?
>
> I guess the challenge here is to write a program that generates a  
> Webby page for our website, commit it to the repository every time a  
> change is made, then we would re-deploy the site right after.
>
> Laurent
>
> On Oct 1, 2009, at 11:01 PM, Ben Schwarz wrote:
>
> Hi all,
>
>
> I've had some loose discussions with @lrz regarding a visual  
> representation of classes and methods that are working via the  
> rubyspec.
> This would enable developers to find an area of development to focus  
> on and also for end-users to understand what they might face before
> conducting any development using macruby (bringing real applications  
> closer to tuition, rather than a start/stop experience)
>
> I'm happy to offer some hours to get something together that is  
> styled like macruby.org but I obviously need to:
>
>        A) consult the group
>        B) work out a spec
>        C) have something setup on the macruby.org infrastructure.
>
>
> Discuss.
>
>
> Cheers,
>
> -
>
> Ben Schwarz
> Web architect
>
> Web:            http://www.germanforblack.com
> Mobile:                 +61 407 339 418
>
> -- 
> Please consider your environment before printing or distributing  
> this material.
> --
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/03bb0cec/attachment.html>

From eloy.de.enige at gmail.com  Fri Oct  2 12:28:55 2009
From: eloy.de.enige at gmail.com (Eloy Duran)
Date: Fri, 2 Oct 2009 21:28:55 +0200
Subject: [MacRuby-devel] Xcode Project Template with Testing Baked In
In-Reply-To: <F05F5378-C28A-4C91-BEE6-4F5F8CB648C1@gmail.com>
References: <aea090980910011626h75e35cf8l8998f9090a56e95@mail.gmail.com>
	<D739ECF9-5C14-4979-A16E-545B86C3C769@gmail.com>
	<20fefa50910020124i3ee6325cva5380dc9b8dbe990@mail.gmail.com>
	<3AE6C2C5-A9CC-4D5C-81E5-AAFABF90B1BC@gmail.com>
	<aea090980910021044gab6d818o64f87044c30f4265@mail.gmail.com>
	<F05F5378-C28A-4C91-BEE6-4F5F8CB648C1@gmail.com>
Message-ID: <2D891F46-2290-43A8-86B9-F3C0B61DB8B1@gmail.com>

> So, since I do wholeheartedly agree with you that we don't want  
> users to bump into any walls, I'm gonna apply your patch right now,  
> and we will discuss further on the test case helpers as we go :)

Where "now" is right after I get some food ;)

Eloy

From ruby-noreply at macosforge.org  Fri Oct  2 13:24:16 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 02 Oct 2009 20:24:16 -0000
Subject: [MacRuby-devel] [MacRuby] #362: Add Unit Testing and Embed
 MacRuby to Project Template
In-Reply-To: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
References: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
Message-ID: <059.34073eacc2b9b15f61d996afffff8ce0@macosforge.org>

#362: Add Unit Testing and Embed MacRuby to Project Template
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |       Owner:  eloy.de.enige@?        
     Type:  enhancement          |      Status:  new                    
 Priority:  trivial              |   Milestone:                         
Component:  MacRuby              |    Keywords:                         
---------------------------------+------------------------------------------

Comment(by eloy.de.enige@?):

 So, I was gonna apply it as Laurent already tried it and said it worked
 great, but I'd first like to run some stuff by you:

 How about changing the test_suite.rb file to run_suite.rb, move it into
 the Tests dir and use glob like:

 {{{
 Dir.glob(File.expand_path('../**/*_test.rb', __FILE__)).each { |test|
 require test }
 }}}

 And rename the test_stub.rb to stub_test.rb.

 So invoking the complete suite would be: $ ruby Tests/run_suite.rb

 Thoughts?

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/362#comment:6>
MacRuby <http://macruby.org/>


From mattaimonetti at gmail.com  Fri Oct  2 14:00:08 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Fri, 2 Oct 2009 14:00:08 -0700
Subject: [MacRuby-devel] Supported classes & methods diagram fed from
	rubyspec
In-Reply-To: <2A915063-5955-46F6-BA62-A8241DC9182D@gmail.com>
References: <E148045D-99B5-4CB6-9542-2973197873A4@gmail.com>
	<9939E537-6087-41E2-8EBD-A818C1C5B06F@apple.com>
	<D0AA1C17-5F29-42FB-A5B1-BD5611EF37FE@gmail.com>
	<E24BEB42-0CC6-48D1-B897-F2FF8A45CFD5@apple.com>
	<07A34B0C-48FC-4705-9133-E7898818F213@gmail.com>
	<20fefa50910021216y2b2cd6ebn222c57b21097fa01@mail.gmail.com>
	<2A915063-5955-46F6-BA62-A8241DC9182D@gmail.com>
Message-ID: <20fefa50910021400r2872a303k42865e3ff2d9c27a@mail.gmail.com>

Wait, I said he "could" do it, or someone could fork the sinatra app and add
it, it's not done yet tho :)
Btw, thanks a lot Claudio for making a server available!

- Matt


On Fri, Oct 2, 2009 at 12:19 PM, Eloy Duran <eloy.de.enige at gmail.com> wrote:

> Oh serious?! I didn't know, awesome! Thanks Claudio, your my hero of the
> day!Sorry Laurent, there will be plenty of other days left for you to
> shine again ;-)
>
> Eloy
>
> On 2 okt 2009, at 21:16, Matt Aimonetti wrote:
>
> Actually.... Claudio is doing that already ;) He might as well add one more
> step to his nightly building app.
>
> - Matt
>
> On Fri, Oct 2, 2009 at 12:11 PM, Eloy Duran <eloy.de.enige at gmail.com>wrote:
>
>> That looks great indeed Ben, much better than what my investigation in
>> exiting solutions resulted in :)
>>
>> It would be great if we'd have a osx machine that would automatically run
>> the suite at night and generate this from it. Any idea if that would become
>> a possibility in the near future Laurent?
>>
>> Eloy
>>
>>
>> On 2 okt 2009, at 20:48, Laurent Sansonetti wrote:
>>
>>  Hi Ben,
>>>
>>> I wasn't aware of that project, it looks good indeed. And the fact that
>>> it can be reused for different implementations of Ruby is very cool too :)
>>>
>>> Laurent
>>>
>>> On Oct 1, 2009, at 11:48 PM, Ben Schwarz wrote:
>>>
>>>  Laurent,
>>>>
>>>> I just had a quick chat with Brian Ford (Rubinius) apparently they're
>>>> looking at using some incarnation of git://
>>>> github.com/madriska/unity.git (http://unity.madriska.com/)
>>>> Which uses a YAML formatter for mspec. (
>>>> http://github.com/madriska/mspec/commit/36b8bce62c272d546bcbd8ab9f136576ff4701e5
>>>> )
>>>>
>>>> I think this might be the best way to get something that works running.
>>>> I'm sure that all the ruby implementations would benefit from the shared
>>>> work effort in this regard.
>>>> We could start by investigating unity, chatting to the author and seeing
>>>> if we can make some contributions.
>>>>
>>>>
>>>>
>>>>
>>>> On 02/10/2009, at 4:23 PM, Laurent Sansonetti wrote:
>>>>
>>>>  Hi Ben,
>>>>>
>>>>> That sounds like a good idea and looks like what I had in mind.
>>>>>
>>>>> I was thinking of having a status page, that shows hitlist items
>>>>> (critical bugs / things to do for the upcoming release), some rubyspec
>>>>> progress, a link to the latest nighty build, etc.
>>>>>
>>>>> The hitlist thing could be generated from a local file from the
>>>>> repository. We currently use TODO for that.
>>>>>
>>>>> We wrote a special mspec formatter in order to know what percentage of
>>>>> a given spec category we do pass. But having a more detailed view (classes /
>>>>> methods as you suggested) might be more interesting, this way we know on
>>>>> what class / method to focus in priority. Assuming that the mspec formatter
>>>>> is altered a little bit, this information could also be generated after a
>>>>> spec:ci pass.
>>>>>
>>>>> Is that what you had in mind?
>>>>>
>>>>> I guess the challenge here is to write a program that generates a Webby
>>>>> page for our website, commit it to the repository every time a change is
>>>>> made, then we would re-deploy the site right after.
>>>>>
>>>>> Laurent
>>>>>
>>>>> On Oct 1, 2009, at 11:01 PM, Ben Schwarz wrote:
>>>>>
>>>>>  Hi all,
>>>>>>
>>>>>>
>>>>>> I've had some loose discussions with @lrz regarding a visual
>>>>>> representation of classes and methods that are working via the rubyspec.
>>>>>> This would enable developers to find an area of development to focus
>>>>>> on and also for end-users to understand what they might face before
>>>>>> conducting any development using macruby (bringing real applications
>>>>>> closer to tuition, rather than a start/stop experience)
>>>>>>
>>>>>> I'm happy to offer some hours to get something together that is styled
>>>>>> like macruby.org but I obviously need to:
>>>>>>
>>>>>>        A) consult the group
>>>>>>        B) work out a spec
>>>>>>        C) have something setup on the macruby.org infrastructure.
>>>>>>
>>>>>>
>>>>>> Discuss.
>>>>>>
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> -
>>>>>>
>>>>>> Ben Schwarz
>>>>>> Web architect
>>>>>>
>>>>>> Web:            http://www.germanforblack.com
>>>>>> Mobile:                 +61 407 339 418
>>>>>>
>>>>>> --
>>>>>> Please consider your environment before printing or distributing this
>>>>>> material.
>>>>>> --
>>>>>>
>>>>>> _______________________________________________
>>>>>> MacRuby-devel mailing list
>>>>>> MacRuby-devel at lists.macosforge.org
>>>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> MacRuby-devel mailing list
>>>>> MacRuby-devel at lists.macosforge.org
>>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>>>
>>>>
>>>> _______________________________________________
>>>> MacRuby-devel mailing list
>>>> MacRuby-devel at lists.macosforge.org
>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>>
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/837f60f8/attachment-0001.html>

From ruby-noreply at macosforge.org  Fri Oct  2 14:03:45 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 02 Oct 2009 21:03:45 -0000
Subject: [MacRuby-devel] [MacRuby] #362: Add Unit Testing and Embed
 MacRuby to Project Template
In-Reply-To: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
References: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
Message-ID: <059.1219d7610a0b7cb980910c937985821b@macosforge.org>

#362: Add Unit Testing and Embed MacRuby to Project Template
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |       Owner:  eloy.de.enige@?        
     Type:  enhancement          |      Status:  new                    
 Priority:  trivial              |   Milestone:                         
Component:  MacRuby              |    Keywords:                         
---------------------------------+------------------------------------------

Comment(by dylan@?):

 I like it. I've attached a version with the changes :)

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/362#comment:7>
MacRuby <http://macruby.org/>


From masterkain at gmail.com  Fri Oct  2 14:10:51 2009
From: masterkain at gmail.com (Claudio Poli)
Date: Fri, 2 Oct 2009 23:10:51 +0200
Subject: [MacRuby-devel] Supported classes & methods diagram fed from
	rubyspec
In-Reply-To: <20fefa50910021400r2872a303k42865e3ff2d9c27a@mail.gmail.com>
References: <E148045D-99B5-4CB6-9542-2973197873A4@gmail.com>
	<9939E537-6087-41E2-8EBD-A818C1C5B06F@apple.com>
	<D0AA1C17-5F29-42FB-A5B1-BD5611EF37FE@gmail.com>
	<E24BEB42-0CC6-48D1-B897-F2FF8A45CFD5@apple.com>
	<07A34B0C-48FC-4705-9133-E7898818F213@gmail.com>
	<20fefa50910021216y2b2cd6ebn222c57b21097fa01@mail.gmail.com>
	<2A915063-5955-46F6-BA62-A8241DC9182D@gmail.com>
	<20fefa50910021400r2872a303k42865e3ff2d9c27a@mail.gmail.com>
Message-ID: <A56927FD-82F5-47F1-A9AD-153D83021428@gmail.com>

hey, it's no problem :)
like Matt said if someone wants to fork/look the sinatra app is  
located at http://github.com/masterkain/macruby-nightlies-web .

the app itself it's considered somewhat stable but there's still room  
for improvements that I will do in next days, anyway I'm not going to  
change important functionality; it's open for forking.


otherwise I'm open to suggestions/direction on stuff to add to daily  
jobs.

cheers,
claudio

Il giorno 02/ott/2009, alle ore 23.00, Matt Aimonetti ha scritto:

> Wait, I said he "could" do it, or someone could fork the sinatra app  
> and add it, it's not done yet tho :)
> Btw, thanks a lot Claudio for making a server available!
>
> - Matt
>
>
> On Fri, Oct 2, 2009 at 12:19 PM, Eloy Duran  
> <eloy.de.enige at gmail.com> wrote:
> Oh serious?! I didn't know, awesome! Thanks Claudio, your my hero of  
> the day!
> Sorry Laurent, there will be plenty of other days left for you to  
> shine again ;-)
>
> Eloy
>
> On 2 okt 2009, at 21:16, Matt Aimonetti wrote:
>
>> Actually.... Claudio is doing that already ;) He might as well add  
>> one more step to his nightly building app.
>>
>> - Matt
>>
>> On Fri, Oct 2, 2009 at 12:11 PM, Eloy Duran  
>> <eloy.de.enige at gmail.com> wrote:
>> That looks great indeed Ben, much better than what my investigation  
>> in exiting solutions resulted in :)
>>
>> It would be great if we'd have a osx machine that would  
>> automatically run the suite at night and generate this from it. Any  
>> idea if that would become a possibility in the near future Laurent?
>>
>> Eloy
>>
>>
>> On 2 okt 2009, at 20:48, Laurent Sansonetti wrote:
>>
>> Hi Ben,
>>
>> I wasn't aware of that project, it looks good indeed. And the fact  
>> that it can be reused for different implementations of Ruby is very  
>> cool too :)
>>
>> Laurent
>>
>> On Oct 1, 2009, at 11:48 PM, Ben Schwarz wrote:
>>
>> Laurent,
>>
>> I just had a quick chat with Brian Ford (Rubinius) apparently  
>> they're looking at using some incarnation of git://github.com/madriska/unity.git 
>>  (http://unity.madriska.com/)
>> Which uses a YAML formatter for mspec. (http://github.com/madriska/mspec/commit/36b8bce62c272d546bcbd8ab9f136576ff4701e5 
>> )
>>
>> I think this might be the best way to get something that works  
>> running. I'm sure that all the ruby implementations would benefit  
>> from the shared work effort in this regard.
>> We could start by investigating unity, chatting to the author and  
>> seeing if we can make some contributions.
>>
>>
>>
>>
>> On 02/10/2009, at 4:23 PM, Laurent Sansonetti wrote:
>>
>> Hi Ben,
>>
>> That sounds like a good idea and looks like what I had in mind.
>>
>> I was thinking of having a status page, that shows hitlist items  
>> (critical bugs / things to do for the upcoming release), some  
>> rubyspec progress, a link to the latest nighty build, etc.
>>
>> The hitlist thing could be generated from a local file from the  
>> repository. We currently use TODO for that.
>>
>> We wrote a special mspec formatter in order to know what percentage  
>> of a given spec category we do pass. But having a more detailed  
>> view (classes / methods as you suggested) might be more  
>> interesting, this way we know on what class / method to focus in  
>> priority. Assuming that the mspec formatter is altered a little  
>> bit, this information could also be generated after a spec:ci pass.
>>
>> Is that what you had in mind?
>>
>> I guess the challenge here is to write a program that generates a  
>> Webby page for our website, commit it to the repository every time  
>> a change is made, then we would re-deploy the site right after.
>>
>> Laurent
>>
>> On Oct 1, 2009, at 11:01 PM, Ben Schwarz wrote:
>>
>> Hi all,
>>
>>
>> I've had some loose discussions with @lrz regarding a visual  
>> representation of classes and methods that are working via the  
>> rubyspec.
>> This would enable developers to find an area of development to  
>> focus on and also for end-users to understand what they might face  
>> before
>> conducting any development using macruby (bringing real  
>> applications closer to tuition, rather than a start/stop experience)
>>
>> I'm happy to offer some hours to get something together that is  
>> styled like macruby.org but I obviously need to:
>>
>>        A) consult the group
>>        B) work out a spec
>>        C) have something setup on the macruby.org infrastructure.
>>
>>
>> Discuss.
>>
>>
>> Cheers,
>>
>> -
>>
>> Ben Schwarz
>> Web architect
>>
>> Web:            http://www.germanforblack.com
>> Mobile:                 +61 407 339 418
>>
>> -- 
>> Please consider your environment before printing or distributing  
>> this material.
>> --
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Fri Oct  2 17:49:54 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 03 Oct 2009 00:49:54 -0000
Subject: [MacRuby-devel] [MacRuby] #362: Add Unit Testing and Embed
 MacRuby to Project Template
In-Reply-To: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
References: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
Message-ID: <059.0db15becfe7077c936dd5cd98cbed352@macosforge.org>

#362: Add Unit Testing and Embed MacRuby to Project Template
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |       Owner:  eloy.de.enige@?        
     Type:  enhancement          |      Status:  new                    
 Priority:  trivial              |   Milestone:                         
Component:  MacRuby              |    Keywords:                         
---------------------------------+------------------------------------------

Comment(by dylan@?):

 I was playing around with this a bit more and I noticed a bug in the
 template. Fix attached.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/362#comment:8>
MacRuby <http://macruby.org/>


From ben.schwarz at gmail.com  Fri Oct  2 17:57:18 2009
From: ben.schwarz at gmail.com (Ben Schwarz)
Date: Sat, 3 Oct 2009 10:57:18 +1000
Subject: [MacRuby-devel] Supported classes & methods diagram fed from
	rubyspec
In-Reply-To: <A56927FD-82F5-47F1-A9AD-153D83021428@gmail.com>
References: <E148045D-99B5-4CB6-9542-2973197873A4@gmail.com> 
	<9939E537-6087-41E2-8EBD-A818C1C5B06F@apple.com>
	<D0AA1C17-5F29-42FB-A5B1-BD5611EF37FE@gmail.com> 
	<E24BEB42-0CC6-48D1-B897-F2FF8A45CFD5@apple.com>
	<07A34B0C-48FC-4705-9133-E7898818F213@gmail.com> 
	<20fefa50910021216y2b2cd6ebn222c57b21097fa01@mail.gmail.com> 
	<2A915063-5955-46F6-BA62-A8241DC9182D@gmail.com>
	<20fefa50910021400r2872a303k42865e3ff2d9c27a@mail.gmail.com> 
	<A56927FD-82F5-47F1-A9AD-153D83021428@gmail.com>
Message-ID: <5619001149397642491@unknownmsgid>

Awsome Claudio, I'm definitly interested on helping the macruby space
out while I'm not committing C code :). I'm a bit over booked during
the next week but I hope to pull the unity project apart a bit.

I think that representing all flavours of ruby on unity is an
important step to bring thier authors closer together.

Last night I was thinking that a "percentage of core" progress bar
would be interesting to see between the projects.

Sent from my iPhone

On 03/10/2009, at 7:11 AM, Claudio Poli <masterkain at gmail.com> wrote:

> hey, it's no problem :)
> like Matt said if someone wants to fork/look the sinatra app is
> located at http://github.com/masterkain/macruby-nightlies-web .
>
> the app itself it's considered somewhat stable but there's still
> room for improvements that I will do in next days, anyway I'm not
> going to change important functionality; it's open for forking.
>
>
> otherwise I'm open to suggestions/direction on stuff to add to daily
> jobs.
>
> cheers,
> claudio
>
> Il giorno 02/ott/2009, alle ore 23.00, Matt Aimonetti ha scritto:
>
>> Wait, I said he "could" do it, or someone could fork the sinatra
>> app and add it, it's not done yet tho :)
>> Btw, thanks a lot Claudio for making a server available!
>>
>> - Matt
>>
>>
>> On Fri, Oct 2, 2009 at 12:19 PM, Eloy Duran
>> <eloy.de.enige at gmail.com> wrote:
>> Oh serious?! I didn't know, awesome! Thanks Claudio, your my hero
>> of the day!
>> Sorry Laurent, there will be plenty of other days left for you to
>> shine again ;-)
>>
>> Eloy
>>
>> On 2 okt 2009, at 21:16, Matt Aimonetti wrote:
>>
>>> Actually.... Claudio is doing that already ;) He might as well add
>>> one more step to his nightly building app.
>>>
>>> - Matt
>>>
>>> On Fri, Oct 2, 2009 at 12:11 PM, Eloy Duran
>>> <eloy.de.enige at gmail.com> wrote:
>>> That looks great indeed Ben, much better than what my
>>> investigation in exiting solutions resulted in :)
>>>
>>> It would be great if we'd have a osx machine that would
>>> automatically run the suite at night and generate this from it.
>>> Any idea if that would become a possibility in the near future
>>> Laurent?
>>>
>>> Eloy
>>>
>>>
>>> On 2 okt 2009, at 20:48, Laurent Sansonetti wrote:
>>>
>>> Hi Ben,
>>>
>>> I wasn't aware of that project, it looks good indeed. And the fact
>>> that it can be reused for different implementations of Ruby is
>>> very cool too :)
>>>
>>> Laurent
>>>
>>> On Oct 1, 2009, at 11:48 PM, Ben Schwarz wrote:
>>>
>>> Laurent,
>>>
>>> I just had a quick chat with Brian Ford (Rubinius) apparently
>>> they're looking at using some incarnation of git://github.com/
>>> madriska/unity.git (http://unity.madriska.com/)
>>> Which uses a YAML formatter for mspec. (http://github.com/madriska/mspec/commit/36b8bce62c272d546bcbd8ab9f136576ff4701e5
>>> )
>>>
>>> I think this might be the best way to get something that works
>>> running. I'm sure that all the ruby implementations would benefit
>>> from the shared work effort in this regard.
>>> We could start by investigating unity, chatting to the author and
>>> seeing if we can make some contributions.
>>>
>>>
>>>
>>>
>>> On 02/10/2009, at 4:23 PM, Laurent Sansonetti wrote:
>>>
>>> Hi Ben,
>>>
>>> That sounds like a good idea and looks like what I had in mind.
>>>
>>> I was thinking of having a status page, that shows hitlist items
>>> (critical bugs / things to do for the upcoming release), some
>>> rubyspec progress, a link to the latest nighty build, etc.
>>>
>>> The hitlist thing could be generated from a local file from the
>>> repository. We currently use TODO for that.
>>>
>>> We wrote a special mspec formatter in order to know what
>>> percentage of a given spec category we do pass. But having a more
>>> detailed view (classes / methods as you suggested) might be more
>>> interesting, this way we know on what class / method to focus in
>>> priority. Assuming that the mspec formatter is altered a little
>>> bit, this information could also be generated after a spec:ci pass.
>>>
>>> Is that what you had in mind?
>>>
>>> I guess the challenge here is to write a program that generates a
>>> Webby page for our website, commit it to the repository every time
>>> a change is made, then we would re-deploy the site right after.
>>>
>>> Laurent
>>>
>>> On Oct 1, 2009, at 11:01 PM, Ben Schwarz wrote:
>>>
>>> Hi all,
>>>
>>>
>>> I've had some loose discussions with @lrz regarding a visual
>>> representation of classes and methods that are working via the
>>> rubyspec.
>>> This would enable developers to find an area of development to
>>> focus on and also for end-users to understand what they might face
>>> before
>>> conducting any development using macruby (bringing real
>>> applications closer to tuition, rather than a start/stop experience)
>>>
>>> I'm happy to offer some hours to get something together that is
>>> styled like macruby.org but I obviously need to:
>>>
>>>       A) consult the group
>>>       B) work out a spec
>>>       C) have something setup on the macruby.org infrastructure.
>>>
>>>
>>> Discuss.
>>>
>>>
>>> Cheers,
>>>
>>> -
>>>
>>> Ben Schwarz
>>> Web architect
>>>
>>> Web:            http://www.germanforblack.com
>>> Mobile:                 +61 407 339 418
>>>
>>> --
>>> Please consider your environment before printing or distributing
>>> this material.
>>> --
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

From trevor at monts.demon.co.uk  Sat Oct  3 04:52:12 2009
From: trevor at monts.demon.co.uk (Trevor Hills)
Date: Sat, 3 Oct 2009 12:52:12 +0100
Subject: [MacRuby-devel] HotCocoa on_notification Method with Snow Leopard
Message-ID: <E8EBCEFD-42B0-495F-9CDD-5A659357C72A@monts.demon.co.uk>

I have a small MacRuby/HotCocoa application that uses the  
on_notification method described by Richard Kilmer in his post of Sept  
19 2008 http://lists.macosforge.org/pipermail/macruby-devel/2008-September/000539.html

This application worked well under MacRuby 0.4 and Mac OS 10.5. It  
intercepts Spotify Growl messages to obtain track title and artist  
information to pass into an AppleScript Studio application I wrote.  
The MacRuby/HotCocoa app was provided by a friendly software  
developer, Peter MacRobert, for me since ASS did not have the  
appropriate inter-process message handling capability.

I upgraded to Snow Leopard and discovered that the app crashed out  
with MacRuby 0.4. I succeeded in downloading and installing MacRuby  
0.5 and now the app loads successfully with no error messages as  
before under Leopard.

Unfortunately the on_notification code does not get triggered any  
longer. No error messages, just stubbornly refuses to respond when the  
Distributed Notifications Center gets the Spotify message. I am able  
to see that the message is there by firing up Growl which shows the  
message each time Spotify plays a track.

I'm looking for guidance if anybody has any words of wisdom please?  
Has something changed under MacOS 10.6.1 to do with the Distributed  
Notifications Center or is it likely that my re-installation of  
MacRuby 0.5 is incorrect and I have to do something additional to get  
the on_notification method re-enabled?

My googling efforts suggest that there are changes in inter-process  
security with Snow Leopard but I am unable to discover any security  
violation error messages.

Regards

Trevor Hills

From ruby-noreply at macosforge.org  Sat Oct  3 12:29:45 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 03 Oct 2009 19:29:45 -0000
Subject: [MacRuby-devel] [MacRuby] #363: IO.copy_stream dont handle copyfile.
Message-ID: <049.e7b5edbada4eb86a7d2dacb90726d131@macosforge.org>

#363: IO.copy_stream dont handle copyfile.
--------------------------------+-------------------------------------------
 Reporter:  kazuhisa@?          |       Owner:  lsansonetti@?        
     Type:  defect              |      Status:  new                  
 Priority:  minor               |   Milestone:  MacRuby 0.5          
Component:  MacRuby             |    Keywords:                       
--------------------------------+-------------------------------------------
 I try to run folloing script.
 {{{
   src = open("a")
   dst = open("b","w+")
   IO.copy_stream(src,dst)
   src.close
   dst.close
 }}}
 I expected to run via copyfile function . but not.
 because src/dst object is indicated as not T_FILE by rb_type.(T_NATIVE)

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/363>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct  3 15:00:03 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 03 Oct 2009 22:00:03 -0000
Subject: [MacRuby-devel] [MacRuby] #363: IO.copy_stream dont handle
	copyfile.
In-Reply-To: <049.e7b5edbada4eb86a7d2dacb90726d131@macosforge.org>
References: <049.e7b5edbada4eb86a7d2dacb90726d131@macosforge.org>
Message-ID: <058.bb281fcb49b5be5229efabde92478ab8@macosforge.org>

#363: IO.copy_stream dont handle copyfile.
--------------------------------+-------------------------------------------
 Reporter:  kazuhisa@?          |       Owner:  lsansonetti@?        
     Type:  defect              |      Status:  new                  
 Priority:  minor               |   Milestone:  MacRuby 0.5          
Component:  MacRuby             |    Keywords:                       
--------------------------------+-------------------------------------------

Comment(by lsansonetti@?):

 Currently, copyfile() is only used if both operands are file paths
 (strings), otherwise we simulate it.

 If an operand is of T_FILE and if its seek offset is 0 and if it has a
 path, we could potentially use copyfile() too (and update the seek offset
 in case it's the destination operand).

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/363#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sun Oct  4 00:33:44 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 04 Oct 2009 07:33:44 -0000
Subject: [MacRuby-devel] [MacRuby] #363: IO.copy_stream dont handle
	copyfile.
In-Reply-To: <049.e7b5edbada4eb86a7d2dacb90726d131@macosforge.org>
References: <049.e7b5edbada4eb86a7d2dacb90726d131@macosforge.org>
Message-ID: <058.6c628e3b9bcd8d634ff548715c591c37@macosforge.org>

#363: IO.copy_stream dont handle copyfile.
--------------------------------+-------------------------------------------
 Reporter:  kazuhisa@?          |       Owner:  lsansonetti@?        
     Type:  defect              |      Status:  new                  
 Priority:  minor               |   Milestone:  MacRuby 0.5          
Component:  MacRuby             |    Keywords:                       
--------------------------------+-------------------------------------------

Comment(by kazuhisa@?):

 ok. understand. but i have one question.

  * why  is this routine not  ported from matzruby 1.9 without copyfille?
 if i copied IO via IO.copy_stream, all memory for copy  is allocated (
 examply fille size is 500M , 1 G)
  * BUILDIN_TYPE should not be called in rb_type before NATIVE(obj) ?
  * why fcopyfile is not used ? the reason is exists? ( sorry i dont know
 detail of fcopyfile specification ....  )

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/363#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct  5 10:50:41 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Mon, 05 Oct 2009 17:50:41 -0000
Subject: [MacRuby-devel] [MacRuby] #362: Add Unit Testing and Embed
 MacRuby to Project Template
In-Reply-To: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
References: <050.1810f83b3786f3e0a94b0de11bc07774@macosforge.org>
Message-ID: <059.dcc405ee0c041bb8cce2c14848a43473@macosforge.org>

#362: Add Unit Testing and Embed MacRuby to Project Template
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |        Owner:  eloy.de.enige@?        
     Type:  enhancement          |       Status:  closed                 
 Priority:  trivial              |    Milestone:                         
Component:  MacRuby              |   Resolution:  fixed                  
 Keywords:                       |  
---------------------------------+------------------------------------------
Changes (by eloy.de.enige@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Thanks! Committed in r2723 & r2724. Please double check everything works
 as expected.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/362#comment:9>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Mon Oct  5 14:04:16 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Mon, 05 Oct 2009 14:04:16 -0700
Subject: [MacRuby-devel] HotCocoa on_notification Method with Snow
	Leopard
In-Reply-To: <E8EBCEFD-42B0-495F-9CDD-5A659357C72A@monts.demon.co.uk>
References: <E8EBCEFD-42B0-495F-9CDD-5A659357C72A@monts.demon.co.uk>
Message-ID: <A7864F0A-56B6-4851-9EEC-527B50671635@apple.com>

Hi Trevor,

Thanks for the report. It's very likely a bug in MacRuby 0.5. If you  
are willing to create a test case that reproduces the problem we can  
then investigate a fix.

Laurent

On Oct 3, 2009, at 4:52 AM, Trevor Hills wrote:

> I have a small MacRuby/HotCocoa application that uses the  
> on_notification method described by Richard Kilmer in his post of  
> Sept 19 2008 http://lists.macosforge.org/pipermail/macruby-devel/2008-September/000539.html
>
> This application worked well under MacRuby 0.4 and Mac OS 10.5. It  
> intercepts Spotify Growl messages to obtain track title and artist  
> information to pass into an AppleScript Studio application I wrote.  
> The MacRuby/HotCocoa app was provided by a friendly software  
> developer, Peter MacRobert, for me since ASS did not have the  
> appropriate inter-process message handling capability.
>
> I upgraded to Snow Leopard and discovered that the app crashed out  
> with MacRuby 0.4. I succeeded in downloading and installing MacRuby  
> 0.5 and now the app loads successfully with no error messages as  
> before under Leopard.
>
> Unfortunately the on_notification code does not get triggered any  
> longer. No error messages, just stubbornly refuses to respond when  
> the Distributed Notifications Center gets the Spotify message. I am  
> able to see that the message is there by firing up Growl which shows  
> the message each time Spotify plays a track.
>
> I'm looking for guidance if anybody has any words of wisdom please?  
> Has something changed under MacOS 10.6.1 to do with the Distributed  
> Notifications Center or is it likely that my re-installation of  
> MacRuby 0.5 is incorrect and I have to do something additional to  
> get the on_notification method re-enabled?
>
> My googling efforts suggest that there are changes in inter-process  
> security with Snow Leopard but I am unable to discover any security  
> violation error messages.
>
> Regards
>
> Trevor Hills
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From lsansonetti at apple.com  Mon Oct  5 14:34:15 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Mon, 05 Oct 2009 14:34:15 -0700
Subject: [MacRuby-devel] trunk status update
Message-ID: <1F1AE689-E1CB-4E33-8350-B889156D37B1@apple.com>

Another status update, covering about 2 weeks of development.

Highlights:

- Early backtracing support.
- Much better AOT compilation. Parts of the standard library are now  
pre-compiled for testing.
- Migrated to LLVM top of tree.
- Dispatcher performance is now back to normal (we lost about 30% due  
to gcc not inlining code).
- Many bug fixes.

We are content-complete for a first beta release of MacRuby 0.5.  We  
will release it very soon then continue converging until the final 0.5  
release.

Details:

- Better GCD documentation
- Implemented Symbol.all_symbols
- Rewrote the file loader (file.c) fixing a few bugs
- Added preliminary support for backtracing / symbolication
- Make sure stdio objects are never finalized
- Fixed more eval/Binding bugs
- Fixed END{} block
- Fixed a memory problem in the libyaml extension
- Fixed rescues in rescues (most cases)
- Fixed a 10.5-only bug in the new Array class
- Fixed a bug of the parser when dealing with byte strings
- AOT: now compiling part of the stdlib (notably irb and rubygems)
- AOT: fixed bugs in the compilation of defined?, undef,  
rb_eStandardError, literal ranges
- Fixed a bug in the compilation of `for' loops
- Fixed many minor compilation bugs discovered by the LLVM module  
verifier
- The arguments resolver is now able to deal with any number of  
arguments
- Fixed minor String bugs
- Added autorelease and dealloc to the list of handled ignored selectors
- Fixed a bug when instance variables were not visible from within an  
iterator in method called through KVO
- Fixed an infinite recursion trying to convert an NSPathStore2 to a  
string
- Moved to LLVM r82747, enabled LLVM multithreaded mode
- Fixed GC problems in the parser
- Create all ruby scopes with external linkage, otherwise the AOT  
compiler won't generate frame info for them
- Fixed a bug when open would crash when mode is numeric
- Now using a gcc constructor to initialize .rbo files
- Added Dispatch::Semaphore + fixed a few things
- Make sure RoxorVM instances created lazily have a valid thread  
accessor
- Fixed a random bug of Numeric#chr
- macruby is now SIGINT interruptible (but no exception is raised, yet)
- Fixed a few 32-bit only bugs
- Fixed a GC bug in builtin global variable setters
- Fixed a bug in Set#to_a
- Fixed the BridgeSupport parser to properly handle one liner <method>  
elements
- Fixed variadic functions/methods calls
- Fixed a few bugs in Array#pack
- Fixed a serious bug in the way we used to promote strings to byte  
strings
- Fixed a few bugs in IO#ioctl and IO#fcntl
- Now separately compiling the dispatcher and forcing function inlining
- Fixed a bug in File.open when file permissions were not taken into  
account
- Make sure ivar slot generation is disabled when compiling attr  
accessors
- Fixed a bug in the way we AOT compile super method cache
- Added an empty Ruby template file
- Improved the MacRuby Application template: Embed MacRuby target and  
some unit testing mechanism are added

Laurent

From tali.wang at gmail.com  Mon Oct  5 16:55:23 2009
From: tali.wang at gmail.com (Linan Wang)
Date: Tue, 6 Oct 2009 00:55:23 +0100
Subject: [MacRuby-devel] implementation of symbols
Message-ID: <1B621C31-8160-4FE7-9766-D6E24F17E579@gmail.com>

Hi,
I read a little bit source codes and found out that Symbol is  
implemented on top of NSString. My question is if it's a better choice  
to use SEL as the basis when objc is available? objc runtime takes  
care of the registration and management. I guess using NSString class  
is a decision with good reasons, could anybody please shine some  
lights on it? Thanks
Best wishes
Linan

From lsansonetti at apple.com  Mon Oct  5 17:05:27 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Mon, 05 Oct 2009 17:05:27 -0700
Subject: [MacRuby-devel] implementation of symbols
In-Reply-To: <1B621C31-8160-4FE7-9766-D6E24F17E579@gmail.com>
References: <1B621C31-8160-4FE7-9766-D6E24F17E579@gmail.com>
Message-ID: <3B3A3114-43D0-4F58-A505-C9170FD7E121@apple.com>

Hi Linan,

Actually, we do use SELs to unify symbols (if you look at parse.y).  
The Symbol class just inherits from NSString for convenience purposes.

The current code is far to be perfect but so far it works okay.

Laurent

On Oct 5, 2009, at 4:55 PM, Linan Wang wrote:

> Hi,
> I read a little bit source codes and found out that Symbol is  
> implemented on top of NSString. My question is if it's a better  
> choice to use SEL as the basis when objc is available? objc runtime  
> takes care of the registration and management. I guess using  
> NSString class is a decision with good reasons, could anybody please  
> shine some lights on it? Thanks
> Best wishes
> Linan
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From tali.wang at gmail.com  Mon Oct  5 17:06:58 2009
From: tali.wang at gmail.com (Linan Wang)
Date: Tue, 6 Oct 2009 01:06:58 +0100
Subject: [MacRuby-devel] implementation of symbols
In-Reply-To: <3B3A3114-43D0-4F58-A505-C9170FD7E121@apple.com>
References: <1B621C31-8160-4FE7-9766-D6E24F17E579@gmail.com>
	<3B3A3114-43D0-4F58-A505-C9170FD7E121@apple.com>
Message-ID: <ABE9B60C-7ADC-4545-8DD5-A4C4A28C16EC@gmail.com>

That's a quick response. I'll look into the codes. Thanks!
On 6 Oct 2009, at 01:05, Laurent Sansonetti wrote:

> Hi Linan,
>
> Actually, we do use SELs to unify symbols (if you look at parse.y).  
> The Symbol class just inherits from NSString for convenience purposes.
>
> The current code is far to be perfect but so far it works okay.
>
> Laurent
>
> On Oct 5, 2009, at 4:55 PM, Linan Wang wrote:
>
>> Hi,
>> I read a little bit source codes and found out that Symbol is  
>> implemented on top of NSString. My question is if it's a better  
>> choice to use SEL as the basis when objc is available? objc runtime  
>> takes care of the registration and management. I guess using  
>> NSString class is a decision with good reasons, could anybody  
>> please shine some lights on it? Thanks
>> Best wishes
>> Linan
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From gdeciantis at gmail.com  Mon Oct  5 17:11:16 2009
From: gdeciantis at gmail.com (Giampiero De Ciantis)
Date: Mon, 5 Oct 2009 20:11:16 -0400
Subject: [MacRuby-devel] implement Enumerable::Enumerator
Message-ID: <677A94A5-A9A6-4C5D-AA5B-EE4D23FB1916@gmail.com>

I wanted to contribute to the project and I am not sure what I am  
seeing. I ran the following specs:

  ./mspec/bin/mspec ci -B ./spec/macruby.mspec ./spec/frozen/core/ 
enumerator

and

./mspec/bin/mspec ci -B ./spec/macruby.mspec ./spec/frozen/core/ 
enumerable

Both of these groups of specs pass. Does that mean that the TODO item  
is done or am I not running the right commands?

Cheers,

-Gp

From lsansonetti at apple.com  Mon Oct  5 17:19:15 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Mon, 05 Oct 2009 17:19:15 -0700
Subject: [MacRuby-devel] implement Enumerable::Enumerator
In-Reply-To: <677A94A5-A9A6-4C5D-AA5B-EE4D23FB1916@gmail.com>
References: <677A94A5-A9A6-4C5D-AA5B-EE4D23FB1916@gmail.com>
Message-ID: <706FA76B-E162-4ECF-89A8-7CC092842D6A@apple.com>

Hi Giampiero,

I think it works because the specs are tagged :) Check out spec/frozen/ 
tags/macruby/core/enumerator.

Supporting Enumerable::Enumerator might be harder than planned. I  
think we will have to implement coroutines first. I wonder if we want  
to do that for 0.5.

Laurent

On Oct 5, 2009, at 5:11 PM, Giampiero De Ciantis wrote:

> I wanted to contribute to the project and I am not sure what I am  
> seeing. I ran the following specs:
>
> ./mspec/bin/mspec ci -B ./spec/macruby.mspec ./spec/frozen/core/ 
> enumerator
>
> and
>
> ./mspec/bin/mspec ci -B ./spec/macruby.mspec ./spec/frozen/core/ 
> enumerable
>
> Both of these groups of specs pass. Does that mean that the TODO  
> item is done or am I not running the right commands?
>
> Cheers,
>
> -Gp
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From gdeciantis at gmail.com  Mon Oct  5 17:50:19 2009
From: gdeciantis at gmail.com (Giampiero De Ciantis)
Date: Mon, 5 Oct 2009 20:50:19 -0400
Subject: [MacRuby-devel] implement Enumerable::Enumerator
In-Reply-To: <706FA76B-E162-4ECF-89A8-7CC092842D6A@apple.com>
References: <677A94A5-A9A6-4C5D-AA5B-EE4D23FB1916@gmail.com>
	<706FA76B-E162-4ECF-89A8-7CC092842D6A@apple.com>
Message-ID: <D9684950-C49C-4EE2-864F-493251BA895C@gmail.com>

Somehow I always pick dead ends.

I guess I am out of my league with this project.

Thanks,

-Gp
On 2009-10-05, at 8:19 PM, Laurent Sansonetti wrote:

> Hi Giampiero,
>
> I think it works because the specs are tagged :) Check out spec/ 
> frozen/tags/macruby/core/enumerator.
>
> Supporting Enumerable::Enumerator might be harder than planned. I  
> think we will have to implement coroutines first. I wonder if we  
> want to do that for 0.5.
>
> Laurent
>
> On Oct 5, 2009, at 5:11 PM, Giampiero De Ciantis wrote:
>
>> I wanted to contribute to the project and I am not sure what I am  
>> seeing. I ran the following specs:
>>
>> ./mspec/bin/mspec ci -B ./spec/macruby.mspec ./spec/frozen/core/ 
>> enumerator
>>
>> and
>>
>> ./mspec/bin/mspec ci -B ./spec/macruby.mspec ./spec/frozen/core/ 
>> enumerable
>>
>> Both of these groups of specs pass. Does that mean that the TODO  
>> item is done or am I not running the right commands?
>>
>> Cheers,
>>
>> -Gp
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From vincent.isambart at gmail.com  Mon Oct  5 17:50:54 2009
From: vincent.isambart at gmail.com (Vincent Isambart)
Date: Tue, 6 Oct 2009 09:50:54 +0900
Subject: [MacRuby-devel] implement Enumerable::Enumerator
In-Reply-To: <706FA76B-E162-4ECF-89A8-7CC092842D6A@apple.com>
References: <677A94A5-A9A6-4C5D-AA5B-EE4D23FB1916@gmail.com>
	<706FA76B-E162-4ECF-89A8-7CC092842D6A@apple.com>
Message-ID: <7d9a1f530910051750s3fcb00d6x81c5290ad2ed6abb@mail.gmail.com>

> Supporting Enumerable::Enumerator might be harder than planned. I think we
> will have to implement coroutines first. I wonder if we want to do that for
> 0.5.

I think it can wait after 0.5. There's already enough things to do for 0.5 ;-)

From koudelka at ryoukai.org  Mon Oct  5 18:37:01 2009
From: koudelka at ryoukai.org (Michael Shapiro)
Date: Mon, 5 Oct 2009 21:37:01 -0400
Subject: [MacRuby-devel] Super not passing init: through to NSObject
	correctly?
Message-ID: <D8F21FD3-3C56-41A0-9CCE-D771329DB37B@ryoukai.org>

Hi all,
I searched a few months of the list archives and trac, but wasn't able  
to find reference to this.

Calling `super` inside of an overridden #init function where no ruby  
ancestors define #init causes a segmentation fault. If I'm not  
mistaken, shouldn't the init: message be passed to NSObject?

---------------------------------------------------------
class HasInit
def init
   super
   p 'HasInit'
   self
end
end

class A < HasInit; end

class B < A; end

A.new
p 'A'
B.new
p 'B'

class HasNoInit; end

class C < HasNoInit; end

class D < C
def init
   super
   self
end
end

C.new
p 'C'
D.new
p 'D'
---------------------------------------------------------

You should see the segfault happen when trying to init D, but HasInit  
passes the message through to NSObject just fine, it seems.

Tested with the 2009-10-05-1158 nightly.

Thanks!
--Mike

From cwdinfo at gmail.com  Mon Oct  5 19:32:04 2009
From: cwdinfo at gmail.com (s.ross)
Date: Mon, 5 Oct 2009 19:32:04 -0700
Subject: [MacRuby-devel] trunk status update
In-Reply-To: <1F1AE689-E1CB-4E33-8350-B889156D37B1@apple.com>
References: <1F1AE689-E1CB-4E33-8350-B889156D37B1@apple.com>
Message-ID: <BB1585D8-8649-49D5-BC6B-C8D3859AF732@gmail.com>

Great progress. I'm pretty sure you would have mentioned it in the  
release notes if it were stable, but has there been any progress  
making MacRuby work properly on Snow Leopard 32-bit architectures like  
the Core Duo? (nag, nag :)

Thx


On Oct 5, 2009, at 2:34 PM, Laurent Sansonetti wrote:

> Another status update, covering about 2 weeks of development.
>
> Highlights:
>
> - Early backtracing support.
> - Much better AOT compilation. Parts of the standard library are now  
> pre-compiled for testing.
> - Migrated to LLVM top of tree.
> - Dispatcher performance is now back to normal (we lost about 30%  
> due to gcc not inlining code).
> - Many bug fixes.
>
> We are content-complete for a first beta release of MacRuby 0.5.  We  
> will release it very soon then continue converging until the final  
> 0.5 release.
>
> Details:
>
> - Better GCD documentation
> - Implemented Symbol.all_symbols
> - Rewrote the file loader (file.c) fixing a few bugs
> - Added preliminary support for backtracing / symbolication
> - Make sure stdio objects are never finalized
> - Fixed more eval/Binding bugs
> - Fixed END{} block
> - Fixed a memory problem in the libyaml extension
> - Fixed rescues in rescues (most cases)
> - Fixed a 10.5-only bug in the new Array class
> - Fixed a bug of the parser when dealing with byte strings
> - AOT: now compiling part of the stdlib (notably irb and rubygems)
> - AOT: fixed bugs in the compilation of defined?, undef,  
> rb_eStandardError, literal ranges
> - Fixed a bug in the compilation of `for' loops
> - Fixed many minor compilation bugs discovered by the LLVM module  
> verifier
> - The arguments resolver is now able to deal with any number of  
> arguments
> - Fixed minor String bugs
> - Added autorelease and dealloc to the list of handled ignored  
> selectors
> - Fixed a bug when instance variables were not visible from within  
> an iterator in method called through KVO
> - Fixed an infinite recursion trying to convert an NSPathStore2 to a  
> string
> - Moved to LLVM r82747, enabled LLVM multithreaded mode
> - Fixed GC problems in the parser
> - Create all ruby scopes with external linkage, otherwise the AOT  
> compiler won't generate frame info for them
> - Fixed a bug when open would crash when mode is numeric
> - Now using a gcc constructor to initialize .rbo files
> - Added Dispatch::Semaphore + fixed a few things
> - Make sure RoxorVM instances created lazily have a valid thread  
> accessor
> - Fixed a random bug of Numeric#chr
> - macruby is now SIGINT interruptible (but no exception is raised,  
> yet)
> - Fixed a few 32-bit only bugs
> - Fixed a GC bug in builtin global variable setters
> - Fixed a bug in Set#to_a
> - Fixed the BridgeSupport parser to properly handle one liner  
> <method> elements
> - Fixed variadic functions/methods calls
> - Fixed a few bugs in Array#pack
> - Fixed a serious bug in the way we used to promote strings to byte  
> strings
> - Fixed a few bugs in IO#ioctl and IO#fcntl
> - Now separately compiling the dispatcher and forcing function  
> inlining
> - Fixed a bug in File.open when file permissions were not taken into  
> account
> - Make sure ivar slot generation is disabled when compiling attr  
> accessors
> - Fixed a bug in the way we AOT compile super method cache
> - Added an empty Ruby template file
> - Improved the MacRuby Application template: Embed MacRuby target  
> and some unit testing mechanism are added
>
> Laurent
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From vincent.isambart at gmail.com  Mon Oct  5 19:46:48 2009
From: vincent.isambart at gmail.com (Vincent Isambart)
Date: Tue, 6 Oct 2009 11:46:48 +0900
Subject: [MacRuby-devel] trunk status update
In-Reply-To: <BB1585D8-8649-49D5-BC6B-C8D3859AF732@gmail.com>
References: <1F1AE689-E1CB-4E33-8350-B889156D37B1@apple.com>
	<BB1585D8-8649-49D5-BC6B-C8D3859AF732@gmail.com>
Message-ID: <7d9a1f530910051946m7fd8e779l8edaf36eb604ba8f@mail.gmail.com>

> Great progress. I'm pretty sure you would have mentioned it in the release
> notes if it were stable, but has there been any progress making MacRuby work
> properly on Snow Leopard 32-bit architectures like the Core Duo? (nag, nag
> :)

Yes, 32-bit mode should work better (Laurent fixed the asserts that
were failing), but there is still one important problem : Objective-C
exceptions cannot be caught yet in 32-bit MacRuby.

From lsansonetti at apple.com  Mon Oct  5 19:45:21 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Mon, 05 Oct 2009 19:45:21 -0700
Subject: [MacRuby-devel] Super not passing init: through to
	NSObject	correctly?
In-Reply-To: <D8F21FD3-3C56-41A0-9CCE-D771329DB37B@ryoukai.org>
References: <D8F21FD3-3C56-41A0-9CCE-D771329DB37B@ryoukai.org>
Message-ID: <6C77D8CF-BB58-4DB8-85C4-537FA4E0467D@apple.com>

Thanks for the report, I added your snippet in our test suite.

At a glance it looks like an infinite loop in the dispatcher.  
Definitely a bug :)

Laurent

On Oct 5, 2009, at 6:37 PM, Michael Shapiro wrote:

> Hi all,
> I searched a few months of the list archives and trac, but wasn't  
> able to find reference to this.
>
> Calling `super` inside of an overridden #init function where no ruby  
> ancestors define #init causes a segmentation fault. If I'm not  
> mistaken, shouldn't the init: message be passed to NSObject?
>
> ---------------------------------------------------------
> class HasInit
> def init
>  super
>  p 'HasInit'
>  self
> end
> end
>
> class A < HasInit; end
>
> class B < A; end
>
> A.new
> p 'A'
> B.new
> p 'B'
>
> class HasNoInit; end
>
> class C < HasNoInit; end
>
> class D < C
> def init
>  super
>  self
> end
> end
>
> C.new
> p 'C'
> D.new
> p 'D'
> ---------------------------------------------------------
>
> You should see the segfault happen when trying to init D, but  
> HasInit passes the message through to NSObject just fine, it seems.
>
> Tested with the 2009-10-05-1158 nightly.
>
> Thanks!
> --Mike
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From lsansonetti at apple.com  Mon Oct  5 19:47:01 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Mon, 05 Oct 2009 19:47:01 -0700
Subject: [MacRuby-devel] trunk status update
In-Reply-To: <BB1585D8-8649-49D5-BC6B-C8D3859AF732@gmail.com>
References: <1F1AE689-E1CB-4E33-8350-B889156D37B1@apple.com>
	<BB1585D8-8649-49D5-BC6B-C8D3859AF732@gmail.com>
Message-ID: <98E101C0-0345-46A4-A390-78B1E5874E49@apple.com>

Hi,

I fixed several 32-bit bugs, so it should be better. However, the  
specs don't pass at 100% yet (a notable thing is that ruby exceptions  
cannot be intercepted by objc).

Feel free to give it a try and let us know if it's better now :)

Laurent

On Oct 5, 2009, at 7:32 PM, s.ross wrote:

> Great progress. I'm pretty sure you would have mentioned it in the  
> release notes if it were stable, but has there been any progress  
> making MacRuby work properly on Snow Leopard 32-bit architectures  
> like the Core Duo? (nag, nag :)
>
> Thx
>
>
> On Oct 5, 2009, at 2:34 PM, Laurent Sansonetti wrote:
>
>> Another status update, covering about 2 weeks of development.
>>
>> Highlights:
>>
>> - Early backtracing support.
>> - Much better AOT compilation. Parts of the standard library are  
>> now pre-compiled for testing.
>> - Migrated to LLVM top of tree.
>> - Dispatcher performance is now back to normal (we lost about 30%  
>> due to gcc not inlining code).
>> - Many bug fixes.
>>
>> We are content-complete for a first beta release of MacRuby 0.5.   
>> We will release it very soon then continue converging until the  
>> final 0.5 release.
>>
>> Details:
>>
>> - Better GCD documentation
>> - Implemented Symbol.all_symbols
>> - Rewrote the file loader (file.c) fixing a few bugs
>> - Added preliminary support for backtracing / symbolication
>> - Make sure stdio objects are never finalized
>> - Fixed more eval/Binding bugs
>> - Fixed END{} block
>> - Fixed a memory problem in the libyaml extension
>> - Fixed rescues in rescues (most cases)
>> - Fixed a 10.5-only bug in the new Array class
>> - Fixed a bug of the parser when dealing with byte strings
>> - AOT: now compiling part of the stdlib (notably irb and rubygems)
>> - AOT: fixed bugs in the compilation of defined?, undef,  
>> rb_eStandardError, literal ranges
>> - Fixed a bug in the compilation of `for' loops
>> - Fixed many minor compilation bugs discovered by the LLVM module  
>> verifier
>> - The arguments resolver is now able to deal with any number of  
>> arguments
>> - Fixed minor String bugs
>> - Added autorelease and dealloc to the list of handled ignored  
>> selectors
>> - Fixed a bug when instance variables were not visible from within  
>> an iterator in method called through KVO
>> - Fixed an infinite recursion trying to convert an NSPathStore2 to  
>> a string
>> - Moved to LLVM r82747, enabled LLVM multithreaded mode
>> - Fixed GC problems in the parser
>> - Create all ruby scopes with external linkage, otherwise the AOT  
>> compiler won't generate frame info for them
>> - Fixed a bug when open would crash when mode is numeric
>> - Now using a gcc constructor to initialize .rbo files
>> - Added Dispatch::Semaphore + fixed a few things
>> - Make sure RoxorVM instances created lazily have a valid thread  
>> accessor
>> - Fixed a random bug of Numeric#chr
>> - macruby is now SIGINT interruptible (but no exception is raised,  
>> yet)
>> - Fixed a few 32-bit only bugs
>> - Fixed a GC bug in builtin global variable setters
>> - Fixed a bug in Set#to_a
>> - Fixed the BridgeSupport parser to properly handle one liner  
>> <method> elements
>> - Fixed variadic functions/methods calls
>> - Fixed a few bugs in Array#pack
>> - Fixed a serious bug in the way we used to promote strings to byte  
>> strings
>> - Fixed a few bugs in IO#ioctl and IO#fcntl
>> - Now separately compiling the dispatcher and forcing function  
>> inlining
>> - Fixed a bug in File.open when file permissions were not taken  
>> into account
>> - Make sure ivar slot generation is disabled when compiling attr  
>> accessors
>> - Fixed a bug in the way we AOT compile super method cache
>> - Added an empty Ruby template file
>> - Improved the MacRuby Application template: Embed MacRuby target  
>> and some unit testing mechanism are added
>>
>> Laurent
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From conradwt at gmail.com  Mon Oct  5 20:01:45 2009
From: conradwt at gmail.com (Conrad Taylor)
Date: Mon, 5 Oct 2009 20:01:45 -0700
Subject: [MacRuby-devel] Super not passing init: through to NSObject
	correctly?
In-Reply-To: <6C77D8CF-BB58-4DB8-85C4-537FA4E0467D@apple.com>
References: <D8F21FD3-3C56-41A0-9CCE-D771329DB37B@ryoukai.org>
	<6C77D8CF-BB58-4DB8-85C4-537FA4E0467D@apple.com>
Message-ID: <7317d7610910052001w3efad883xc1c78d7b957c9553@mail.gmail.com>

What should be the exact output?  In Ruby 1.9.1, I see the following output:
$ ruby test.rb
"A"
"B"
"C"
"D"

Note:  When <class>.new is called allocate method is called.  Then the
object's initialize method is called and the
          instance is returned to the caller.

$ macruby test.rb
"HasInit"
"A"
"HasInit"
"B"
"C"
Segmentation fault

Now, changing the init methods to initialize, the following output is
generated:

$ ruby test.rb
"HasInit"
"A"
"HasInit"
"B"
"C"
"D"

$ macruby test.rb
"HasInit"
"A"
"HasInit"
"B"
"C"
"D"

Next, will there be an implementation of BasicObject in MacRuby as it is in
Ruby 1.9.x?

-Conrad

On Mon, Oct 5, 2009 at 7:45 PM, Laurent Sansonetti <lsansonetti at apple.com>wrote:

> Thanks for the report, I added your snippet in our test suite.
>
> At a glance it looks like an infinite loop in the dispatcher. Definitely a
> bug :)
>
> Laurent
>
>
> On Oct 5, 2009, at 6:37 PM, Michael Shapiro wrote:
>
>  Hi all,
>> I searched a few months of the list archives and trac, but wasn't able to
>> find reference to this.
>>
>> Calling `super` inside of an overridden #init function where no ruby
>> ancestors define #init causes a segmentation fault. If I'm not mistaken,
>> shouldn't the init: message be passed to NSObject?
>>
>> ---------------------------------------------------------
>> class HasInit
>> def init
>>  super
>>  p 'HasInit'
>>  self
>> end
>> end
>>
>> class A < HasInit; end
>>
>> class B < A; end
>>
>> A.new
>> p 'A'
>> B.new
>> p 'B'
>>
>> class HasNoInit; end
>>
>> class C < HasNoInit; end
>>
>> class D < C
>> def init
>>  super
>>  self
>> end
>> end
>>
>> C.new
>> p 'C'
>> D.new
>> p 'D'
>> ---------------------------------------------------------
>>
>> You should see the segfault happen when trying to init D, but HasInit
>> passes the message through to NSObject just fine, it seems.
>>
>> Tested with the 2009-10-05-1158 nightly.
>>
>> Thanks!
>> --Mike
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091005/3b38879d/attachment.html>

From lsansonetti at apple.com  Mon Oct  5 20:08:41 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Mon, 05 Oct 2009 20:08:41 -0700
Subject: [MacRuby-devel] Super not passing init: through to NSObject
 correctly?
In-Reply-To: <7317d7610910052001w3efad883xc1c78d7b957c9553@mail.gmail.com>
References: <D8F21FD3-3C56-41A0-9CCE-D771329DB37B@ryoukai.org>
	<6C77D8CF-BB58-4DB8-85C4-537FA4E0467D@apple.com>
	<7317d7610910052001w3efad883xc1c78d7b957c9553@mail.gmail.com>
Message-ID: <0F7FCAAF-465B-4356-841B-705B5840CD1E@apple.com>

On Oct 5, 2009, at 8:01 PM, Conrad Taylor wrote:
> What should be the exact output?  In Ruby 1.9.1, I see the following  
> output:
>
> $ ruby test.rb
> "A"
> "B"
> "C"
> "D"

[snip]

#init is actually a NSObject thing. MacRuby's default initializer  
calls it.

The mainstream Ruby doesn't, which explains your output.

> Next, will there be an implementation of BasicObject in MacRuby as  
> it is in Ruby 1.9.x?

There is one already (maybe not 100% compatible):

$ macruby -e "p BasicObject"
BasicObject

Laurent

> On Mon, Oct 5, 2009 at 7:45 PM, Laurent Sansonetti <lsansonetti at apple.com 
> > wrote:
> Thanks for the report, I added your snippet in our test suite.
>
> At a glance it looks like an infinite loop in the dispatcher.  
> Definitely a bug :)
>
> Laurent
>
>
> On Oct 5, 2009, at 6:37 PM, Michael Shapiro wrote:
>
> Hi all,
> I searched a few months of the list archives and trac, but wasn't  
> able to find reference to this.
>
> Calling `super` inside of an overridden #init function where no ruby  
> ancestors define #init causes a segmentation fault. If I'm not  
> mistaken, shouldn't the init: message be passed to NSObject?
>
> ---------------------------------------------------------
> class HasInit
> def init
>  super
>  p 'HasInit'
>  self
> end
> end
>
> class A < HasInit; end
>
> class B < A; end
>
> A.new
> p 'A'
> B.new
> p 'B'
>
> class HasNoInit; end
>
> class C < HasNoInit; end
>
> class D < C
> def init
>  super
>  self
> end
> end
>
> C.new
> p 'C'
> D.new
> p 'D'
> ---------------------------------------------------------
>
> You should see the segfault happen when trying to init D, but  
> HasInit passes the message through to NSObject just fine, it seems.
>
> Tested with the 2009-10-05-1158 nightly.
>
> Thanks!
> --Mike
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From cwdinfo at gmail.com  Mon Oct  5 22:33:30 2009
From: cwdinfo at gmail.com (s.ross)
Date: Mon, 5 Oct 2009 22:33:30 -0700
Subject: [MacRuby-devel] trunk status update
In-Reply-To: <98E101C0-0345-46A4-A390-78B1E5874E49@apple.com>
References: <1F1AE689-E1CB-4E33-8350-B889156D37B1@apple.com>
	<BB1585D8-8649-49D5-BC6B-C8D3859AF732@gmail.com>
	<98E101C0-0345-46A4-A390-78B1E5874E49@apple.com>
Message-ID: <D86BD30F-9981-49FD-B577-D69B34BCDD85@gmail.com>

It's way better, but I'm getting this:

[Switching to process 1982]
Running?
2009-10-05 22:29:51.141 IStockCocoa[1982:80f] Error loading /Library/ 
InputManagers/GearsEnabler.old/GearsEnabler.bundle/Contents/MacOS/ 
GearsEnabler:  dlopen(/Library/InputManagers/GearsEnabler.old/ 
GearsEnabler.bundle/Contents/MacOS/GearsEnabler, 265): no suitable  
image found.  Did find:
	/Library/InputManagers/GearsEnabler.old/GearsEnabler.bundle/Contents/ 
MacOS/GearsEnabler: GC capability mismatch
Program received signal:  ?SIGABRT?.
sharedlibrary apply-load-rules all
warning: Could not find object file "/Sites/kain/icoretech.org/macruby/ 
repo/array.o" - no debug information available for "array.c".


The specific code that causes it is:

class TitleController < ControllerBase
   attr_writer :image_title, :word_count, :title_notes

   def awakeFromNib
     @word_count.setStringValue('Words: 0')
     @title_notes.setStringValue 'Duplicates: 0'
   end

   def controlTextDidChange(notification)
     contents = (notification.userInfo 
['NSFieldEditor'].textStorage.string || '').to_s
     unless contents.empty?
       words = contents.empty? ? [] : contents.split(/\W+/).collect{| 
w| w.downcase}
       wc = words.length
       dups = words.length - words.uniq.length

       @word_count.setStringValue("Words: #{wc}")
       @ControllerBase.setTextColor(wc > 10 ? NSColor::redColor :  
NSColor::textColor)
       @title_notes.setStringValue("Duplicates: #{dups}")
       @title_notes.setTextColor(dups > 0 ? NSColor::redColor :  
NSColor::textColor)
     end
   end
end

When a keystroke is entered into the NSTextField, the  
controlTextDidChange delegate should be called. That's when the  
SIGABRT is triggered. I don't know what the deal with Gears is. I'm  
not using Gears but if there's something on my Mac that should be  
cleaned up, perhaps that's what caused the problem.

Again, great progress. This is really exciting to work with.

Steve

On Oct 5, 2009, at 7:47 PM, Laurent Sansonetti wrote:

> Hi,
>
> I fixed several 32-bit bugs, so it should be better. However, the  
> specs don't pass at 100% yet (a notable thing is that ruby  
> exceptions cannot be intercepted by objc).
>
> Feel free to give it a try and let us know if it's better now :)
>
> Laurent
>
> On Oct 5, 2009, at 7:32 PM, s.ross wrote:
>
>> Great progress. I'm pretty sure you would have mentioned it in the  
>> release notes if it were stable, but has there been any progress  
>> making MacRuby work properly on Snow Leopard 32-bit architectures  
>> like the Core Duo? (nag, nag :)
>>
>> Thx
>>
>>
>> On Oct 5, 2009, at 2:34 PM, Laurent Sansonetti wrote:
>>
>>> Another status update, covering about 2 weeks of development.
>>>
>>> Highlights:
>>>
>>> - Early backtracing support.
>>> - Much better AOT compilation. Parts of the standard library are  
>>> now pre-compiled for testing.
>>> - Migrated to LLVM top of tree.
>>> - Dispatcher performance is now back to normal (we lost about 30%  
>>> due to gcc not inlining code).
>>> - Many bug fixes.
>>>
>>> We are content-complete for a first beta release of MacRuby 0.5.   
>>> We will release it very soon then continue converging until the  
>>> final 0.5 release.
>>>
>>> Details:
>>>
>>> - Better GCD documentation
>>> - Implemented Symbol.all_symbols
>>> - Rewrote the file loader (file.c) fixing a few bugs
>>> - Added preliminary support for backtracing / symbolication
>>> - Make sure stdio objects are never finalized
>>> - Fixed more eval/Binding bugs
>>> - Fixed END{} block
>>> - Fixed a memory problem in the libyaml extension
>>> - Fixed rescues in rescues (most cases)
>>> - Fixed a 10.5-only bug in the new Array class
>>> - Fixed a bug of the parser when dealing with byte strings
>>> - AOT: now compiling part of the stdlib (notably irb and rubygems)
>>> - AOT: fixed bugs in the compilation of defined?, undef,  
>>> rb_eStandardError, literal ranges
>>> - Fixed a bug in the compilation of `for' loops
>>> - Fixed many minor compilation bugs discovered by the LLVM module  
>>> verifier
>>> - The arguments resolver is now able to deal with any number of  
>>> arguments
>>> - Fixed minor String bugs
>>> - Added autorelease and dealloc to the list of handled ignored  
>>> selectors
>>> - Fixed a bug when instance variables were not visible from within  
>>> an iterator in method called through KVO
>>> - Fixed an infinite recursion trying to convert an NSPathStore2 to  
>>> a string
>>> - Moved to LLVM r82747, enabled LLVM multithreaded mode
>>> - Fixed GC problems in the parser
>>> - Create all ruby scopes with external linkage, otherwise the AOT  
>>> compiler won't generate frame info for them
>>> - Fixed a bug when open would crash when mode is numeric
>>> - Now using a gcc constructor to initialize .rbo files
>>> - Added Dispatch::Semaphore + fixed a few things
>>> - Make sure RoxorVM instances created lazily have a valid thread  
>>> accessor
>>> - Fixed a random bug of Numeric#chr
>>> - macruby is now SIGINT interruptible (but no exception is raised,  
>>> yet)
>>> - Fixed a few 32-bit only bugs
>>> - Fixed a GC bug in builtin global variable setters
>>> - Fixed a bug in Set#to_a
>>> - Fixed the BridgeSupport parser to properly handle one liner  
>>> <method> elements
>>> - Fixed variadic functions/methods calls
>>> - Fixed a few bugs in Array#pack
>>> - Fixed a serious bug in the way we used to promote strings to  
>>> byte strings
>>> - Fixed a few bugs in IO#ioctl and IO#fcntl
>>> - Now separately compiling the dispatcher and forcing function  
>>> inlining
>>> - Fixed a bug in File.open when file permissions were not taken  
>>> into account
>>> - Make sure ivar slot generation is disabled when compiling attr  
>>> accessors
>>> - Fixed a bug in the way we AOT compile super method cache
>>> - Added an empty Ruby template file
>>> - Improved the MacRuby Application template: Embed MacRuby target  
>>> and some unit testing mechanism are added
>>>
>>> Laurent
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091005/2da96b15/attachment-0001.html>

From vincent.isambart at gmail.com  Mon Oct  5 22:48:57 2009
From: vincent.isambart at gmail.com (Vincent Isambart)
Date: Tue, 6 Oct 2009 14:48:57 +0900
Subject: [MacRuby-devel] trunk status update
In-Reply-To: <D86BD30F-9981-49FD-B577-D69B34BCDD85@gmail.com>
References: <1F1AE689-E1CB-4E33-8350-B889156D37B1@apple.com>
	<BB1585D8-8649-49D5-BC6B-C8D3859AF732@gmail.com>
	<98E101C0-0345-46A4-A390-78B1E5874E49@apple.com>
	<D86BD30F-9981-49FD-B577-D69B34BCDD85@gmail.com>
Message-ID: <7d9a1f530910052248j2275a92ci90c1ffe648d033b9@mail.gmail.com>

> [Switching to process 1982]
> Running?
> 2009-10-05 22:29:51.141 IStockCocoa[1982:80f] Error loading
> /Library/InputManagers/GearsEnabler.old/GearsEnabler.bundle/Contents/MacOS/GearsEnabler:
> dlopen(/Library/InputManagers/GearsEnabler.old/GearsEnabler.bundle/Contents/MacOS/GearsEnabler,
> 265): no suitable image found.? Did find:
> /Library/InputManagers/GearsEnabler.old/GearsEnabler.bundle/Contents/MacOS/GearsEnabler:
> GC capability mismatch
> Program received signal:? ?SIGABRT?.
> sharedlibrary apply-load-rules all
> warning: Could not find object file
> "/Sites/kain/icoretech.org/macruby/repo/array.o" - no debug information
> available for "array.c".

Try moving this stupid GearEnabler Input Manager somewhere else and
restart the app
sudo mv /Library/InputManagers/GearsEnabler.old /tmp
I'm pretty sure you can even delete it (especially as the name ends with .old)

From cwdinfo at gmail.com  Tue Oct  6 07:59:42 2009
From: cwdinfo at gmail.com (s.ross)
Date: Tue, 6 Oct 2009 07:59:42 -0700
Subject: [MacRuby-devel] trunk status update
In-Reply-To: <7d9a1f530910052248j2275a92ci90c1ffe648d033b9@mail.gmail.com>
References: <1F1AE689-E1CB-4E33-8350-B889156D37B1@apple.com>
	<BB1585D8-8649-49D5-BC6B-C8D3859AF732@gmail.com>
	<98E101C0-0345-46A4-A390-78B1E5874E49@apple.com>
	<D86BD30F-9981-49FD-B577-D69B34BCDD85@gmail.com>
	<7d9a1f530910052248j2275a92ci90c1ffe648d033b9@mail.gmail.com>
Message-ID: <728E811C-2A5F-4CF4-90C8-163635F5F30C@gmail.com>

Hello-

On Oct 5, 2009, at 10:48 PM, Vincent Isambart wrote:

>> [Switching to process 1982]
>> Running?
>> 2009-10-05 22:29:51.141 IStockCocoa[1982:80f] Error loading
>> /Library/InputManagers/GearsEnabler.old/GearsEnabler.bundle/ 
>> Contents/MacOS/GearsEnabler:
>> dlopen(/Library/InputManagers/GearsEnabler.old/GearsEnabler.bundle/ 
>> Contents/MacOS/GearsEnabler,
>> 265): no suitable image found.  Did find:
>> /Library/InputManagers/GearsEnabler.old/GearsEnabler.bundle/ 
>> Contents/MacOS/GearsEnabler:
>> GC capability mismatch
>> Program received signal:  ?SIGABRT?.
>> sharedlibrary apply-load-rules all
>> warning: Could not find object file
>> "/Sites/kain/icoretech.org/macruby/repo/array.o" - no debug  
>> information
>> available for "array.c".
>
> Try moving this stupid GearEnabler Input Manager somewhere else and
> restart the app
> sudo mv /Library/InputManagers/GearsEnabler.old /tmp
> I'm pretty sure you can even delete it (especially as the name ends  
> with .old)
> _______________________________________________

I'm pretty sure it's unnecessary as well. I moved it and the Gears  
warning goes away, but the SIGABRT remains. Could it be something  
wrong with my code? :)

From cwdinfo at gmail.com  Tue Oct  6 08:18:43 2009
From: cwdinfo at gmail.com (s.ross)
Date: Tue, 6 Oct 2009 08:18:43 -0700
Subject: [MacRuby-devel] trunk status update
In-Reply-To: <7d9a1f530910052248j2275a92ci90c1ffe648d033b9@mail.gmail.com>
References: <1F1AE689-E1CB-4E33-8350-B889156D37B1@apple.com>
	<BB1585D8-8649-49D5-BC6B-C8D3859AF732@gmail.com>
	<98E101C0-0345-46A4-A390-78B1E5874E49@apple.com>
	<D86BD30F-9981-49FD-B577-D69B34BCDD85@gmail.com>
	<7d9a1f530910052248j2275a92ci90c1ffe648d033b9@mail.gmail.com>
Message-ID: <4D4F0EDE-2649-4641-8EDE-7075AA2F15A5@gmail.com>

Whoa, thanks for the help with the Gears enabler. It didn't relate to  
the problem. It was, as is most often the case, user error on my part.  
Reduced:

class ControllerBase < NSObject
end

class TitleController < ControllerBase
   @ControllerBase.setTextColor(NSColor::redColor) # <= yeah, right.  
Try to invoke a nonexistent, presumably on nil.
end

This tries to invoke a method, presumably on nil, and produces a  
SIGABRT with no backtrace. I'm not sure why a SIGABRT, but incorrect  
program behavior is the expected result of bonehead programmer error  
on my part.

Again, thanks (sheepish grin) for bearing with me in getting this  
errant search/replace goop out of my code. Gee, what a noob error.

Steve


On Oct 5, 2009, at 10:48 PM, Vincent Isambart wrote:

>> [Switching to process 1982]
>> Running?
>> 2009-10-05 22:29:51.141 IStockCocoa[1982:80f] Error loading
>> /Library/InputManagers/GearsEnabler.old/GearsEnabler.bundle/ 
>> Contents/MacOS/GearsEnabler:
>> dlopen(/Library/InputManagers/GearsEnabler.old/GearsEnabler.bundle/ 
>> Contents/MacOS/GearsEnabler,
>> 265): no suitable image found.  Did find:
>> /Library/InputManagers/GearsEnabler.old/GearsEnabler.bundle/ 
>> Contents/MacOS/GearsEnabler:
>> GC capability mismatch
>> Program received signal:  ?SIGABRT?.
>> sharedlibrary apply-load-rules all
>> warning: Could not find object file
>> "/Sites/kain/icoretech.org/macruby/repo/array.o" - no debug  
>> information
>> available for "array.c".
>
> Try moving this stupid GearEnabler Input Manager somewhere else and
> restart the app
> sudo mv /Library/InputManagers/GearsEnabler.old /tmp
> I'm pretty sure you can even delete it (especially as the name ends  
> with .old)
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From mattaimonetti at gmail.com  Tue Oct  6 10:50:37 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Tue, 6 Oct 2009 10:50:37 -0700
Subject: [MacRuby-devel] MacRuby tips
Message-ID: <20fefa50910061050j5257d6b7h359b51327e92940c@mail.gmail.com>

Because Googling for MacRuby issues can still be quite challenging, I
decided to start blogging about small things that might be useful to others.
My first post is about embedding a custom font into your application and
then use it on a text field or somewhere else:

http://merbist.com/2009/10/06/macruby-tips-embed-a-custom-font/

Searching the Cocoa doc and converting the result into MacRuby isn't hard.
However, I am sure that other developers will also try to embed a custom
font into one of their apps, and if a result shows up right away when they
google the problem, their experience will be much better.

Anyway, I hope this series of tips will be helpful, and if you are learning
Cocoa and have a blog, you might also want to share what you've
learned/discovered.

- Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091006/48fd21ee/attachment.html>

From ruby-noreply at macosforge.org  Tue Oct  6 11:36:41 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 06 Oct 2009 18:36:41 -0000
Subject: [MacRuby-devel] [MacRuby] #364: priority queue program crashes
	MacRuby
Message-ID: <054.0603c1304c7461cada1c6fed59280cf0@macosforge.org>

#364: priority queue program crashes MacRuby
-------------------------------------+--------------------------------------
 Reporter:  jordan.breeding@?        |       Owner:  lsansonetti@?        
     Type:  defect                   |      Status:  new                  
 Priority:  blocker                  |   Milestone:  MacRuby 0.5          
Component:  MacRuby                  |    Keywords:                       
-------------------------------------+--------------------------------------
 So, I have been trying to track down a crash in MacRuby for some time. The
 crash is inside of a priority queue program I wrote earlier this year for
 an artificial intelligence class. In MacRuby 0.4 the program was non-
 deterministic but would run. Under MacRuby 0.5 (trunk) it currently
 doesn't run at all, crashing instead.

 crash text:
 {{{
 126 jordan at thetourist ...tificial Intelligence/Assignment No.
 1/priority_queue_bug > ./search.cocoa -m -c a-star
 input_files/input13_7.txt
 uncaught Objective-C/C++ exception...
 terminate called after throwing an instance of
 'RoxorReturnFromBlockException*'
 zsh: abort      ./search.cocoa -m -c a-star input_files/input13_7.txt
 }}}

 The current search.cocoa file will only run under MacRuby, but it could
 probably be made to work on RubyCocoa.

 search.pqueue will work under Ruby 1.8.6 and Ruby 1.9, but crash with the
 same error under MacRuby.

 I originally wanted to narrow this down to a smaller, more management test
 case that could easily be turned into a test for MacRuby's test suite, but
 everything I try works as a small test even though the original larger
 program crashes.

 Since I have had no luck tracking this down for sometime I am just
 uploading it as a bug.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/364>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Tue Oct  6 11:47:27 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Tue, 06 Oct 2009 11:47:27 -0700
Subject: [MacRuby-devel] trunk status update
In-Reply-To: <4D4F0EDE-2649-4641-8EDE-7075AA2F15A5@gmail.com>
References: <1F1AE689-E1CB-4E33-8350-B889156D37B1@apple.com>
	<BB1585D8-8649-49D5-BC6B-C8D3859AF732@gmail.com>
	<98E101C0-0345-46A4-A390-78B1E5874E49@apple.com>
	<D86BD30F-9981-49FD-B577-D69B34BCDD85@gmail.com>
	<7d9a1f530910052248j2275a92ci90c1ffe648d033b9@mail.gmail.com>
	<4D4F0EDE-2649-4641-8EDE-7075AA2F15A5@gmail.com>
Message-ID: <8D6BF013-C506-45B9-9DB7-FAEB25A9AA22@apple.com>

Hi Ross,

The SIGABRT is definitely not intended, there is surely a bug there,  
probably 32-bit only :)

I tried to reproduce it here without success

$ arch -i386 macruby -e "@foo.bar"
-e:in `<main>': undefined method `bar' for nil:NilClass (NoMethodError)

It would be awesome if you could extract the crash to a separate  
project and attach it to a Trac ticket.

Laurent

On Oct 6, 2009, at 8:18 AM, s.ross wrote:

> Whoa, thanks for the help with the Gears enabler. It didn't relate  
> to the problem. It was, as is most often the case, user error on my  
> part. Reduced:
>
> class ControllerBase < NSObject
> end
>
> class TitleController < ControllerBase
>  @ControllerBase.setTextColor(NSColor::redColor) # <= yeah, right.  
> Try to invoke a nonexistent, presumably on nil.
> end
>
> This tries to invoke a method, presumably on nil, and produces a  
> SIGABRT with no backtrace. I'm not sure why a SIGABRT, but incorrect  
> program behavior is the expected result of bonehead programmer error  
> on my part.
>
> Again, thanks (sheepish grin) for bearing with me in getting this  
> errant search/replace goop out of my code. Gee, what a noob error.
>
> Steve
>
>
> On Oct 5, 2009, at 10:48 PM, Vincent Isambart wrote:
>
>>> [Switching to process 1982]
>>> Running?
>>> 2009-10-05 22:29:51.141 IStockCocoa[1982:80f] Error loading
>>> /Library/InputManagers/GearsEnabler.old/GearsEnabler.bundle/ 
>>> Contents/MacOS/GearsEnabler:
>>> dlopen(/Library/InputManagers/GearsEnabler.old/GearsEnabler.bundle/ 
>>> Contents/MacOS/GearsEnabler,
>>> 265): no suitable image found.  Did find:
>>> /Library/InputManagers/GearsEnabler.old/GearsEnabler.bundle/ 
>>> Contents/MacOS/GearsEnabler:
>>> GC capability mismatch
>>> Program received signal:  ?SIGABRT?.
>>> sharedlibrary apply-load-rules all
>>> warning: Could not find object file
>>> "/Sites/kain/icoretech.org/macruby/repo/array.o" - no debug  
>>> information
>>> available for "array.c".
>>
>> Try moving this stupid GearEnabler Input Manager somewhere else and
>> restart the app
>> sudo mv /Library/InputManagers/GearsEnabler.old /tmp
>> I'm pretty sure you can even delete it (especially as the name ends  
>> with .old)
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From lsansonetti at apple.com  Tue Oct  6 11:48:42 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Tue, 06 Oct 2009 11:48:42 -0700
Subject: [MacRuby-devel] MacRuby tips
In-Reply-To: <20fefa50910061050j5257d6b7h359b51327e92940c@mail.gmail.com>
References: <20fefa50910061050j5257d6b7h359b51327e92940c@mail.gmail.com>
Message-ID: <6F71BE17-05A1-46C4-8E7A-438BF8B5A5D0@apple.com>

Very cool Matt!

Maybe we should move these tips to the macruby.org website (as  
"recipes") at one point.

http://www.macruby.org/documentation.html

Laurent

On Oct 6, 2009, at 10:50 AM, Matt Aimonetti wrote:

> Because Googling for MacRuby issues can still be quite challenging,  
> I decided to start blogging about small things that might be useful  
> to others.
> My first post is about embedding a custom font into your application  
> and then use it on a text field or somewhere else:
>
> http://merbist.com/2009/10/06/macruby-tips-embed-a-custom-font/
>
> Searching the Cocoa doc and converting the result into MacRuby isn't  
> hard. However, I am sure that other developers will also try to  
> embed a custom font into one of their apps, and if a result shows up  
> right away when they google the problem, their experience will be  
> much better.
>
> Anyway, I hope this series of tips will be helpful, and if you are  
> learning Cocoa and have a blog, you might also want to share what  
> you've learned/discovered.
>
> - Matt
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From mattaimonetti at gmail.com  Tue Oct  6 11:54:38 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Tue, 6 Oct 2009 11:54:38 -0700
Subject: [MacRuby-devel] MacRuby tips
In-Reply-To: <6F71BE17-05A1-46C4-8E7A-438BF8B5A5D0@apple.com>
References: <20fefa50910061050j5257d6b7h359b51327e92940c@mail.gmail.com>
	<6F71BE17-05A1-46C4-8E7A-438BF8B5A5D0@apple.com>
Message-ID: <20fefa50910061154q667e8575h6e8e3fcec794c2b@mail.gmail.com>

Sounds good, as soon as I have a nice collection, I'll package them in
recipes.
By the way, anyone faced a problem they couldn't solve? Or maybe there is a
specific topic you would like me/someone else to cover?

- Matt

On Tue, Oct 6, 2009 at 11:48 AM, Laurent Sansonetti
<lsansonetti at apple.com>wrote:

> Very cool Matt!
>
> Maybe we should move these tips to the macruby.org website (as "recipes")
> at one point.
>
> http://www.macruby.org/documentation.html
>
> Laurent
>
>
> On Oct 6, 2009, at 10:50 AM, Matt Aimonetti wrote:
>
>  Because Googling for MacRuby issues can still be quite challenging, I
>> decided to start blogging about small things that might be useful to others.
>> My first post is about embedding a custom font into your application and
>> then use it on a text field or somewhere else:
>>
>> http://merbist.com/2009/10/06/macruby-tips-embed-a-custom-font/
>>
>> Searching the Cocoa doc and converting the result into MacRuby isn't hard.
>> However, I am sure that other developers will also try to embed a custom
>> font into one of their apps, and if a result shows up right away when they
>> google the problem, their experience will be much better.
>>
>> Anyway, I hope this series of tips will be helpful, and if you are
>> learning Cocoa and have a blog, you might also want to share what you've
>> learned/discovered.
>>
>> - Matt
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091006/886feae0/attachment-0001.html>

From cwdinfo at gmail.com  Tue Oct  6 11:59:28 2009
From: cwdinfo at gmail.com (s.ross)
Date: Tue, 6 Oct 2009 11:59:28 -0700
Subject: [MacRuby-devel] trunk status update
In-Reply-To: <8D6BF013-C506-45B9-9DB7-FAEB25A9AA22@apple.com>
References: <1F1AE689-E1CB-4E33-8350-B889156D37B1@apple.com>
	<BB1585D8-8649-49D5-BC6B-C8D3859AF732@gmail.com>
	<98E101C0-0345-46A4-A390-78B1E5874E49@apple.com>
	<D86BD30F-9981-49FD-B577-D69B34BCDD85@gmail.com>
	<7d9a1f530910052248j2275a92ci90c1ffe648d033b9@mail.gmail.com>
	<4D4F0EDE-2649-4641-8EDE-7075AA2F15A5@gmail.com>
	<8D6BF013-C506-45B9-9DB7-FAEB25A9AA22@apple.com>
Message-ID: <D53BF173-D06B-4432-9A66-ABB93DDC547C@gmail.com>

I'll try when I'm on the ground :)

Hunted and pecked from my iPhone

On Oct 6, 2009, at 11:47 AM, Laurent Sansonetti  
<lsansonetti at apple.com> wrote:

> Hi Ross,
>
> The SIGABRT is definitely not intended, there is surely a bug there,  
> probably 32-bit only :)
>
> I tried to reproduce it here without success
>
> $ arch -i386 macruby -e "@foo.bar"
> -e:in `<main>': undefined method `bar' for nil:NilClass  
> (NoMethodError)
>
> It would be awesome if you could extract the crash to a separate  
> project and attach it to a Trac ticket.
>
> Laurent
>
> On Oct 6, 2009, at 8:18 AM, s.ross wrote:
>
>> Whoa, thanks for the help with the Gears enabler. It didn't relate  
>> to the problem. It was, as is most often the case, user error on my  
>> part. Reduced:
>>
>> class ControllerBase < NSObject
>> end
>>
>> class TitleController < ControllerBase
>> @ControllerBase.setTextColor(NSColor::redColor) # <= yeah, right.  
>> Try to invoke a nonexistent, presumably on nil.
>> end
>>
>> This tries to invoke a method, presumably on nil, and produces a  
>> SIGABRT with no backtrace. I'm not sure why a SIGABRT, but  
>> incorrect program behavior is the expected result of bonehead  
>> programmer error on my part.
>>
>> Again, thanks (sheepish grin) for bearing with me in getting this  
>> errant search/replace goop out of my code. Gee, what a noob error.
>>
>> Steve
>>
>>
>> On Oct 5, 2009, at 10:48 PM, Vincent Isambart wrote:
>>
>>>> [Switching to process 1982]
>>>> Running?
>>>> 2009-10-05 22:29:51.141 IStockCocoa[1982:80f] Error loading
>>>> /Library/InputManagers/GearsEnabler.old/GearsEnabler.bundle/ 
>>>> Contents/MacOS/GearsEnabler:
>>>> dlopen(/Library/InputManagers/GearsEnabler.old/ 
>>>> GearsEnabler.bundle/Contents/MacOS/GearsEnabler,
>>>> 265): no suitable image found.  Did find:
>>>> /Library/InputManagers/GearsEnabler.old/GearsEnabler.bundle/ 
>>>> Contents/MacOS/GearsEnabler:
>>>> GC capability mismatch
>>>> Program received signal:  ?SIGABRT?.
>>>> sharedlibrary apply-load-rules all
>>>> warning: Could not find object file
>>>> "/Sites/kain/icoretech.org/macruby/repo/array.o" - no debug  
>>>> information
>>>> available for "array.c".
>>>
>>> Try moving this stupid GearEnabler Input Manager somewhere else and
>>> restart the app
>>> sudo mv /Library/InputManagers/GearsEnabler.old /tmp
>>> I'm pretty sure you can even delete it (especially as the name  
>>> ends with .old)
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

From nexneo at me.com  Tue Oct  6 11:59:52 2009
From: nexneo at me.com (Niket Patel)
Date: Wed, 07 Oct 2009 00:29:52 +0530
Subject: [MacRuby-devel] MacRuby tips
In-Reply-To: <20fefa50910061154q667e8575h6e8e3fcec794c2b@mail.gmail.com>
References: <20fefa50910061050j5257d6b7h359b51327e92940c@mail.gmail.com>
	<6F71BE17-05A1-46C4-8E7A-438BF8B5A5D0@apple.com>
	<20fefa50910061154q667e8575h6e8e3fcec794c2b@mail.gmail.com>
Message-ID: <9109B616-D109-409F-B186-3DFD89A26545@me.com>


On Oct 7, 2009, at 12:24 AM, Matt Aimonetti wrote:

> By the way, anyone faced a problem they couldn't solve? Or maybe  
> there is a specific topic you would like me/someone else to cover?

Compiling MacRuby was lot harder when last I checked. :-)  Specially  
on 32 bit leopard. Then I give up.
Waiting for Binary Release.


From mattaimonetti at gmail.com  Tue Oct  6 12:25:50 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Tue, 6 Oct 2009 12:25:50 -0700
Subject: [MacRuby-devel] MacRuby tips
In-Reply-To: <9109B616-D109-409F-B186-3DFD89A26545@me.com>
References: <20fefa50910061050j5257d6b7h359b51327e92940c@mail.gmail.com>
	<6F71BE17-05A1-46C4-8E7A-438BF8B5A5D0@apple.com>
	<20fefa50910061154q667e8575h6e8e3fcec794c2b@mail.gmail.com>
	<9109B616-D109-409F-B186-3DFD89A26545@me.com>
Message-ID: <20fefa50910061225h43ad63d7iab3da14a8dbbe7a4@mail.gmail.com>

That's why we provide you with nightly builds:
http://www.macruby.org/downloads.html :)
While this is indeed something a bit challenging, most developers shouldn't
have to do it and therefore I don't think a recipe is really needed. (you
basically just have to follow the readme).

Anything else anyone encountered?

I'll probably post something about streaming sound and also few tricks I
discovered when using xcode for ruby code.

- Matt


On Tue, Oct 6, 2009 at 11:59 AM, Niket Patel <nexneo at me.com> wrote:

>
> On Oct 7, 2009, at 12:24 AM, Matt Aimonetti wrote:
>
>  By the way, anyone faced a problem they couldn't solve? Or maybe there is
>> a specific topic you would like me/someone else to cover?
>>
>
> Compiling MacRuby was lot harder when last I checked. :-)  Specially on 32
> bit leopard. Then I give up.
> Waiting for Binary Release.
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091006/2f1ac37a/attachment.html>

From joshua.ballanco at apple.com  Tue Oct  6 12:33:04 2009
From: joshua.ballanco at apple.com (Josh Ballanco)
Date: Tue, 6 Oct 2009 12:33:04 -0700
Subject: [MacRuby-devel] MacRuby tips
In-Reply-To: <20fefa50910061225h43ad63d7iab3da14a8dbbe7a4@mail.gmail.com>
References: <20fefa50910061050j5257d6b7h359b51327e92940c@mail.gmail.com>
	<6F71BE17-05A1-46C4-8E7A-438BF8B5A5D0@apple.com>
	<20fefa50910061154q667e8575h6e8e3fcec794c2b@mail.gmail.com>
	<9109B616-D109-409F-B186-3DFD89A26545@me.com>
	<20fefa50910061225h43ad63d7iab3da14a8dbbe7a4@mail.gmail.com>
Message-ID: <CD27A27B-4A90-4071-8783-68B1AF84ED07@apple.com>

Hey Matt,

Something I'm working on is writing a Framework in Xcode, and using  
MacRuby to test it. I'm running into some issues that I'm trying to  
chase down (segfaults with bacon when loading frameworks), but there  
were enough gottchas that I think this would make for a good little  
recipe. Let me know what you think, and maybe we can put something  
together.

Cheers,

Josh


On Oct 6, 2009, at 12:25 PM, Matt Aimonetti wrote:

> That's why we provide you with nightly builds: http://www.macruby.org/downloads.html 
>  :)
> While this is indeed something a bit challenging, most developers  
> shouldn't have to do it and therefore I don't think a recipe is  
> really needed. (you basically just have to follow the readme).
>
> Anything else anyone encountered?
>
> I'll probably post something about streaming sound and also few  
> tricks I discovered when using xcode for ruby code.
>
> - Matt
>
>
> On Tue, Oct 6, 2009 at 11:59 AM, Niket Patel <nexneo at me.com> wrote:
>
> On Oct 7, 2009, at 12:24 AM, Matt Aimonetti wrote:
>
> By the way, anyone faced a problem they couldn't solve? Or maybe  
> there is a specific topic you would like me/someone else to cover?
>
> Compiling MacRuby was lot harder when last I checked. :-)  Specially  
> on 32 bit leopard. Then I give up.
> Waiting for Binary Release.
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091006/1e901546/attachment.html>

From nexneo at me.com  Tue Oct  6 12:42:07 2009
From: nexneo at me.com (Niket Patel)
Date: Wed, 07 Oct 2009 01:12:07 +0530
Subject: [MacRuby-devel] MacRuby tips
In-Reply-To: <20fefa50910061225h43ad63d7iab3da14a8dbbe7a4@mail.gmail.com>
References: <20fefa50910061050j5257d6b7h359b51327e92940c@mail.gmail.com>
	<6F71BE17-05A1-46C4-8E7A-438BF8B5A5D0@apple.com>
	<20fefa50910061154q667e8575h6e8e3fcec794c2b@mail.gmail.com>
	<9109B616-D109-409F-B186-3DFD89A26545@me.com>
	<20fefa50910061225h43ad63d7iab3da14a8dbbe7a4@mail.gmail.com>
Message-ID: <78AB21B5-5801-4BDC-A1AA-FE48AB40CC94@me.com>

Thanks, But build for snow leopard only. I'm still on Leopard.
I'm not saying recipe is needed for this topic, just mentioning it is  
really hard and unpredictable on 32 bit system. Mainly because most  
developers working on 64 bit snow leopard.

Btw, Blogging on small stuffs that can help to understand tricky areas  
is really great.

On Oct 7, 2009, at 12:55 AM, Matt Aimonetti wrote:

> That's why we provide you with nightly builds: http://www.macruby.org/downloads.html 
>  :)
> While this is indeed something a bit challenging, most developers  
> shouldn't have to do it and therefore I don't think a recipe is  
> really needed. (you basically just have to follow the readme).
>
>
> On Tue, Oct 6, 2009 at 11:59 AM, Niket Patel <nexneo at me.com> wrote:
>
> Compiling MacRuby was lot harder when last I checked. :-)  Specially  
> on 32 bit leopard. Then I give up.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091007/90c414c0/attachment.html>

From parzival at mindspring.com  Tue Oct  6 12:58:05 2009
From: parzival at mindspring.com (Michael Winterstein)
Date: Tue, 6 Oct 2009 12:58:05 -0700
Subject: [MacRuby-devel] Problems with return code from sheet (possible
	regression)
Message-ID: <95F6FAED-DEFE-433E-AE90-188759F372CF@mindspring.com>

I seem to have run into nearly the same problem that I had a while  
back, in this ticket:
http://www.macruby.org/trac/ticket/221

I haven't filed it yet this time since last time it turned out to be  
already fixed, but I'm not certain that's the case now.  At any rate,  
it's being handled by different functions.
The same thing is happening - the return code being passed to my  
delegate (from [NSApplication endSheet:returnCode]) isn't being  
treated as the NSInteger it ought to be.  At least I think so.  Here's  
the trace, and you can see that the value 1(NSOKButton) is being  
treated as id, causing problems (0/NSCancelButton doesn't crash as  
it's a special case) :

Program received signal:  ?EXC_BAD_ACCESS?.
(gdb) bt
#0  rb_ocid_to_rval [inlined] () at /Users/parzival/devo/buried/ 
MacRuby/trunk/include/ruby/ruby.h:1252
#1  0x0000000100130161 in rb_vm_ocval_to_rval (ocval=0x1) at  
compiler.cpp:6155
#2  0x000000010110537c in ?? ()
#3  0x00007fff820c29f9 in -[NSApplication endSheet:returnCode:] ()
#4  0x00007fff81fd523e in -[NSApplication sendAction:to:from:] ()
#5  0x00007fff81fd519d in -[NSControl sendAction:to:] ()
#6  0x00007fff8206068b in -[NSCell  
trackMouse:inRect:ofView:untilMouseUp:] ()
#7  0x00007fff820911a3 in -[NSButtonCell  
trackMouse:inRect:ofView:untilMouseUp:] ()
#8  0x00007fff8205f135 in -[NSControl mouseDown:] ()
#9  0x00007fff81f79967 in -[NSWindow sendEvent:] ()
#10 0x00007fff81eaf122 in -[NSApplication sendEvent:] ()
#11 0x00007fff81e45acc in -[NSApplication run] ()
#12 0x00007fff81e3e798 in NSApplicationMain ()

Attached are a few files as a test case, an NSWindowController  
subclass and MainMenu.nib that can be dropped into a  new project to  
check this if anyone wants to.  I recall when I first had this problem  
that I could see what the change was, but unfortunately I've forgotten  
that now.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091006/d489c051/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Testfiles.zip
Type: application/zip
Size: 23589 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091006/d489c051/attachment-0001.zip>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091006/d489c051/attachment-0003.html>

From mattaimonetti at gmail.com  Tue Oct  6 13:25:23 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Tue, 6 Oct 2009 13:25:23 -0700
Subject: [MacRuby-devel] MacRuby tips
In-Reply-To: <78AB21B5-5801-4BDC-A1AA-FE48AB40CC94@me.com>
References: <20fefa50910061050j5257d6b7h359b51327e92940c@mail.gmail.com>
	<6F71BE17-05A1-46C4-8E7A-438BF8B5A5D0@apple.com>
	<20fefa50910061154q667e8575h6e8e3fcec794c2b@mail.gmail.com>
	<9109B616-D109-409F-B186-3DFD89A26545@me.com>
	<20fefa50910061225h43ad63d7iab3da14a8dbbe7a4@mail.gmail.com>
	<78AB21B5-5801-4BDC-A1AA-FE48AB40CC94@me.com>
Message-ID: <9BB2EA26-85B6-443C-B190-367909B10796@gmail.com>

Very good point about Leopard. Maybe Vincent can shine in since he's  
still on Leopard.

My guess is that the beta/rc1 will be built for leopard/snow leopard.  
What kind of problems did you have while trying to build from trunk?

FYI, Instead if doing a LLVM svn update, It turned out easier to just  
checkout a new version of the repo.

- Matt

Sent from my iPhone

On Oct 6, 2009, at 12:42, Niket Patel <nexneo at me.com> wrote:

> Thanks, But build for snow leopard only. I'm still on Leopard.
> I'm not saying recipe is needed for this topic, just mentioning it  
> is really hard and unpredictable on 32 bit system. Mainly because  
> most developers working on 64 bit snow leopard.
>
> Btw, Blogging on small stuffs that can help to understand tricky  
> areas is really great.
>
> On Oct 7, 2009, at 12:55 AM, Matt Aimonetti wrote:
>
>> That's why we provide you with nightly builds: http://www.macruby.org/downloads.html 
>>  :)
>> While this is indeed something a bit challenging, most developers  
>> shouldn't have to do it and therefore I don't think a recipe is  
>> really needed. (you basically just have to follow the readme).
>>
>>
>> On Tue, Oct 6, 2009 at 11:59 AM, Niket Patel <nexneo at me.com> wrote:
>>
>> Compiling MacRuby was lot harder when last I checked. :-)   
>> Specially on 32 bit leopard. Then I give up.
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091006/f7f865b7/attachment.html>

From lsansonetti at apple.com  Tue Oct  6 13:28:39 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Tue, 06 Oct 2009 13:28:39 -0700
Subject: [MacRuby-devel] Problems with return code from sheet (possible
 regression)
In-Reply-To: <95F6FAED-DEFE-433E-AE90-188759F372CF@mindspring.com>
References: <95F6FAED-DEFE-433E-AE90-188759F372CF@mindspring.com>
Message-ID: <25EE3080-B429-4DF2-A7A7-28FA5090DD44@apple.com>

Hi Michael,

It's actually a well-known bug. MacRuby trunk doesn't honor the  
sel_of_type BridgeSupport attribute, therefore your sheet callback is  
registered to the runtime with the default signature (where all  
arguments and return value are Objective-C objects), and later it  
fails to convert the returnCode argument (in this backtrace, 0x1) as  
an Objective-C object.

Laurent

On Oct 6, 2009, at 12:58 PM, Michael Winterstein wrote:

> I seem to have run into nearly the same problem that I had a while  
> back, in this ticket:
> http://www.macruby.org/trac/ticket/221
>
> I haven't filed it yet this time since last time it turned out to be  
> already fixed, but I'm not certain that's the case now.  At any  
> rate, it's being handled by different functions.
> The same thing is happening - the return code being passed to my  
> delegate (from [NSApplication endSheet:returnCode]) isn't being  
> treated as the NSInteger it ought to be.  At least I think so.   
> Here's the trace, and you can see that the value 1(NSOKButton) is  
> being treated as id, causing problems (0/NSCancelButton doesn't  
> crash as it's a special case) :
>
> Program received signal:  ?EXC_BAD_ACCESS?.
> (gdb) bt
> #0  rb_ocid_to_rval [inlined] () at /Users/parzival/devo/buried/ 
> MacRuby/trunk/include/ruby/ruby.h:1252
> #1  0x0000000100130161 in rb_vm_ocval_to_rval (ocval=0x1) at  
> compiler.cpp:6155
> #2  0x000000010110537c in ?? ()
> #3  0x00007fff820c29f9 in -[NSApplication endSheet:returnCode:] ()
> #4  0x00007fff81fd523e in -[NSApplication sendAction:to:from:] ()
> #5  0x00007fff81fd519d in -[NSControl sendAction:to:] ()
> #6  0x00007fff8206068b in -[NSCell  
> trackMouse:inRect:ofView:untilMouseUp:] ()
> #7  0x00007fff820911a3 in -[NSButtonCell  
> trackMouse:inRect:ofView:untilMouseUp:] ()
> #8  0x00007fff8205f135 in -[NSControl mouseDown:] ()
> #9  0x00007fff81f79967 in -[NSWindow sendEvent:] ()
> #10 0x00007fff81eaf122 in -[NSApplication sendEvent:] ()
> #11 0x00007fff81e45acc in -[NSApplication run] ()
> #12 0x00007fff81e3e798 in NSApplicationMain ()
>
> Attached are a few files as a test case, an NSWindowController  
> subclass and MainMenu.nib that can be dropped into a  new project to  
> check this if anyone wants to.  I recall when I first had this  
> problem that I could see what the change was, but unfortunately I've  
> forgotten that now.
> <Testfiles.zip>
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From mail2lf at gmail.com  Tue Oct  6 13:28:40 2009
From: mail2lf at gmail.com (=?ISO-8859-5?B?sN3i3t0gtuPg0NLh2vbZ?=)
Date: Tue, 6 Oct 2009 23:28:40 +0300
Subject: [MacRuby-devel]  MacRuby on iPhone
Message-ID: <2FDBD102-0F4B-4D08-9861-77384CD3AE97@gmail.com>

Hi all,

I know most of you are 100% pissed off by this topic, but does anybody  
work on porting MacRuby to iPhone?
What are main issues around that (if any)? And do we have a chance to  
be alive when it finally gets there?

I'm personaly very excited by Ruby in general and MacRuby in  
particular, so would like to help if I can.

Best,
Anton

From lsansonetti at apple.com  Tue Oct  6 13:37:38 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Tue, 06 Oct 2009 13:37:38 -0700
Subject: [MacRuby-devel] MacRuby on iPhone
In-Reply-To: <2FDBD102-0F4B-4D08-9861-77384CD3AE97@gmail.com>
References: <2FDBD102-0F4B-4D08-9861-77384CD3AE97@gmail.com>
Message-ID: <001AFF70-AE6F-40B4-8CA4-FC9135D35510@apple.com>

Hi Anton,

It's more complicated than that. It's basically a 2 goals target:

1) finishing the AOT compiler
2) emulating garbage collection

I work on 1) heavily. AFAIK nobody started working on 2).

The project is free software by the way, so anyone can hack on the  
source code. If you won't want to die before it gets there, it's  
probably the best solution.

Laurent

On Oct 6, 2009, at 1:28 PM, ????? ????????? wrote:

> Hi all,
>
> I know most of you are 100% pissed off by this topic, but does  
> anybody work on porting MacRuby to iPhone?
> What are main issues around that (if any)? And do we have a chance  
> to be alive when it finally gets there?
>
> I'm personaly very excited by Ruby in general and MacRuby in  
> particular, so would like to help if I can.
>
> Best,
> Anton
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From mail2lf at gmail.com  Tue Oct  6 13:42:37 2009
From: mail2lf at gmail.com (=?ISO-8859-5?B?sN3i3t0gtuPg0NLh2vbZ?=)
Date: Tue, 6 Oct 2009 23:42:37 +0300
Subject: [MacRuby-devel] MacRuby on iPhone
In-Reply-To: <001AFF70-AE6F-40B4-8CA4-FC9135D35510@apple.com>
References: <2FDBD102-0F4B-4D08-9861-77384CD3AE97@gmail.com>
	<001AFF70-AE6F-40B4-8CA4-FC9135D35510@apple.com>
Message-ID: <2EB020AE-0B2A-451A-A8FC-AC069498F2D9@gmail.com>

Hi Laurent,

So I believe I will at least try to work out something re 2). The only  
issue that might emerge is that even if I end up with something  
working, it would be great to be checked by somebody as I'm not a  
proficient C developer (however, I wrote some stuff in C, C++ and  
Objective-C).

Also, may I count on any hints from the community in case I have been  
stuck with something?

Best,
Anton

06.10.2009, ? 23:37, Laurent Sansonetti ???????(?):

> Hi Anton,
>
> It's more complicated than that. It's basically a 2 goals target:
>
> 1) finishing the AOT compiler
> 2) emulating garbage collection
>
> I work on 1) heavily. AFAIK nobody started working on 2).
>
> The project is free software by the way, so anyone can hack on the  
> source code. If you won't want to die before it gets there, it's  
> probably the best solution.
>
> Laurent
>
> On Oct 6, 2009, at 1:28 PM, ????? ????????? wrote:
>
>> Hi all,
>>
>> I know most of you are 100% pissed off by this topic, but does  
>> anybody work on porting MacRuby to iPhone?
>> What are main issues around that (if any)? And do we have a chance  
>> to be alive when it finally gets there?
>>
>> I'm personaly very excited by Ruby in general and MacRuby in  
>> particular, so would like to help if I can.
>>
>> Best,
>> Anton
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From jordan.breeding at me.com  Tue Oct  6 13:43:47 2009
From: jordan.breeding at me.com (Jordan Breeding)
Date: Tue, 06 Oct 2009 15:43:47 -0500
Subject: [MacRuby-devel] BridgeSupport Question
Message-ID: <554FD285-4537-4A63-A949-E33BA7FAE642@me.com>

I have a question about whether I am seeing a bug in BridgeSupport or  
not.

I am running Mac OS X 10.6.1 and have a custom framework that has some  
categories for Foundation/Cocoa classes.

The following are the problem I noticed when using gen_bridge_metadata:

1) I have to include Cocoa/Cocoa.h in the files, Foundation/ 
Foundation.h doesn't seem to work even though those are really the  
only classes I am dealing with.

2) This is the bigger one, gen_bridge_metadata isn't picking up all of  
the methods/messages from my header, here is one of the headers:

=====
#import <Cocoa/Cocoa.h>

@interface NSArray (JBBAdditions)

#pragma mark Instance Methods

- (NSArray *)jbb_dictionariesWithKey:(NSString *)keyName;
- (id)jbb_firstObject;
- (BOOL)jbb_isEmpty;
@end
=====

but here is the relevant section of the .bridgesupport file:

=====
<class name='NSArray'>
<method selector='jbb_isEmpty'>
<retval type='B'/>
</method>
</class>
=====

Any ideas as to why it is behaving this way? It is doing this for all  
of the classes I have defined categories on (only defining one method/ 
message).

Thanks for any input,
Jordan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3820 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091006/cf90ec33/attachment-0001.bin>

From lsansonetti at apple.com  Tue Oct  6 13:49:59 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Tue, 06 Oct 2009 13:49:59 -0700
Subject: [MacRuby-devel] MacRuby on iPhone
In-Reply-To: <2EB020AE-0B2A-451A-A8FC-AC069498F2D9@gmail.com>
References: <2FDBD102-0F4B-4D08-9861-77384CD3AE97@gmail.com>
	<001AFF70-AE6F-40B4-8CA4-FC9135D35510@apple.com>
	<2EB020AE-0B2A-451A-A8FC-AC069498F2D9@gmail.com>
Message-ID: <6AFB73F9-77ED-41BB-962F-F33B1ABFF245@apple.com>

Hi Anton,

Great! So, since autozone doesn't exist on the iPhone, we must emulate  
it. First, we make sure all memory allocations are done from the  
default malloc zone. Second, we need to appropriately retain/release/ 
autorelease Objective-C objects (as an example, if an object becomes  
an instance variable, it has to be retained). Third, we need to  
programmatically compile autorelease pools.

This isn't an easy task but we can work together on this. Of course  
feel free to ping us if you have any question.

Laurent

On Oct 6, 2009, at 1:42 PM, ????? ????????? wrote:

> Hi Laurent,
>
> So I believe I will at least try to work out something re 2). The  
> only issue that might emerge is that even if I end up with something  
> working, it would be great to be checked by somebody as I'm not a  
> proficient C developer (however, I wrote some stuff in C, C++ and  
> Objective-C).
>
> Also, may I count on any hints from the community in case I have  
> been stuck with something?
>
> Best,
> Anton
>
> 06.10.2009, ? 23:37, Laurent Sansonetti ???????(?):
>
>> Hi Anton,
>>
>> It's more complicated than that. It's basically a 2 goals target:
>>
>> 1) finishing the AOT compiler
>> 2) emulating garbage collection
>>
>> I work on 1) heavily. AFAIK nobody started working on 2).
>>
>> The project is free software by the way, so anyone can hack on the  
>> source code. If you won't want to die before it gets there, it's  
>> probably the best solution.
>>
>> Laurent
>>
>> On Oct 6, 2009, at 1:28 PM, ????? ????????? wrote:
>>
>>> Hi all,
>>>
>>> I know most of you are 100% pissed off by this topic, but does  
>>> anybody work on porting MacRuby to iPhone?
>>> What are main issues around that (if any)? And do we have a chance  
>>> to be alive when it finally gets there?
>>>
>>> I'm personaly very excited by Ruby in general and MacRuby in  
>>> particular, so would like to help if I can.
>>>
>>> Best,
>>> Anton
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From lsansonetti at apple.com  Tue Oct  6 13:50:55 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Tue, 06 Oct 2009 13:50:55 -0700
Subject: [MacRuby-devel] BridgeSupport Question
In-Reply-To: <554FD285-4537-4A63-A949-E33BA7FAE642@me.com>
References: <554FD285-4537-4A63-A949-E33BA7FAE642@me.com>
Message-ID: <380B69C9-61A3-46B9-97F2-E704E4655E78@apple.com>

Hi Jordan,

You should submit BridgeSupport problems to:

http://bugreporter.apple.com/

The developer will deal with them there.

Laurent

On Oct 6, 2009, at 1:43 PM, Jordan Breeding wrote:

> I have a question about whether I am seeing a bug in BridgeSupport  
> or not.
>
> I am running Mac OS X 10.6.1 and have a custom framework that has  
> some categories for Foundation/Cocoa classes.
>
> The following are the problem I noticed when using  
> gen_bridge_metadata:
>
> 1) I have to include Cocoa/Cocoa.h in the files, Foundation/ 
> Foundation.h doesn't seem to work even though those are really the  
> only classes I am dealing with.
>
> 2) This is the bigger one, gen_bridge_metadata isn't picking up all  
> of the methods/messages from my header, here is one of the headers:
>
> =====
> #import <Cocoa/Cocoa.h>
>
> @interface NSArray (JBBAdditions)
>
> #pragma mark Instance Methods
>
> - (NSArray *)jbb_dictionariesWithKey:(NSString *)keyName;
> - (id)jbb_firstObject;
> - (BOOL)jbb_isEmpty;
> @end
> =====
>
> but here is the relevant section of the .bridgesupport file:
>
> =====
> <class name='NSArray'>
> <method selector='jbb_isEmpty'>
> <retval type='B'/>
> </method>
> </class>
> =====
>
> Any ideas as to why it is behaving this way? It is doing this for  
> all of the classes I have defined categories on (only defining one  
> method/message).
>
> Thanks for any input,
> Jordan
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From jordan.breeding at me.com  Tue Oct  6 13:54:02 2009
From: jordan.breeding at me.com (Jordan Breeding)
Date: Tue, 06 Oct 2009 15:54:02 -0500
Subject: [MacRuby-devel] BridgeSupport Question
In-Reply-To: <380B69C9-61A3-46B9-97F2-E704E4655E78@apple.com>
References: <554FD285-4537-4A63-A949-E33BA7FAE642@me.com>
	<380B69C9-61A3-46B9-97F2-E704E4655E78@apple.com>
Message-ID: <D6C9A567-F206-4741-B740-52A1E3BD7462@me.com>

So does it sound like a legitimate problem?

I just didn't want to take up my time and developer time at Apple if I  
was just doing something stupid.

I ran it like this: "gen_bridge_metadata -f ./JBBAdditions.framework - 
F final --64-bit -o ./JBBAdditions.framework/Resources/BridgeSupport/ 
JBBAdditions.bridgesupport"

As long as you don't see any reason that shouldn't have worked I will  
file a bug.

Jordan

On Oct 06, 2009, at 15:50, Laurent Sansonetti wrote:

> Hi Jordan,
>
> You should submit BridgeSupport problems to:
>
> http://bugreporter.apple.com/
>
> The developer will deal with them there.
>
> Laurent
>
> On Oct 6, 2009, at 1:43 PM, Jordan Breeding wrote:
>
>> I have a question about whether I am seeing a bug in BridgeSupport  
>> or not.
>>
>> I am running Mac OS X 10.6.1 and have a custom framework that has  
>> some categories for Foundation/Cocoa classes.
>>
>> The following are the problem I noticed when using  
>> gen_bridge_metadata:
>>
>> 1) I have to include Cocoa/Cocoa.h in the files, Foundation/ 
>> Foundation.h doesn't seem to work even though those are really the  
>> only classes I am dealing with.
>>
>> 2) This is the bigger one, gen_bridge_metadata isn't picking up all  
>> of the methods/messages from my header, here is one of the headers:
>>
>> =====
>> #import <Cocoa/Cocoa.h>
>>
>> @interface NSArray (JBBAdditions)
>>
>> #pragma mark Instance Methods
>>
>> - (NSArray *)jbb_dictionariesWithKey:(NSString *)keyName;
>> - (id)jbb_firstObject;
>> - (BOOL)jbb_isEmpty;
>> @end
>> =====
>>
>> but here is the relevant section of the .bridgesupport file:
>>
>> =====
>> <class name='NSArray'>
>> <method selector='jbb_isEmpty'>
>> <retval type='B'/>
>> </method>
>> </class>
>> =====
>>
>> Any ideas as to why it is behaving this way? It is doing this for  
>> all of the classes I have defined categories on (only defining one  
>> method/message).
>>
>> Thanks for any input,
>> Jordan
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3820 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091006/93a6843c/attachment.bin>

From mail2lf at gmail.com  Tue Oct  6 13:55:32 2009
From: mail2lf at gmail.com (=?ISO-8859-5?B?sN3i3t0gtuPg0NLh2vbZ?=)
Date: Tue, 6 Oct 2009 23:55:32 +0300
Subject: [MacRuby-devel] MacRuby on iPhone
In-Reply-To: <6AFB73F9-77ED-41BB-962F-F33B1ABFF245@apple.com>
References: <2FDBD102-0F4B-4D08-9861-77384CD3AE97@gmail.com>
	<001AFF70-AE6F-40B4-8CA4-FC9135D35510@apple.com>
	<2EB020AE-0B2A-451A-A8FC-AC069498F2D9@gmail.com>
	<6AFB73F9-77ED-41BB-962F-F33B1ABFF245@apple.com>
Message-ID: <D13F968E-C947-4DC4-9DEB-2862D94CD33B@gmail.com>

Hi Laurent,

Wow, thanks, you gave me a fair amount of directions ? many thanks. I  
will start digging into it and let you know as I advance.

I will start with malloc then. Re retain/release ? this seems to be a  
good and quite straightforward approach, but I believe there will be  
issues like circular dependencies (A -> B, B -> A => never released  
once isolated from roots), so there are quite a few problems to think  
about.

Thanks for help, will contact you soon.

Regards,
Anton

06.10.2009, ? 23:49, Laurent Sansonetti ???????(?):

> Hi Anton,
>
> Great! So, since autozone doesn't exist on the iPhone, we must  
> emulate it. First, we make sure all memory allocations are done from  
> the default malloc zone. Second, we need to appropriately retain/ 
> release/autorelease Objective-C objects (as an example, if an object  
> becomes an instance variable, it has to be retained). Third, we need  
> to programmatically compile autorelease pools.
>
> This isn't an easy task but we can work together on this. Of course  
> feel free to ping us if you have any question.
>
> Laurent
>
> On Oct 6, 2009, at 1:42 PM, ????? ????????? wrote:
>
>> Hi Laurent,
>>
>> So I believe I will at least try to work out something re 2). The  
>> only issue that might emerge is that even if I end up with  
>> something working, it would be great to be checked by somebody as  
>> I'm not a proficient C developer (however, I wrote some stuff in C,  
>> C++ and Objective-C).
>>
>> Also, may I count on any hints from the community in case I have  
>> been stuck with something?
>>
>> Best,
>> Anton
>>
>> 06.10.2009, ? 23:37, Laurent Sansonetti ???????(?):
>>
>>> Hi Anton,
>>>
>>> It's more complicated than that. It's basically a 2 goals target:
>>>
>>> 1) finishing the AOT compiler
>>> 2) emulating garbage collection
>>>
>>> I work on 1) heavily. AFAIK nobody started working on 2).
>>>
>>> The project is free software by the way, so anyone can hack on the  
>>> source code. If you won't want to die before it gets there, it's  
>>> probably the best solution.
>>>
>>> Laurent
>>>
>>> On Oct 6, 2009, at 1:28 PM, ????? ????????? wrote:
>>>
>>>> Hi all,
>>>>
>>>> I know most of you are 100% pissed off by this topic, but does  
>>>> anybody work on porting MacRuby to iPhone?
>>>> What are main issues around that (if any)? And do we have a  
>>>> chance to be alive when it finally gets there?
>>>>
>>>> I'm personaly very excited by Ruby in general and MacRuby in  
>>>> particular, so would like to help if I can.
>>>>
>>>> Best,
>>>> Anton
>>>> _______________________________________________
>>>> MacRuby-devel mailing list
>>>> MacRuby-devel at lists.macosforge.org
>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From lsansonetti at apple.com  Tue Oct  6 14:05:07 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Tue, 06 Oct 2009 14:05:07 -0700
Subject: [MacRuby-devel] BridgeSupport Question
In-Reply-To: <D6C9A567-F206-4741-B740-52A1E3BD7462@me.com>
References: <554FD285-4537-4A63-A949-E33BA7FAE642@me.com>
	<380B69C9-61A3-46B9-97F2-E704E4655E78@apple.com>
	<D6C9A567-F206-4741-B740-52A1E3BD7462@me.com>
Message-ID: <3E900DF2-B7F9-4A91-81C4-88FFCF64BE41@apple.com>

Hi Jordan,

I don't know for 1), but you should probably pass -c "-framework Cocoa".

For 2) it's totally expected, the file only contains non- 
introspectable APIs. It lists -jbb_isEmpty because the method returns  
BOOL which needs to be annotated because it shares the same runtime  
encoding as unsigned char. The other methods can be handled at runtime.

Read the BridgeSupport(5) man page for more information.

Laurent

On Oct 6, 2009, at 1:54 PM, Jordan Breeding wrote:

> So does it sound like a legitimate problem?
>
> I just didn't want to take up my time and developer time at Apple if  
> I was just doing something stupid.
>
> I ran it like this: "gen_bridge_metadata -f ./JBBAdditions.framework  
> -F final --64-bit -o ./JBBAdditions.framework/Resources/ 
> BridgeSupport/JBBAdditions.bridgesupport"
>
> As long as you don't see any reason that shouldn't have worked I  
> will file a bug.
>
> Jordan
>
> On Oct 06, 2009, at 15:50, Laurent Sansonetti wrote:
>
>> Hi Jordan,
>>
>> You should submit BridgeSupport problems to:
>>
>> http://bugreporter.apple.com/
>>
>> The developer will deal with them there.
>>
>> Laurent
>>
>> On Oct 6, 2009, at 1:43 PM, Jordan Breeding wrote:
>>
>>> I have a question about whether I am seeing a bug in BridgeSupport  
>>> or not.
>>>
>>> I am running Mac OS X 10.6.1 and have a custom framework that has  
>>> some categories for Foundation/Cocoa classes.
>>>
>>> The following are the problem I noticed when using  
>>> gen_bridge_metadata:
>>>
>>> 1) I have to include Cocoa/Cocoa.h in the files, Foundation/ 
>>> Foundation.h doesn't seem to work even though those are really the  
>>> only classes I am dealing with.
>>>
>>> 2) This is the bigger one, gen_bridge_metadata isn't picking up  
>>> all of the methods/messages from my header, here is one of the  
>>> headers:
>>>
>>> =====
>>> #import <Cocoa/Cocoa.h>
>>>
>>> @interface NSArray (JBBAdditions)
>>>
>>> #pragma mark Instance Methods
>>>
>>> - (NSArray *)jbb_dictionariesWithKey:(NSString *)keyName;
>>> - (id)jbb_firstObject;
>>> - (BOOL)jbb_isEmpty;
>>> @end
>>> =====
>>>
>>> but here is the relevant section of the .bridgesupport file:
>>>
>>> =====
>>> <class name='NSArray'>
>>> <method selector='jbb_isEmpty'>
>>> <retval type='B'/>
>>> </method>
>>> </class>
>>> =====
>>>
>>> Any ideas as to why it is behaving this way? It is doing this for  
>>> all of the classes I have defined categories on (only defining one  
>>> method/message).
>>>
>>> Thanks for any input,
>>> Jordan
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From jordan.breeding at me.com  Tue Oct  6 14:08:09 2009
From: jordan.breeding at me.com (Jordan Breeding)
Date: Tue, 06 Oct 2009 16:08:09 -0500
Subject: [MacRuby-devel] BridgeSupport Question
In-Reply-To: <3E900DF2-B7F9-4A91-81C4-88FFCF64BE41@apple.com>
References: <554FD285-4537-4A63-A949-E33BA7FAE642@me.com>
	<380B69C9-61A3-46B9-97F2-E704E4655E78@apple.com>
	<D6C9A567-F206-4741-B740-52A1E3BD7462@me.com>
	<3E900DF2-B7F9-4A91-81C4-88FFCF64BE41@apple.com>
Message-ID: <BCC5F9DB-B76B-430F-BEC0-AC97E94B7240@me.com>

Thanks, that clears up a few things.

Jordan

On Oct 06, 2009, at 16:05, Laurent Sansonetti wrote:

> Hi Jordan,
>
> I don't know for 1), but you should probably pass -c "-framework  
> Cocoa".
>
> For 2) it's totally expected, the file only contains non- 
> introspectable APIs. It lists -jbb_isEmpty because the method  
> returns BOOL which needs to be annotated because it shares the same  
> runtime encoding as unsigned char. The other methods can be handled  
> at runtime.
>
> Read the BridgeSupport(5) man page for more information.
>
> Laurent
>
> On Oct 6, 2009, at 1:54 PM, Jordan Breeding wrote:
>
>> So does it sound like a legitimate problem?
>>
>> I just didn't want to take up my time and developer time at Apple  
>> if I was just doing something stupid.
>>
>> I ran it like this: "gen_bridge_metadata -f ./ 
>> JBBAdditions.framework -F final --64-bit -o ./ 
>> JBBAdditions.framework/Resources/BridgeSupport/ 
>> JBBAdditions.bridgesupport"
>>
>> As long as you don't see any reason that shouldn't have worked I  
>> will file a bug.
>>
>> Jordan
>>
>> On Oct 06, 2009, at 15:50, Laurent Sansonetti wrote:
>>
>>> Hi Jordan,
>>>
>>> You should submit BridgeSupport problems to:
>>>
>>> http://bugreporter.apple.com/
>>>
>>> The developer will deal with them there.
>>>
>>> Laurent
>>>
>>> On Oct 6, 2009, at 1:43 PM, Jordan Breeding wrote:
>>>
>>>> I have a question about whether I am seeing a bug in  
>>>> BridgeSupport or not.
>>>>
>>>> I am running Mac OS X 10.6.1 and have a custom framework that has  
>>>> some categories for Foundation/Cocoa classes.
>>>>
>>>> The following are the problem I noticed when using  
>>>> gen_bridge_metadata:
>>>>
>>>> 1) I have to include Cocoa/Cocoa.h in the files, Foundation/ 
>>>> Foundation.h doesn't seem to work even though those are really  
>>>> the only classes I am dealing with.
>>>>
>>>> 2) This is the bigger one, gen_bridge_metadata isn't picking up  
>>>> all of the methods/messages from my header, here is one of the  
>>>> headers:
>>>>
>>>> =====
>>>> #import <Cocoa/Cocoa.h>
>>>>
>>>> @interface NSArray (JBBAdditions)
>>>>
>>>> #pragma mark Instance Methods
>>>>
>>>> - (NSArray *)jbb_dictionariesWithKey:(NSString *)keyName;
>>>> - (id)jbb_firstObject;
>>>> - (BOOL)jbb_isEmpty;
>>>> @end
>>>> =====
>>>>
>>>> but here is the relevant section of the .bridgesupport file:
>>>>
>>>> =====
>>>> <class name='NSArray'>
>>>> <method selector='jbb_isEmpty'>
>>>> <retval type='B'/>
>>>> </method>
>>>> </class>
>>>> =====
>>>>
>>>> Any ideas as to why it is behaving this way? It is doing this for  
>>>> all of the classes I have defined categories on (only defining  
>>>> one method/message).
>>>>
>>>> Thanks for any input,
>>>> Jordan
>>>>
>>>> _______________________________________________
>>>> MacRuby-devel mailing list
>>>> MacRuby-devel at lists.macosforge.org
>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3820 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091006/c36f6885/attachment.bin>

From mattaimonetti at gmail.com  Tue Oct  6 15:28:27 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Tue, 6 Oct 2009 15:28:27 -0700
Subject: [MacRuby-devel] MacRuby tips
In-Reply-To: <CD27A27B-4A90-4071-8783-68B1AF84ED07@apple.com>
References: <20fefa50910061050j5257d6b7h359b51327e92940c@mail.gmail.com>
	<6F71BE17-05A1-46C4-8E7A-438BF8B5A5D0@apple.com>
	<20fefa50910061154q667e8575h6e8e3fcec794c2b@mail.gmail.com>
	<9109B616-D109-409F-B186-3DFD89A26545@me.com>
	<20fefa50910061225h43ad63d7iab3da14a8dbbe7a4@mail.gmail.com>
	<CD27A27B-4A90-4071-8783-68B1AF84ED07@apple.com>
Message-ID: <20fefa50910061528x3fcb0e8bh322282becda5b6f8@mail.gmail.com>

Josh, that's a great idea!

Testing Cocoa using MacRuby is something that I'm sure a lot of CocoaHeads
will love to do.
I'd be glad to help you out. Did you see my recipe on writing your own
framework/bundle for macruby?
http://www.macruby.org/recipes/create-an-objective-c-bundle.html

- Matt


On Tue, Oct 6, 2009 at 12:33 PM, Josh Ballanco <joshua.ballanco at apple.com>wrote:

> Hey Matt,
> Something I'm working on is writing a Framework in Xcode, and using MacRuby
> to test it. I'm running into some issues that I'm trying to chase down
> (segfaults with bacon when loading frameworks), but there were enough
> gottchas that I think this would make for a good little recipe. Let me know
> what you think, and maybe we can put something together.
>
> Cheers,
>
> Josh
>
>
> On Oct 6, 2009, at 12:25 PM, Matt Aimonetti wrote:
>
> That's why we provide you with nightly builds:
> http://www.macruby.org/downloads.html :)
> While this is indeed something a bit challenging, most developers shouldn't
> have to do it and therefore I don't think a recipe is really needed. (you
> basically just have to follow the readme).
>
> Anything else anyone encountered?
>
> I'll probably post something about streaming sound and also few tricks I
> discovered when using xcode for ruby code.
>
> - Matt
>
>
> On Tue, Oct 6, 2009 at 11:59 AM, Niket Patel <nexneo at me.com> wrote:
>
>>
>> On Oct 7, 2009, at 12:24 AM, Matt Aimonetti wrote:
>>
>>  By the way, anyone faced a problem they couldn't solve? Or maybe there is
>>> a specific topic you would like me/someone else to cover?
>>>
>>
>> Compiling MacRuby was lot harder when last I checked. :-)  Specially on 32
>> bit leopard. Then I give up.
>> Waiting for Binary Release.
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091006/e8f3176d/attachment.html>

From lsansonetti at apple.com  Tue Oct  6 16:57:21 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Tue, 06 Oct 2009 16:57:21 -0700
Subject: [MacRuby-devel] Problems with return code from sheet (possible
 regression)
In-Reply-To: <25EE3080-B429-4DF2-A7A7-28FA5090DD44@apple.com>
References: <95F6FAED-DEFE-433E-AE90-188759F372CF@mindspring.com>
	<25EE3080-B429-4DF2-A7A7-28FA5090DD44@apple.com>
Message-ID: <0120120B-7130-4830-BF3B-6A3002CA8BB6@apple.com>

FYI, the problem should (in theory) be fixed in r2741.

Laurent

On Oct 6, 2009, at 1:28 PM, Laurent Sansonetti wrote:

> Hi Michael,
>
> It's actually a well-known bug. MacRuby trunk doesn't honor the  
> sel_of_type BridgeSupport attribute, therefore your sheet callback  
> is registered to the runtime with the default signature (where all  
> arguments and return value are Objective-C objects), and later it  
> fails to convert the returnCode argument (in this backtrace, 0x1) as  
> an Objective-C object.
>
> Laurent
>
> On Oct 6, 2009, at 12:58 PM, Michael Winterstein wrote:
>
>> I seem to have run into nearly the same problem that I had a while  
>> back, in this ticket:
>> http://www.macruby.org/trac/ticket/221
>>
>> I haven't filed it yet this time since last time it turned out to  
>> be already fixed, but I'm not certain that's the case now.  At any  
>> rate, it's being handled by different functions.
>> The same thing is happening - the return code being passed to my  
>> delegate (from [NSApplication endSheet:returnCode]) isn't being  
>> treated as the NSInteger it ought to be.  At least I think so.   
>> Here's the trace, and you can see that the value 1(NSOKButton) is  
>> being treated as id, causing problems (0/NSCancelButton doesn't  
>> crash as it's a special case) :
>>
>> Program received signal:  ?EXC_BAD_ACCESS?.
>> (gdb) bt
>> #0  rb_ocid_to_rval [inlined] () at /Users/parzival/devo/buried/ 
>> MacRuby/trunk/include/ruby/ruby.h:1252
>> #1  0x0000000100130161 in rb_vm_ocval_to_rval (ocval=0x1) at  
>> compiler.cpp:6155
>> #2  0x000000010110537c in ?? ()
>> #3  0x00007fff820c29f9 in -[NSApplication endSheet:returnCode:] ()
>> #4  0x00007fff81fd523e in -[NSApplication sendAction:to:from:] ()
>> #5  0x00007fff81fd519d in -[NSControl sendAction:to:] ()
>> #6  0x00007fff8206068b in -[NSCell  
>> trackMouse:inRect:ofView:untilMouseUp:] ()
>> #7  0x00007fff820911a3 in -[NSButtonCell  
>> trackMouse:inRect:ofView:untilMouseUp:] ()
>> #8  0x00007fff8205f135 in -[NSControl mouseDown:] ()
>> #9  0x00007fff81f79967 in -[NSWindow sendEvent:] ()
>> #10 0x00007fff81eaf122 in -[NSApplication sendEvent:] ()
>> #11 0x00007fff81e45acc in -[NSApplication run] ()
>> #12 0x00007fff81e3e798 in NSApplicationMain ()
>>
>> Attached are a few files as a test case, an NSWindowController  
>> subclass and MainMenu.nib that can be dropped into a  new project  
>> to check this if anyone wants to.  I recall when I first had this  
>> problem that I could see what the change was, but unfortunately  
>> I've forgotten that now.
>> <Testfiles.zip>
>>
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Tue Oct  6 17:20:36 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 07 Oct 2009 00:20:36 -0000
Subject: [MacRuby-devel] [MacRuby] #365: nil.setStringValue causes SIGABRT
Message-ID: <048.bdfcde8f3f35957f329f84bd7f845551@macosforge.org>

#365: nil.setStringValue causes SIGABRT
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  major              |   Milestone:                       
Component:  MacRuby            |    Keywords:  32-bit, SIGABRT      
-------------------------------+--------------------------------------------
 Misusing an ivar that has not been set results in calling a method on a
 nil object. The attached code illustrates. More info in README.

 Observed on MBP 2.16 GHz Intel Core Duo
 OSX V.10.6.1

 MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, i386]

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/365>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct  6 17:43:45 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 07 Oct 2009 00:43:45 -0000
Subject: [MacRuby-devel] [MacRuby] #365: nil.setStringValue causes
	SIGABRT
In-Reply-To: <048.bdfcde8f3f35957f329f84bd7f845551@macosforge.org>
References: <048.bdfcde8f3f35957f329f84bd7f845551@macosforge.org>
Message-ID: <057.9ef6ef04db85153de202a14834f756c3@macosforge.org>

#365: nil.setStringValue causes SIGABRT
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  major              |   Milestone:                       
Component:  MacRuby            |    Keywords:  32-bit, SIGABRT      
-------------------------------+--------------------------------------------

Comment(by lsansonetti@?):

 This program crashes in 32-bit because currently Objective-C cannot
 intercept MacRuby exceptions. So, sending a message to nil triggers an
 exception which calls std::terminate() because there is no active handler.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/365#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct  6 19:16:51 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 07 Oct 2009 02:16:51 -0000
Subject: [MacRuby-devel] [MacRuby] #294: Experimental: EmbeddedMacRuby
	example crashes
In-Reply-To: <050.07b8958b7e5aa0454100890d79c489b6@macosforge.org>
References: <050.07b8958b7e5aa0454100890d79c489b6@macosforge.org>
Message-ID: <059.f5c193038f49585e26d94278e1aae7c0@macosforge.org>

#294: Experimental: EmbeddedMacRuby example crashes
---------------------------------+------------------------------------------
 Reporter:  illenberger@?        |        Owner:  lsansonetti@?        
     Type:  defect               |       Status:  closed               
 Priority:  major                |    Milestone:  MacRuby 0.5          
Component:  MacRuby              |   Resolution:  fixed                
 Keywords:                       |  
---------------------------------+------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 It seems to work now.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/294#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct  6 19:17:44 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 07 Oct 2009 02:17:44 -0000
Subject: [MacRuby-devel] [MacRuby] #138: macgem not working for me
In-Reply-To: <046.056b1e2d9f6cd81183740a7f12ddbe98@macosforge.org>
References: <046.056b1e2d9f6cd81183740a7f12ddbe98@macosforge.org>
Message-ID: <055.ecc356d10d223611bdcc6770aa56c8a9@macosforge.org>

#138: macgem not working for me
-----------------------------+----------------------------------------------
 Reporter:  nick@?           |       Owner:  lsansonetti@?        
     Type:  defect           |      Status:  new                  
 Priority:  blocker          |   Milestone:  MacRuby 0.5          
Component:  MacRuby          |    Keywords:                       
-----------------------------+----------------------------------------------
Changes (by lsansonetti@?):

  * milestone:  MacRuby 0.4 => MacRuby 0.5


Comment:

 This should be fixed by now.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/138#comment:6>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct  6 21:37:34 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 07 Oct 2009 04:37:34 -0000
Subject: [MacRuby-devel] [MacRuby] #365: nil.setStringValue causes
	SIGABRT
In-Reply-To: <048.bdfcde8f3f35957f329f84bd7f845551@macosforge.org>
References: <048.bdfcde8f3f35957f329f84bd7f845551@macosforge.org>
Message-ID: <057.04a4885a104a56551f71c65ea88196e4@macosforge.org>

#365: nil.setStringValue causes SIGABRT
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  major              |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:  32-bit, SIGABRT    |  
-------------------------------+--------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Should be fixed in r2745.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/365#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct  7 04:36:27 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 07 Oct 2009 11:36:27 -0000
Subject: [MacRuby-devel] [MacRuby] #366: Hotcocoa 'demo' crashes
Message-ID: <057.897a95e0ed94f019c19ae45716d3a9b8@macosforge.org>

#366: Hotcocoa 'demo' crashes
----------------------------------------+-----------------------------------
 Reporter:  dave.baldwin@?              |       Owner:  lsansonetti@?        
     Type:  defect                      |      Status:  new                  
 Priority:  blocker                     |   Milestone:                       
Component:  MacRuby                     |    Keywords:                       
----------------------------------------+-----------------------------------
 Using the nightly build from 6th October on Snow Leopard, Macbook pro (64
 bit).

 macrake in the hotcocoa demo directory brings up a window and then quits
 unexpectedly.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/366>
MacRuby <http://macruby.org/>


From mattaimonetti at gmail.com  Wed Oct  7 10:28:22 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Wed, 7 Oct 2009 10:28:22 -0700
Subject: [MacRuby-devel] another macruby tips post: playing audio files
Message-ID: <20fefa50910071028y724e1d05md2cc9764d384c192@mail.gmail.com>

I published another post in my macruby tips series:
http://merbist.com/2009/10/06/macruby-tips-how-to-play-an-audio-file/
Let me know if you have any questions, and since I'm at it, I'd like to
thank Laurent for his time reviewing the post.

- Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091007/68631a97/attachment.html>

From mred at dharmagaia.com  Wed Oct  7 19:37:02 2009
From: mred at dharmagaia.com (Edward Hynes)
Date: Wed, 7 Oct 2009 22:37:02 -0400
Subject: [MacRuby-devel] MacRuby not finding a method that Ruby is
Message-ID: <7B512C30-87C0-4E0B-8D47-15A8D7E5B0DF@dharmagaia.com>

Hi,

I'm attempting to use the RParsec gem under MacRuby, but am getting a  
NoMethodError when it loads.  I've create a test file that simply adds  
my local gem directory to the front of the library search path and  
then calls "require 'rparsec'".  This file runs fine under Ruby 1.9,  
but produces the following error when called from MacRuby 0.4.

/Users/ehynes/Test/Gems/rparsec/parser.rb:32:in `block in init':  
super: no superclass method `initialize:' for  
RParsec::ValueParser:RParsec::ValueParser (NoMethodError)
	from /Users/ehynes/Test/Gems/rparsec/parsers.rb:621:in `new'
	from /Users/ehynes/Test/Gems/rparsec/parsers.rb:621:in  
`<module:RParsec>'
	from /Users/ehynes/Test/Gems/rparsec/parsers.rb:3:in `<top (required)>'
	from /Users/ehynes/Test/Gems/rparsec.rb:3:in `require'
	from /Users/ehynes/Test/Gems/rparsec.rb:3:in `block in <top  
(required)>'
	from /Users/ehynes/Test/Gems/rparsec.rb:2:in `each'
	from /Users/ehynes/Test/Gems/rparsec.rb:2:in `<top (required)>'
	from AbcParser.rb:2:in `require'
	from AbcParser.rb:2:in `<main>'


The method with the error in the Parser class is:

   def self.init(*vars)
     parser_checker = {}
     vars.each_with_index do |var, i|
       name = var.to_s
       parser_checker[i] = var if name.include?('parser') && ! 
name.include?('parsers')
     end
     define_method(:initialize) do |*params|
--->  super()   # <--- line 32
       vars.each_with_index do |var, i|
         param = params[i]
         if parser_checker.include? i
           TypeChecker.check_arg_type Parser, param, self, i
         end
         instance_variable_set("@"+var.to_s, param)
       end
     end
   end


Any ideas as to why Ruby can call super in the above method, but  
MacRuby can't?  Is there a fix or workaround that I could use?  An  
alternate parser?

Thanks,
Ed


P.S.  I did have to change one line in the RParsec parser.rb file to  
get it to run under Ruby 1.9, replacing a ':' with a 'then' in a case  
statement.

	$ diff parser_original.rb parser.rb
	881c881
	<     case c when String: c[0] else c end
	---
	>     case c when String then c[0] else c end  # ':' replaced with  
'then'




From mattaimonetti at gmail.com  Wed Oct  7 19:51:17 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Wed, 7 Oct 2009 19:51:17 -0700
Subject: [MacRuby-devel] MacRuby not finding a method that Ruby is
In-Reply-To: <7B512C30-87C0-4E0B-8D47-15A8D7E5B0DF@dharmagaia.com>
References: <7B512C30-87C0-4E0B-8D47-15A8D7E5B0DF@dharmagaia.com>
Message-ID: <20fefa50910071951v18f12378yf64318d49c02197f@mail.gmail.com>

you might want to try your luck with 0.5

- Matt

On Wed, Oct 7, 2009 at 7:37 PM, Edward Hynes <mred at dharmagaia.com> wrote:

> Hi,
>
> I'm attempting to use the RParsec gem under MacRuby, but am getting a
> NoMethodError when it loads.  I've create a test file that simply adds my
> local gem directory to the front of the library search path and then calls
> "require 'rparsec'".  This file runs fine under Ruby 1.9, but produces the
> following error when called from MacRuby 0.4.
>
> /Users/ehynes/Test/Gems/rparsec/parser.rb:32:in `block in init': super: no
> superclass method `initialize:' for
> RParsec::ValueParser:RParsec::ValueParser (NoMethodError)
>        from /Users/ehynes/Test/Gems/rparsec/parsers.rb:621:in `new'
>        from /Users/ehynes/Test/Gems/rparsec/parsers.rb:621:in
> `<module:RParsec>'
>        from /Users/ehynes/Test/Gems/rparsec/parsers.rb:3:in `<top
> (required)>'
>        from /Users/ehynes/Test/Gems/rparsec.rb:3:in `require'
>        from /Users/ehynes/Test/Gems/rparsec.rb:3:in `block in <top
> (required)>'
>        from /Users/ehynes/Test/Gems/rparsec.rb:2:in `each'
>        from /Users/ehynes/Test/Gems/rparsec.rb:2:in `<top (required)>'
>        from AbcParser.rb:2:in `require'
>        from AbcParser.rb:2:in `<main>'
>
>
> The method with the error in the Parser class is:
>
>  def self.init(*vars)
>    parser_checker = {}
>    vars.each_with_index do |var, i|
>      name = var.to_s
>      parser_checker[i] = var if name.include?('parser') &&
> !name.include?('parsers')
>    end
>    define_method(:initialize) do |*params|
> --->  super()   # <--- line 32
>      vars.each_with_index do |var, i|
>        param = params[i]
>        if parser_checker.include? i
>          TypeChecker.check_arg_type Parser, param, self, i
>        end
>        instance_variable_set("@"+var.to_s, param)
>      end
>    end
>  end
>
>
> Any ideas as to why Ruby can call super in the above method, but MacRuby
> can't?  Is there a fix or workaround that I could use?  An alternate parser?
>
> Thanks,
> Ed
>
>
> P.S.  I did have to change one line in the RParsec parser.rb file to get it
> to run under Ruby 1.9, replacing a ':' with a 'then' in a case statement.
>
>        $ diff parser_original.rb parser.rb
>        881c881
>        <     case c when String: c[0] else c end
>        ---
>        >     case c when String then c[0] else c end  # ':' replaced with
> 'then'
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091007/88dca73e/attachment.html>

From lsansonetti at apple.com  Wed Oct  7 21:13:48 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Wed, 07 Oct 2009 21:13:48 -0700
Subject: [MacRuby-devel] MacRuby 0.5 beta 1
Message-ID: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>

Hi,

The first beta release of MacRuby 0.5 is out! I prepared some notes  
here:

http://www.macruby.org/blog/2009/10/07/macruby05b1.html

The goal is to go through a few beta releases before releasing the  
final 0.5.

Please give it a try and report us bugs & feedback :)

Laurent

From mred at dharmagaia.com  Wed Oct  7 21:16:35 2009
From: mred at dharmagaia.com (Edward Hynes)
Date: Thu, 8 Oct 2009 00:16:35 -0400
Subject: [MacRuby-devel] MacRuby not finding a method that Ruby is
In-Reply-To: <20fefa50910071951v18f12378yf64318d49c02197f@mail.gmail.com>
References: <7B512C30-87C0-4E0B-8D47-15A8D7E5B0DF@dharmagaia.com>
	<20fefa50910071951v18f12378yf64318d49c02197f@mail.gmail.com>
Message-ID: <6AA0F2B6-0053-4978-91AC-39BB9FF03B8D@dharmagaia.com>

I'm still on a 32-bit machine, so can't try 0.5 yet :^(

I did manage to find a workaround, however, by creating an alias for  
the 'initialize' method and then calling it instead of 'super' inside  
of the 'define_method' call.

Ed

On Oct 7, 2009, at 10:51 PM, Matt Aimonetti wrote:

> you might want to try your luck with 0.5
>
> - Matt
>
> On Wed, Oct 7, 2009 at 7:37 PM, Edward Hynes <mred at dharmagaia.com>  
> wrote:
> Hi,
>
> I'm attempting to use the RParsec gem under MacRuby, but am getting  
> a NoMethodError when it loads.  I've create a test file that simply  
> adds my local gem directory to the front of the library search path  
> and then calls "require 'rparsec'".  This file runs fine under Ruby  
> 1.9, but produces the following error when called from MacRuby 0.4.
>
> /Users/ehynes/Test/Gems/rparsec/parser.rb:32:in `block in init':  
> super: no superclass method `initialize:' for  
> RParsec::ValueParser:RParsec::ValueParser (NoMethodError)
>        from /Users/ehynes/Test/Gems/rparsec/parsers.rb:621:in `new'
>        from /Users/ehynes/Test/Gems/rparsec/parsers.rb:621:in  
> `<module:RParsec>'
>        from /Users/ehynes/Test/Gems/rparsec/parsers.rb:3:in `<top  
> (required)>'
>        from /Users/ehynes/Test/Gems/rparsec.rb:3:in `require'
>        from /Users/ehynes/Test/Gems/rparsec.rb:3:in `block in <top  
> (required)>'
>        from /Users/ehynes/Test/Gems/rparsec.rb:2:in `each'
>        from /Users/ehynes/Test/Gems/rparsec.rb:2:in `<top (required)>'
>        from AbcParser.rb:2:in `require'
>        from AbcParser.rb:2:in `<main>'
>
>
> The method with the error in the Parser class is:
>
>  def self.init(*vars)
>    parser_checker = {}
>    vars.each_with_index do |var, i|
>      name = var.to_s
>      parser_checker[i] = var if name.include?('parser') && ! 
> name.include?('parsers')
>    end
>    define_method(:initialize) do |*params|
> --->  super()   # <--- line 32
>      vars.each_with_index do |var, i|
>        param = params[i]
>        if parser_checker.include? i
>          TypeChecker.check_arg_type Parser, param, self, i
>        end
>        instance_variable_set("@"+var.to_s, param)
>      end
>    end
>  end
>
>
> Any ideas as to why Ruby can call super in the above method, but  
> MacRuby can't?  Is there a fix or workaround that I could use?  An  
> alternate parser?
>
> Thanks,
> Ed
>
>
> P.S.  I did have to change one line in the RParsec parser.rb file to  
> get it to run under Ruby 1.9, replacing a ':' with a 'then' in a  
> case statement.
>
>        $ diff parser_original.rb parser.rb
>        881c881
>        <     case c when String: c[0] else c end
>        ---
>        >     case c when String then c[0] else c end  # ':' replaced  
> with 'then'
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-- 
Edward Hynes
Dharma Gaia LLC
"Software with the Earth in Mind"
http://dharmagaia.com



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091008/27b33d90/attachment-0001.html>

From lsansonetti at apple.com  Wed Oct  7 21:21:07 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Wed, 07 Oct 2009 21:21:07 -0700
Subject: [MacRuby-devel] MacRuby not finding a method that Ruby is
In-Reply-To: <6AA0F2B6-0053-4978-91AC-39BB9FF03B8D@dharmagaia.com>
References: <7B512C30-87C0-4E0B-8D47-15A8D7E5B0DF@dharmagaia.com>
	<20fefa50910071951v18f12378yf64318d49c02197f@mail.gmail.com>
	<6AA0F2B6-0053-4978-91AC-39BB9FF03B8D@dharmagaia.com>
Message-ID: <9DE16C12-3F71-480F-AC55-260A74DCB485@apple.com>

We fixed a few 32-bit issues in trunk so you may want to give it a try  
one more time.

At least we are not maintaining 0.4 anymore, so it would be great if  
you could try your code with trunk and let us know if the bug is still  
there. Then we can try to reduce it and fix it :)

Laurent

On Oct 7, 2009, at 9:16 PM, Edward Hynes wrote:

> I'm still on a 32-bit machine, so can't try 0.5 yet :^(
>
> I did manage to find a workaround, however, by creating an alias for  
> the 'initialize' method and then calling it instead of 'super'  
> inside of the 'define_method' call.
>
> Ed
>
> On Oct 7, 2009, at 10:51 PM, Matt Aimonetti wrote:
>
>> you might want to try your luck with 0.5
>>
>> - Matt
>>
>> On Wed, Oct 7, 2009 at 7:37 PM, Edward Hynes <mred at dharmagaia.com>  
>> wrote:
>> Hi,
>>
>> I'm attempting to use the RParsec gem under MacRuby, but am getting  
>> a NoMethodError when it loads.  I've create a test file that simply  
>> adds my local gem directory to the front of the library search path  
>> and then calls "require 'rparsec'".  This file runs fine under Ruby  
>> 1.9, but produces the following error when called from MacRuby 0.4.
>>
>> /Users/ehynes/Test/Gems/rparsec/parser.rb:32:in `block in init':  
>> super: no superclass method `initialize:' for  
>> RParsec::ValueParser:RParsec::ValueParser (NoMethodError)
>>        from /Users/ehynes/Test/Gems/rparsec/parsers.rb:621:in `new'
>>        from /Users/ehynes/Test/Gems/rparsec/parsers.rb:621:in  
>> `<module:RParsec>'
>>        from /Users/ehynes/Test/Gems/rparsec/parsers.rb:3:in `<top  
>> (required)>'
>>        from /Users/ehynes/Test/Gems/rparsec.rb:3:in `require'
>>        from /Users/ehynes/Test/Gems/rparsec.rb:3:in `block in <top  
>> (required)>'
>>        from /Users/ehynes/Test/Gems/rparsec.rb:2:in `each'
>>        from /Users/ehynes/Test/Gems/rparsec.rb:2:in `<top (required) 
>> >'
>>        from AbcParser.rb:2:in `require'
>>        from AbcParser.rb:2:in `<main>'
>>
>>
>> The method with the error in the Parser class is:
>>
>>  def self.init(*vars)
>>    parser_checker = {}
>>    vars.each_with_index do |var, i|
>>      name = var.to_s
>>      parser_checker[i] = var if name.include?('parser') && ! 
>> name.include?('parsers')
>>    end
>>    define_method(:initialize) do |*params|
>> --->  super()   # <--- line 32
>>      vars.each_with_index do |var, i|
>>        param = params[i]
>>        if parser_checker.include? i
>>          TypeChecker.check_arg_type Parser, param, self, i
>>        end
>>        instance_variable_set("@"+var.to_s, param)
>>      end
>>    end
>>  end
>>
>>
>> Any ideas as to why Ruby can call super in the above method, but  
>> MacRuby can't?  Is there a fix or workaround that I could use?  An  
>> alternate parser?
>>
>> Thanks,
>> Ed
>>
>>
>> P.S.  I did have to change one line in the RParsec parser.rb file  
>> to get it to run under Ruby 1.9, replacing a ':' with a 'then' in a  
>> case statement.
>>
>>        $ diff parser_original.rb parser.rb
>>        881c881
>>        <     case c when String: c[0] else c end
>>        ---
>>        >     case c when String then c[0] else c end  # ':'  
>> replaced with 'then'
>>
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> -- 
> Edward Hynes
> Dharma Gaia LLC
> "Software with the Earth in Mind"
> http://dharmagaia.com
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From gdeciantis at gmail.com  Wed Oct  7 21:30:01 2009
From: gdeciantis at gmail.com (Giampiero De Ciantis)
Date: Thu, 8 Oct 2009 00:30:01 -0400
Subject: [MacRuby-devel] Trunk build not working
Message-ID: <483F001F-AA88-48E2-9BA3-B6D065621068@gmail.com>

I am getting this when I build:

(in /Users/Gp/projects/macruby)
/usr/bin/gcc -std=c99 markgc.c -o markgc -Wno-format
In file included from markgc.c:31:
/usr/local/include/mach-o/arch.h:35: error: nested redefinition of  
?enum NXByteOrder?
/usr/local/include/mach-o/arch.h:35: error: redeclaration of ?enum  
NXByteOrder?
/usr/local/include/mach-o/arch.h:36: error: redeclaration of  
enumerator ?NX_UnknownByteOrder?
/usr/include/architecture/byte_order.h:147: error: previous definition  
of ?NX_UnknownByteOrder? was here
/usr/local/include/mach-o/arch.h:37: error: redeclaration of  
enumerator ?NX_LittleEndian?
/usr/include/architecture/byte_order.h:148: error: previous definition  
of ?NX_LittleEndian? was here
/usr/local/include/mach-o/arch.h:39: error: redeclaration of  
enumerator ?NX_BigEndian?
/usr/include/architecture/byte_order.h:150: error: previous definition  
of ?NX_BigEndian? was here
rake aborted!
Command failed with status (1): [/usr/bin/gcc -std=c99 markgc.c -o  
markgc -...]

I am using SL on a Core 2 Duo iMac. Any thoughts?

Cheers,

-Gp

From lsansonetti at apple.com  Wed Oct  7 21:31:49 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Wed, 07 Oct 2009 21:31:49 -0700
Subject: [MacRuby-devel] MacRuby 0.5 beta 1
In-Reply-To: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
Message-ID: <B0A4F781-48A4-4BAC-AED6-D8DC1B446D1A@apple.com>

On Oct 7, 2009, at 9:13 PM, Laurent Sansonetti wrote:

> Hi,
>
> The first beta release of MacRuby 0.5 is out! I prepared some notes  
> here:
>
> http://www.macruby.org/blog/2009/10/07/macruby05b1.html
>
> The goal is to go through a few beta releases before releasing the  
> final 0.5.
>
> Please give it a try and report us bugs & feedback :)


I forgot an important detail:

I would also like to thank all the people who contributed efforts into  
this release. It took us several months to get there and I am really  
glad of what we achieved in such a relatively short period of time.

Now, let's continue the good work until the next beta :)

http://svn.macosforge.org/repository/ruby/MacRuby/trunk/TODO

Laurent

From lsansonetti at apple.com  Wed Oct  7 21:34:18 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Wed, 07 Oct 2009 21:34:18 -0700
Subject: [MacRuby-devel] Trunk build not working
In-Reply-To: <483F001F-AA88-48E2-9BA3-B6D065621068@gmail.com>
References: <483F001F-AA88-48E2-9BA3-B6D065621068@gmail.com>
Message-ID: <A79581D3-6D18-4EAA-99C0-68350AE423D9@apple.com>

It doesn't build because you apparently installed an incompatible set  
of mach-o include files in /usr/local. You could temporarily rename  
the /usr/local/include/mach-o directory (or delete it, if you don't  
know why it's there).

Laurent

On Oct 7, 2009, at 9:30 PM, Giampiero De Ciantis wrote:

> I am getting this when I build:
>
> (in /Users/Gp/projects/macruby)
> /usr/bin/gcc -std=c99 markgc.c -o markgc -Wno-format
> In file included from markgc.c:31:
> /usr/local/include/mach-o/arch.h:35: error: nested redefinition of  
> ?enum NXByteOrder?
> /usr/local/include/mach-o/arch.h:35: error: redeclaration of ?enum  
> NXByteOrder?
> /usr/local/include/mach-o/arch.h:36: error: redeclaration of  
> enumerator ?NX_UnknownByteOrder?
> /usr/include/architecture/byte_order.h:147: error: previous  
> definition of ?NX_UnknownByteOrder? was here
> /usr/local/include/mach-o/arch.h:37: error: redeclaration of  
> enumerator ?NX_LittleEndian?
> /usr/include/architecture/byte_order.h:148: error: previous  
> definition of ?NX_LittleEndian? was here
> /usr/local/include/mach-o/arch.h:39: error: redeclaration of  
> enumerator ?NX_BigEndian?
> /usr/include/architecture/byte_order.h:150: error: previous  
> definition of ?NX_BigEndian? was here
> rake aborted!
> Command failed with status (1): [/usr/bin/gcc -std=c99 markgc.c -o  
> markgc -...]
>
> I am using SL on a Core 2 Duo iMac. Any thoughts?
>
> Cheers,
>
> -Gp
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From parzival at mindspring.com  Wed Oct  7 21:46:04 2009
From: parzival at mindspring.com (Michael Winterstein)
Date: Wed, 7 Oct 2009 21:46:04 -0700
Subject: [MacRuby-devel] Problems with return code from sheet (possible
	regression)
In-Reply-To: <0120120B-7130-4830-BF3B-6A3002CA8BB6@apple.com>
References: <95F6FAED-DEFE-433E-AE90-188759F372CF@mindspring.com>
	<25EE3080-B429-4DF2-A7A7-28FA5090DD44@apple.com>
	<0120120B-7130-4830-BF3B-6A3002CA8BB6@apple.com>
Message-ID: <39164736-5F7F-4816-99A5-3202FE18504C@mindspring.com>

It seems to be working in 2761, thanks.  For a little while none of  
those calls were getting through (apparently being sent to  
drb.method_missing) so I couldn't check if it was working.  'RunModal'  
is a workaround for that specific call, too.  I'm also looking into  
SL's new way of using sheets, with a completion handler.

Michael
On Oct 6, 2009, at 4:57 PM, Laurent Sansonetti wrote:

> FYI, the problem should (in theory) be fixed in r2741.
>
> Laurent
>
> On Oct 6, 2009, at 1:28 PM, Laurent Sansonetti wrote:
>
>> Hi Michael,
>>
>> It's actually a well-known bug. MacRuby trunk doesn't honor the  
>> sel_of_type BridgeSupport attribute, therefore your sheet callback  
>> is registered to the runtime with the default signature (where all  
>> arguments and return value are Objective-C objects), and later it  
>> fails to convert the returnCode argument (in this backtrace, 0x1)  
>> as an Objective-C object.
>>
>> Laurent
>>
>> On Oct 6, 2009, at 12:58 PM, Michael Winterstein wrote:
>>
>>> I seem to have run into nearly the same problem that I had a while  
>>> back, in this ticket:
>>> http://www.macruby.org/trac/ticket/221
>>>
>>> I haven't filed it yet this time since last time it turned out to  
>>> be already fixed, but I'm not certain that's the case now.  At any  
>>> rate, it's being handled by different functions.
>>> The same thing is happening - the return code being passed to my  
>>> delegate (from [NSApplication endSheet:returnCode]) isn't being  
>>> treated as the NSInteger it ought to be.  At least I think so.   
>>> Here's the trace, and you can see that the value 1(NSOKButton) is  
>>> being treated as id, causing problems (0/NSCancelButton doesn't  
>>> crash as it's a special case) :
>>>
>>> Program received signal:  ?EXC_BAD_ACCESS?.
>>> (gdb) bt
>>> #0  rb_ocid_to_rval [inlined] () at /Users/parzival/devo/buried/ 
>>> MacRuby/trunk/include/ruby/ruby.h:1252
>>> #1  0x0000000100130161 in rb_vm_ocval_to_rval (ocval=0x1) at  
>>> compiler.cpp:6155
>>> #2  0x000000010110537c in ?? ()
>>> #3  0x00007fff820c29f9 in -[NSApplication endSheet:returnCode:] ()
>>> #4  0x00007fff81fd523e in -[NSApplication sendAction:to:from:] ()
>>> #5  0x00007fff81fd519d in -[NSControl sendAction:to:] ()
>>> #6  0x00007fff8206068b in -[NSCell  
>>> trackMouse:inRect:ofView:untilMouseUp:] ()
>>> #7  0x00007fff820911a3 in -[NSButtonCell  
>>> trackMouse:inRect:ofView:untilMouseUp:] ()
>>> #8  0x00007fff8205f135 in -[NSControl mouseDown:] ()
>>> #9  0x00007fff81f79967 in -[NSWindow sendEvent:] ()
>>> #10 0x00007fff81eaf122 in -[NSApplication sendEvent:] ()
>>> #11 0x00007fff81e45acc in -[NSApplication run] ()
>>> #12 0x00007fff81e3e798 in NSApplicationMain ()
>>>
>>> Attached are a few files as a test case, an NSWindowController  
>>> subclass and MainMenu.nib that can be dropped into a  new project  
>>> to check this if anyone wants to.  I recall when I first had this  
>>> problem that I could see what the change was, but unfortunately  
>>> I've forgotten that now.
>>> <Testfiles.zip>
>>>
>>>
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From mattaimonetti at gmail.com  Wed Oct  7 21:50:11 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Wed, 7 Oct 2009 21:50:11 -0700
Subject: [MacRuby-devel] MacRuby 0.5 beta 1
In-Reply-To: <B0A4F781-48A4-4BAC-AED6-D8DC1B446D1A@apple.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
	<B0A4F781-48A4-4BAC-AED6-D8DC1B446D1A@apple.com>
Message-ID: <20fefa50910072150q2bbf35cerd76bcc4195a7336a@mail.gmail.com>

Congrats Laurent, you did an awesome job on this release, I can't wait to
0.5 final out :)

To celebrate the release I wrote a quick blog post
http://merbist.com/2009/10/07/macruby-0-5-beta-1-and-textorize/
And pushed what might be the very first MacRuby specific gem (at least on
gemcutter :))

I basically simply ported Thomas Fuchs textorize gem to MacRuby, released it
on gemcutter and wrote a quick explanation on my blog.

It's good to finally have rubygems back in 0.5 :)

- Matt



On Wed, Oct 7, 2009 at 9:31 PM, Laurent Sansonetti <lsansonetti at apple.com>wrote:

> On Oct 7, 2009, at 9:13 PM, Laurent Sansonetti wrote:
>
>  Hi,
>>
>> The first beta release of MacRuby 0.5 is out! I prepared some notes here:
>>
>> http://www.macruby.org/blog/2009/10/07/macruby05b1.html
>>
>> The goal is to go through a few beta releases before releasing the final
>> 0.5.
>>
>> Please give it a try and report us bugs & feedback :)
>>
>
>
> I forgot an important detail:
>
> I would also like to thank all the people who contributed efforts into this
> release. It took us several months to get there and I am really glad of what
> we achieved in such a relatively short period of time.
>
> Now, let's continue the good work until the next beta :)
>
> http://svn.macosforge.org/repository/ruby/MacRuby/trunk/TODO
>
>
> Laurent
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091007/e1a66b66/attachment-0001.html>

From conradwt at gmail.com  Wed Oct  7 22:27:42 2009
From: conradwt at gmail.com (Conrad Taylor)
Date: Wed, 7 Oct 2009 22:27:42 -0700
Subject: [MacRuby-devel] MacRuby 0.5 beta 1
In-Reply-To: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
Message-ID: <7317d7610910072227k222d92bfve0dec538394bafb7@mail.gmail.com>

Hi Laurent, in the compatibility section, you might want to change

We want MacRuby to be as compatible as possible with existing Ruby programs.
We have been working hard on MacRuby to make sure it behaves like MRI 1.9.?.

to

We want MacRuby to be as compatible as possible with existing Ruby programs.
We have been working hard on MacRuby to make sure it behaves like Koichi's
Ruby Interpreter (KRI) or the more commonly used name, *Yet
another<http://en.wikipedia.org/wiki/Yet_another> Ruby
VM (YARV), for Ruby *1.9.?.

In any case, great work and I'll start playing with this release.

-Conrad

On Wed, Oct 7, 2009 at 9:13 PM, Laurent Sansonetti <lsansonetti at apple.com>wrote:

> Hi,
>
> The first beta release of MacRuby 0.5 is out! I prepared some notes here:
>
> http://www.macruby.org/blog/2009/10/07/macruby05b1.html
>
> The goal is to go through a few beta releases before releasing the final
> 0.5.
>
> Please give it a try and report us bugs & feedback :)
>
> Laurent
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091007/31ea0ceb/attachment.html>

From conradwt at gmail.com  Wed Oct  7 23:20:58 2009
From: conradwt at gmail.com (Conrad Taylor)
Date: Wed, 7 Oct 2009 23:20:58 -0700
Subject: [MacRuby-devel] [0.5 beta 1] issues running ruby specs with macrake
	and rake
Message-ID: <7317d7610910072320l209f6b2by4d285d4a2901026d@mail.gmail.com>

a)  running spec:ci using macrake segmentation fault

$ macrake spec:ci
unknown: warning: already initialized constant TOPDIR
unknown: warning: already initialized constant CONFIG
unknown: warning: already initialized constant MAKEFILE_CONFIG
Segmentation fault

b)  running spec:ci using rake aborts

$ rake spec:ci
(in /Users/conradwt/macruby.dir/projects/macruby-trunk)
./mspec/bin/mspec ci -B ./spec/macruby.mspec  :full
MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
.............................................................................................................................................................2009-10-07
23:02:23.167 macruby[11134:1b07] *** Terminating app due to uncaught
exception 'NameError', reason: 'undefined method `pwd' for module
`RbConfig''
*** Call stack at first throw:
(
0   CoreFoundation                      0x00007fff82a995a4
__exceptionPreprocess + 180
1   libobjc.A.dylib                     0x00007fff86ae3313
objc_exception_throw + 45
2   libmacruby.dylib                    0x000000010017a185 rb_vm_raise + 197
3   libmacruby.dylib                    0x000000010003f8c9 rb_exc_raise + 9
4   libmacruby.dylib                    0x000000010003c3d4 rb_name_error +
260
5   libmacruby.dylib                    0x0000000100040154 rb_print_undef +
196
6   libmacruby.dylib                    0x000000010012065d rb_export_method
+ 157
7   libmacruby.dylib                    0x0000000100120d09 rb_mod_modfunc +
441
8   libmacruby.dylib                    0x000000010016d02f rb_vm_dispatch +
5679
9   fileutils.rbo                       0x00000001011bdea5 __ruby_scope1 +
197
)
terminate called after throwing an instance of 'NSException'
rake aborted!
Command failed with status (): [./mspec/bin/mspec ci -B
./spec/macruby.msp...]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091007/034275e2/attachment.html>

From ruby-noreply at macosforge.org  Wed Oct  7 23:30:05 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 08 Oct 2009 06:30:05 -0000
Subject: [MacRuby-devel] [MacRuby] #367: Error in color.rb
Message-ID: <049.05659c440d67222ac4c7f6e5bb281ff4@macosforge.org>

#367: Error in color.rb
--------------------------------+-------------------------------------------
 Reporter:  i.script@?          |       Owner:  lsansonetti@?        
     Type:  defect              |      Status:  new                  
 Priority:  blocker             |   Milestone:  MacRuby 0.5          
Component:  MacRuby             |    Keywords:  Hotcocoa Color Error 
--------------------------------+-------------------------------------------
 The file color.rb inside the hotcocoa/graphics directors is using a wrong
 class method!

 Following code has to be changed:

 COLORNAMES.each_key do |name|
       (class << self; self; end).define_method(name) do
         named(name)
       end
     end


 In this case define_singleton_method is the way to go.

 COLORNAMES.each_key do |name|
       (class << self; self; end).define_singleton_method(name) do
         named(name)
       end
     end

 Tom Fuerstner

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/367>
MacRuby <http://macruby.org/>


From vincent.isambart at gmail.com  Thu Oct  8 00:01:13 2009
From: vincent.isambart at gmail.com (Vincent Isambart)
Date: Thu, 8 Oct 2009 16:01:13 +0900
Subject: [MacRuby-devel] [0.5 beta 1] issues running ruby specs with
	macrake and rake
In-Reply-To: <7317d7610910072320l209f6b2by4d285d4a2901026d@mail.gmail.com>
References: <7317d7610910072320l209f6b2by4d285d4a2901026d@mail.gmail.com>
Message-ID: <7d9a1f530910080001m7173f84o9fcfdfc542ded346@mail.gmail.com>

> a) ?running spec:ci using macrake segmentation fault
> b) ?running spec:ci using rake aborts

Try running spec:ci disabling the RBO files :
VM_DISABLE_RBO=1 rake spec:ci
or
VM_DISABLE_RBO=1 macrake spec:ci

From ruby-noreply at macosforge.org  Thu Oct  8 01:13:07 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 08 Oct 2009 08:13:07 -0000
Subject: [MacRuby-devel] [MacRuby] #368: AOT compilation failing on this
	example
Message-ID: <054.c25ea5a5052403b81df31b96a0ef12e2@macosforge.org>

#368: AOT compilation failing on this example
-------------------------------------+--------------------------------------
 Reporter:  mattaimonetti@?          |       Owner:  lsansonetti@?        
     Type:  defect                   |      Status:  new                  
 Priority:  major                    |   Milestone:  MacRuby 0.5          
Component:  MacRuby                  |    Keywords:                       
-------------------------------------+--------------------------------------


-- 
Ticket URL: <http://www.macruby.org/trac/ticket/368>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Thu Oct  8 01:55:29 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 08 Oct 2009 01:55:29 -0700
Subject: [MacRuby-devel] [0.5 beta 1] issues running ruby specs with
 macrake and rake
In-Reply-To: <7317d7610910072320l209f6b2by4d285d4a2901026d@mail.gmail.com>
References: <7317d7610910072320l209f6b2by4d285d4a2901026d@mail.gmail.com>
Message-ID: <A84BD8EE-CC90-439A-B85C-E851526CD071@apple.com>

This regression was introduced by r2762 (which was committed *after*  
the beta :)) and it has been reverted.

Laurent

On Oct 7, 2009, at 11:20 PM, Conrad Taylor wrote:

> a)  running spec:ci using macrake segmentation fault
>
> $ macrake spec:ci
> unknown: warning: already initialized constant TOPDIR
> unknown: warning: already initialized constant CONFIG
> unknown: warning: already initialized constant MAKEFILE_CONFIG
> Segmentation fault
>
> b)  running spec:ci using rake aborts
>
> $ rake spec:ci
> (in /Users/conradwt/macruby.dir/projects/macruby-trunk)
> ./mspec/bin/mspec ci -B ./spec/macruby.mspec  :full
> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
> .............................................................................................................................................................2009 
> -10-07 23:02:23.167 macruby[11134:1b07] *** Terminating app due to  
> uncaught exception 'NameError', reason: 'undefined method `pwd' for  
> module `RbConfig''
> *** Call stack at first throw:
> (
> 	0   CoreFoundation                      0x00007fff82a995a4  
> __exceptionPreprocess + 180
> 	1   libobjc.A.dylib                     0x00007fff86ae3313  
> objc_exception_throw + 45
> 	2   libmacruby.dylib                    0x000000010017a185  
> rb_vm_raise + 197
> 	3   libmacruby.dylib                    0x000000010003f8c9  
> rb_exc_raise + 9
> 	4   libmacruby.dylib                    0x000000010003c3d4  
> rb_name_error + 260
> 	5   libmacruby.dylib                    0x0000000100040154  
> rb_print_undef + 196
> 	6   libmacruby.dylib                    0x000000010012065d  
> rb_export_method + 157
> 	7   libmacruby.dylib                    0x0000000100120d09  
> rb_mod_modfunc + 441
> 	8   libmacruby.dylib                    0x000000010016d02f  
> rb_vm_dispatch + 5679
> 	9   fileutils.rbo                       0x00000001011bdea5  
> __ruby_scope1 + 197
> )
> terminate called after throwing an instance of 'NSException'
> rake aborted!
> Command failed with status (): [./mspec/bin/mspec ci -B ./spec/ 
> macruby.msp...]
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From conradwt at gmail.com  Thu Oct  8 02:02:34 2009
From: conradwt at gmail.com (Conrad Taylor)
Date: Thu, 8 Oct 2009 02:02:34 -0700
Subject: [MacRuby-devel] [0.5 beta 1] issues running ruby specs with
	macrake and rake
In-Reply-To: <A84BD8EE-CC90-439A-B85C-E851526CD071@apple.com>
References: <7317d7610910072320l209f6b2by4d285d4a2901026d@mail.gmail.com>
	<A84BD8EE-CC90-439A-B85C-E851526CD071@apple.com>
Message-ID: <7317d7610910080202k532ecc43wd592dcf42b7db610@mail.gmail.com>

Laurent, I was interested in putting the RBO through their paces by running
the Ruby Rspecs.  Thus, is this something that's planned for a future
release?
-Conrad

On Thu, Oct 8, 2009 at 1:55 AM, Laurent Sansonetti <lsansonetti at apple.com>wrote:

> This regression was introduced by r2762 (which was committed *after* the
> beta :)) and it has been reverted.
>
> Laurent
>
>
> On Oct 7, 2009, at 11:20 PM, Conrad Taylor wrote:
>
>  a)  running spec:ci using macrake segmentation fault
>>
>> $ macrake spec:ci
>> unknown: warning: already initialized constant TOPDIR
>> unknown: warning: already initialized constant CONFIG
>> unknown: warning: already initialized constant MAKEFILE_CONFIG
>> Segmentation fault
>>
>> b)  running spec:ci using rake aborts
>>
>> $ rake spec:ci
>> (in /Users/conradwt/macruby.dir/projects/macruby-trunk)
>> ./mspec/bin/mspec ci -B ./spec/macruby.mspec  :full
>> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
>> .............................................................................................................................................................2009-10-07
>> 23:02:23.167 macruby[11134:1b07] *** Terminating app due to uncaught
>> exception 'NameError', reason: 'undefined method `pwd' for module
>> `RbConfig''
>> *** Call stack at first throw:
>> (
>>        0   CoreFoundation                      0x00007fff82a995a4
>> __exceptionPreprocess + 180
>>        1   libobjc.A.dylib                     0x00007fff86ae3313
>> objc_exception_throw + 45
>>        2   libmacruby.dylib                    0x000000010017a185
>> rb_vm_raise + 197
>>        3   libmacruby.dylib                    0x000000010003f8c9
>> rb_exc_raise + 9
>>        4   libmacruby.dylib                    0x000000010003c3d4
>> rb_name_error + 260
>>        5   libmacruby.dylib                    0x0000000100040154
>> rb_print_undef + 196
>>        6   libmacruby.dylib                    0x000000010012065d
>> rb_export_method + 157
>>        7   libmacruby.dylib                    0x0000000100120d09
>> rb_mod_modfunc + 441
>>        8   libmacruby.dylib                    0x000000010016d02f
>> rb_vm_dispatch + 5679
>>        9   fileutils.rbo                       0x00000001011bdea5
>> __ruby_scope1 + 197
>> )
>> terminate called after throwing an instance of 'NSException'
>> rake aborted!
>> Command failed with status (): [./mspec/bin/mspec ci -B
>> ./spec/macruby.msp...]
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091008/e70b43dc/attachment.html>

From wayneeseguin at gmail.com  Thu Oct  8 03:36:26 2009
From: wayneeseguin at gmail.com (Wayne Seguin)
Date: Thu, 8 Oct 2009 06:36:26 -0400
Subject: [MacRuby-devel] MacRuby 0.5 beta 1
In-Reply-To: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
Message-ID: <237413E7-69DB-4E7B-844E-7DD33C2B5ECE@gmail.com>

Excellent,

Is it possible to a) install from command line and b) tell it to  
install to a specific location?
(--prefix=~/.rvm/macruby-0.5b1)

Thanks,

   ~Wayne

On Oct 08, 2009, at 00:13 , Laurent Sansonetti wrote:

> Hi,
>
> The first beta release of MacRuby 0.5 is out! I prepared some notes  
> here:
>
> http://www.macruby.org/blog/2009/10/07/macruby05b1.html
>
> The goal is to go through a few beta releases before releasing the  
> final 0.5.
>
> Please give it a try and report us bugs & feedback :)
>
> Laurent
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Thu Oct  8 04:13:15 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 08 Oct 2009 11:13:15 -0000
Subject: [MacRuby-devel] [MacRuby] #178: ArgumentError Exception: can't
 convert C/Objective-C value of type `[4d]' to Ruby object
In-Reply-To: <050.3a3af14b1f6f0240755c56160cc69c63@macosforge.org>
References: <050.3a3af14b1f6f0240755c56160cc69c63@macosforge.org>
Message-ID: <059.6020ed67ac6f2468ac6c58f85de6ee80@macosforge.org>

#178: ArgumentError Exception: can't convert C/Objective-C value of type `[4d]'
to Ruby object
---------------------------------+------------------------------------------
 Reporter:  dognotdog@?          |       Owner:  lsansonetti@?              
     Type:  defect               |      Status:  new                        
 Priority:  major                |   Milestone:                             
Component:  MacRuby              |    Keywords:  ArgumentError array convert
---------------------------------+------------------------------------------

Comment(by dognotdog@?):

 I just want to add that as of trunk r2709, this is still broken, and my
 previous patch also no longer works with 0.5, as the boxing code is
 completely different. Unfortunately, this is critical for me to get my
 project running on Snow Leopard.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/178#comment:2>
MacRuby <http://macruby.org/>


From gdeciantis at gmail.com  Thu Oct  8 04:33:43 2009
From: gdeciantis at gmail.com (Giampiero De Ciantis)
Date: Thu, 8 Oct 2009 07:33:43 -0400
Subject: [MacRuby-devel] Trunk build not working
In-Reply-To: <A79581D3-6D18-4EAA-99C0-68350AE423D9@apple.com>
References: <483F001F-AA88-48E2-9BA3-B6D065621068@gmail.com>
	<A79581D3-6D18-4EAA-99C0-68350AE423D9@apple.com>
Message-ID: <75FEF953-25A8-4CE5-9B60-43FDC0B688A1@gmail.com>

Thanks Laurent.

It's weird that this happened since the only thing I changed between  
builds was that I blew away the \Library\Frameworks\MacRuby folder to  
clean up my machine a bit. Ah well, it's all good now.

Cheers,

-Gp



On 2009-10-08, at 12:34 AM, Laurent Sansonetti wrote:

> It doesn't build because you apparently installed an incompatible  
> set of mach-o include files in /usr/local. You could temporarily  
> rename the /usr/local/include/mach-o directory (or delete it, if you  
> don't know why it's there).
>
> Laurent
>
> On Oct 7, 2009, at 9:30 PM, Giampiero De Ciantis wrote:
>
>> I am getting this when I build:
>>
>> (in /Users/Gp/projects/macruby)
>> /usr/bin/gcc -std=c99 markgc.c -o markgc -Wno-format
>> In file included from markgc.c:31:
>> /usr/local/include/mach-o/arch.h:35: error: nested redefinition of  
>> ?enum NXByteOrder?
>> /usr/local/include/mach-o/arch.h:35: error: redeclaration of ?enum  
>> NXByteOrder?
>> /usr/local/include/mach-o/arch.h:36: error: redeclaration of  
>> enumerator ?NX_UnknownByteOrder?
>> /usr/include/architecture/byte_order.h:147: error: previous  
>> definition of ?NX_UnknownByteOrder? was here
>> /usr/local/include/mach-o/arch.h:37: error: redeclaration of  
>> enumerator ?NX_LittleEndian?
>> /usr/include/architecture/byte_order.h:148: error: previous  
>> definition of ?NX_LittleEndian? was here
>> /usr/local/include/mach-o/arch.h:39: error: redeclaration of  
>> enumerator ?NX_BigEndian?
>> /usr/include/architecture/byte_order.h:150: error: previous  
>> definition of ?NX_BigEndian? was here
>> rake aborted!
>> Command failed with status (1): [/usr/bin/gcc -std=c99 markgc.c -o  
>> markgc -...]
>>
>> I am using SL on a Core 2 Duo iMac. Any thoughts?
>>
>> Cheers,
>>
>> -Gp
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From keith.gautreaux at gmail.com  Thu Oct  8 06:22:01 2009
From: keith.gautreaux at gmail.com (Keith Gautreaux)
Date: Thu, 8 Oct 2009 08:22:01 -0500
Subject: [MacRuby-devel] Link Error in 0.5b1 blog post announcement
Message-ID: <a3fb9cde0910080622m657bfa49t3e95b19bc3d798fe@mail.gmail.com>

FYI, the "report us" link the in third paragraph of the 0.5b1
announcement on macruby.org has a link error.  It should be top-level
(http://macruby.org/contact-us.html) but instead is under the
blog/2009/10/07 hierarchy.  I tried to fork the site on github and
make a diff but the github mirror seems to be lagging behind (last
commit is from 10/2/09).

-- 
Keith

From j.dabel at t-online.de  Thu Oct  8 08:44:26 2009
From: j.dabel at t-online.de (Juergen Dabel)
Date: Thu, 8 Oct 2009 17:44:26 +0200
Subject: [MacRuby-devel] 0.5 beta1
Message-ID: <10D89579-6FA0-44EE-A995-73895E38A9FF@t-online.de>

Help,

I get from the blog sample:

dab:~ jdabel$ macrubyc t.rb -o t
Can't locate program `llc'

My mac:
Hardware-?bersicht:

   Modellname:	MacBook
   Modell-Identifizierung:	MacBook5,1
   Prozessortyp:	Intel Core 2 Duo
   Prozessorgeschwindigkeit:	2,4 GHz
   Anzahl der Prozessoren:	1
   Gesamtzahl der Kerne:	2
   L2-Cache:	3 MB
   Speicher:	4 GB
   Busgeschwindigkeit:	1,07 GHz
   Boot-ROM-Version:	MB51.0073.B06
   SMC-Version (System):	1.32f8
   ...

what todo?

Thank you

Juergen Dabel
Schrobenhausen
Germany
j.dabel at t-online.de


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091008/25424e73/attachment.html>

From mattaimonetti at gmail.com  Thu Oct  8 10:03:36 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Thu, 8 Oct 2009 10:03:36 -0700
Subject: [MacRuby-devel] Link Error in 0.5b1 blog post announcement
In-Reply-To: <a3fb9cde0910080622m657bfa49t3e95b19bc3d798fe@mail.gmail.com>
References: <a3fb9cde0910080622m657bfa49t3e95b19bc3d798fe@mail.gmail.com>
Message-ID: <20fefa50910081003j225af409u2622a2a4783246fb@mail.gmail.com>

thanks fixed, it's waiting for deployment. I'll also update the github
mirror later today.

- Matt

On Thu, Oct 8, 2009 at 6:22 AM, Keith Gautreaux
<keith.gautreaux at gmail.com>wrote:

> FYI, the "report us" link the in third paragraph of the 0.5b1
> announcement on macruby.org has a link error.  It should be top-level
> (http://macruby.org/contact-us.html) but instead is under the
> blog/2009/10/07 hierarchy.  I tried to fork the site on github and
> make a diff but the github mirror seems to be lagging behind (last
> commit is from 10/2/09).
>
> --
> Keith
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091008/2192fdd9/attachment.html>

From keith.gautreaux at gmail.com  Thu Oct  8 10:11:18 2009
From: keith.gautreaux at gmail.com (Keith Gautreaux)
Date: Thu, 8 Oct 2009 12:11:18 -0500
Subject: [MacRuby-devel] Link Error in 0.5b1 blog post announcement
In-Reply-To: <20fefa50910081003j225af409u2622a2a4783246fb@mail.gmail.com>
References: <a3fb9cde0910080622m657bfa49t3e95b19bc3d798fe@mail.gmail.com>
	<20fefa50910081003j225af409u2622a2a4783246fb@mail.gmail.com>
Message-ID: <a3fb9cde0910081011r5d5c6ab6l20c7dbb8a55e5e8@mail.gmail.com>

Matt,
The new URL is closer but still broken.  It points to
http://macruby.org/blog/contact-us.html instead of the top-level
http://macruby.org/contact-us.html, thus it's still giving a 404.

On Thu, Oct 8, 2009 at 12:03 PM, Matt Aimonetti <mattaimonetti at gmail.com> wrote:
> thanks fixed, it's waiting for deployment. I'll also update the github
> mirror later today.
>
> - Matt
>
> On Thu, Oct 8, 2009 at 6:22 AM, Keith Gautreaux <keith.gautreaux at gmail.com>
> wrote:
>>
>> FYI, the "report us" link the in third paragraph of the 0.5b1
>> announcement on macruby.org has a link error. ?It should be top-level
>> (http://macruby.org/contact-us.html) but instead is under the
>> blog/2009/10/07 hierarchy. ?I tried to fork the site on github and
>> make a diff but the github mirror seems to be lagging behind (last
>> commit is from 10/2/09).
>>
>> --
>> Keith
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>



-- 
Keith

From ruby-noreply at macosforge.org  Thu Oct  8 10:24:50 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 08 Oct 2009 17:24:50 -0000
Subject: [MacRuby-devel] [MacRuby] #369: Change wording of
	sample-macruby/buildall.rb
Message-ID: <056.e9f30d1943b0ecdaa3a5bb7e52a39ae4@macosforge.org>

#369: Change wording of sample-macruby/buildall.rb
---------------------------------------+------------------------------------
 Reporter:  keith.gautreaux@?          |       Owner:  lsansonetti@?        
     Type:  enhancement                |      Status:  new                  
 Priority:  trivial                    |   Milestone:  MacRuby 0.5          
Component:  MacRuby                    |    Keywords:                       
---------------------------------------+------------------------------------
 Below is a minor diff to change the output wording of the buildall.rb
 script.  Just adding a little polish.

 http://svn.macosforge.org/repository/ruby/MacRuby/trunk/sample-
 macruby/buildall.rb

 @@ -39,5 +39,5 @@

  [succeeded, failed].each { |a| a << 'None' if a.empty? }

 -puts "Successful to build: #{succeeded.join(', ')}"
 +puts "Successfully built: #{succeeded.join(', ')}"
  puts "Failed to build: #{failed.join(', ')}"
 \ No newline at end of file

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/369>
MacRuby <http://macruby.org/>


From mattaimonetti at gmail.com  Thu Oct  8 10:54:11 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Thu, 8 Oct 2009 10:54:11 -0700
Subject: [MacRuby-devel] Link Error in 0.5b1 blog post announcement
In-Reply-To: <a3fb9cde0910081011r5d5c6ab6l20c7dbb8a55e5e8@mail.gmail.com>
References: <a3fb9cde0910080622m657bfa49t3e95b19bc3d798fe@mail.gmail.com>
	<20fefa50910081003j225af409u2622a2a4783246fb@mail.gmail.com>
	<a3fb9cde0910081011r5d5c6ab6l20c7dbb8a55e5e8@mail.gmail.com>
Message-ID: <20fefa50910081054m17976a5exa26b06646053ecde@mail.gmail.com>

Here is the commit:

-Remember that this is a development version of MacRuby provided for
testing and experimentation purposes only. Even if a few things are
quite stable, others are still under development. Please give it a try
and "report us":contact-us.html any problem you find, to make sure the
final release will be great.
+Remember that this is a development version of MacRuby provided for
testing and experimentation purposes only. Even if a few things are
quite stable, others are still under development. Please give it a try
and "report us":http://www.macruby.org/contact-us.html any problem you
find, to make sure the final release will be great.


However, we need to wait for Laurent to deploy the change :)

- Matt


On Thu, Oct 8, 2009 at 10:11 AM, Keith Gautreaux
<keith.gautreaux at gmail.com>wrote:

> Matt,
> The new URL is closer but still broken.  It points to
> http://macruby.org/blog/contact-us.html instead of the top-level
> http://macruby.org/contact-us.html, thus it's still giving a 404.
>
> On Thu, Oct 8, 2009 at 12:03 PM, Matt Aimonetti <mattaimonetti at gmail.com>
> wrote:
> > thanks fixed, it's waiting for deployment. I'll also update the github
> > mirror later today.
> >
> > - Matt
> >
> > On Thu, Oct 8, 2009 at 6:22 AM, Keith Gautreaux <
> keith.gautreaux at gmail.com>
> > wrote:
> >>
> >> FYI, the "report us" link the in third paragraph of the 0.5b1
> >> announcement on macruby.org has a link error.  It should be top-level
> >> (http://macruby.org/contact-us.html) but instead is under the
> >> blog/2009/10/07 hierarchy.  I tried to fork the site on github and
> >> make a diff but the github mirror seems to be lagging behind (last
> >> commit is from 10/2/09).
> >>
> >> --
> >> Keith
> >> _______________________________________________
> >> MacRuby-devel mailing list
> >> MacRuby-devel at lists.macosforge.org
> >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> >
> >
> > _______________________________________________
> > MacRuby-devel mailing list
> > MacRuby-devel at lists.macosforge.org
> > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> >
> >
>
>
>
> --
> Keith
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091008/2cb40e6d/attachment-0001.html>

From lsansonetti at apple.com  Thu Oct  8 10:57:39 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 08 Oct 2009 10:57:39 -0700
Subject: [MacRuby-devel] Link Error in 0.5b1 blog post announcement
In-Reply-To: <20fefa50910081054m17976a5exa26b06646053ecde@mail.gmail.com>
References: <a3fb9cde0910080622m657bfa49t3e95b19bc3d798fe@mail.gmail.com>
	<20fefa50910081003j225af409u2622a2a4783246fb@mail.gmail.com>
	<a3fb9cde0910081011r5d5c6ab6l20c7dbb8a55e5e8@mail.gmail.com>
	<20fefa50910081054m17976a5exa26b06646053ecde@mail.gmail.com>
Message-ID: <0DA5FF2D-89DB-4F5B-9005-17AE8272ABF7@apple.com>

Done.

Laurent

On Oct 8, 2009, at 10:54 AM, Matt Aimonetti wrote:

> Here is the commit:
>
> -Remember that this is a development version of MacRuby provided for  
> testing and experimentation purposes only. Even if a few things are  
> quite stable, others are still under development. Please give it a  
> try and "report us":contact-us.html any problem you find, to make  
> sure the final release will be great.
>
> +Remember that this is a development version of MacRuby provided for  
> testing and experimentation purposes only. Even if a few things are  
> quite stable, others are still under development. Please give it a  
> try and "report us":http://www.macruby.org/contact-us.html any  
> problem you find, to make sure the final release will be great.
>
>
> However, we need to wait for Laurent to deploy the change :)
>
> - Matt
>
>
> On Thu, Oct 8, 2009 at 10:11 AM, Keith Gautreaux <keith.gautreaux at gmail.com 
> > wrote:
> Matt,
> The new URL is closer but still broken.  It points to
> http://macruby.org/blog/contact-us.html instead of the top-level
> http://macruby.org/contact-us.html, thus it's still giving a 404.
>
> On Thu, Oct 8, 2009 at 12:03 PM, Matt Aimonetti <mattaimonetti at gmail.com 
> > wrote:
> > thanks fixed, it's waiting for deployment. I'll also update the  
> github
> > mirror later today.
> >
> > - Matt
> >
> > On Thu, Oct 8, 2009 at 6:22 AM, Keith Gautreaux <keith.gautreaux at gmail.com 
> >
> > wrote:
> >>
> >> FYI, the "report us" link the in third paragraph of the 0.5b1
> >> announcement on macruby.org has a link error.  It should be top- 
> level
> >> (http://macruby.org/contact-us.html) but instead is under the
> >> blog/2009/10/07 hierarchy.  I tried to fork the site on github and
> >> make a diff but the github mirror seems to be lagging behind (last
> >> commit is from 10/2/09).
> >>
> >> --
> >> Keith
> >> _______________________________________________
> >> MacRuby-devel mailing list
> >> MacRuby-devel at lists.macosforge.org
> >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> >
> >
> > _______________________________________________
> > MacRuby-devel mailing list
> > MacRuby-devel at lists.macosforge.org
> > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> >
> >
>
>
>
> --
> Keith
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From lsansonetti at apple.com  Thu Oct  8 10:59:35 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 08 Oct 2009 10:59:35 -0700
Subject: [MacRuby-devel] 0.5 beta1
In-Reply-To: <10D89579-6FA0-44EE-A995-73895E38A9FF@t-online.de>
References: <10D89579-6FA0-44EE-A995-73895E38A9FF@t-online.de>
Message-ID: <0033CCD7-35FB-4BC1-B7A8-67FC3292A343@apple.com>

Hi Juergen,

Looks like we forgot to bundle llc in the installer, sorry.

We will make sure this is fixed by the next beta. In the meantime you  
can install trunk manually (see README.rdoc file for instructions).

Laurent

On Oct 8, 2009, at 8:44 AM, Juergen Dabel wrote:

> Help,
>
> I get from the blog sample:
>
> dab:~ jdabel$ macrubyc t.rb -o t
> Can't locate program `llc'
>
> My mac:
> Hardware-?bersicht:
>
>   Modellname:	MacBook
>   Modell-Identifizierung:	MacBook5,1
>   Prozessortyp:	Intel Core 2 Duo
>   Prozessorgeschwindigkeit:	2,4 GHz
>   Anzahl der Prozessoren:	1
>   Gesamtzahl der Kerne:	2
>   L2-Cache:	3 MB
>   Speicher:	4 GB
>   Busgeschwindigkeit:	1,07 GHz
>   Boot-ROM-Version:	MB51.0073.B06
>   SMC-Version (System):	1.32f8
>   ...
>
> what todo?
>
> Thank you
>
> Juergen Dabel
> Schrobenhausen
> Germany
> j.dabel at t-online.de
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Thu Oct  8 11:19:32 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 08 Oct 2009 18:19:32 -0000
Subject: [MacRuby-devel] [MacRuby] #369: Change wording of
	sample-macruby/buildall.rb
In-Reply-To: <056.e9f30d1943b0ecdaa3a5bb7e52a39ae4@macosforge.org>
References: <056.e9f30d1943b0ecdaa3a5bb7e52a39ae4@macosforge.org>
Message-ID: <065.14bc4f1e63eb32f297ffc38cd8ec756e@macosforge.org>

#369: Change wording of sample-macruby/buildall.rb
---------------------------------------+------------------------------------
 Reporter:  keith.gautreaux@?          |       Owner:  lsansonetti@?        
     Type:  enhancement                |      Status:  new                  
 Priority:  trivial                    |   Milestone:  MacRuby 0.5          
Component:  MacRuby                    |    Keywords:                       
---------------------------------------+------------------------------------

Comment(by keith.gautreaux@?):

 The HTML escaping ate the pasted diff so I saved it as a file and attached
 it to the ticket.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/369#comment:1>
MacRuby <http://macruby.org/>


From masterkain at gmail.com  Thu Oct  8 11:21:22 2009
From: masterkain at gmail.com (Claudio Poli)
Date: Thu, 8 Oct 2009 20:21:22 +0200
Subject: [MacRuby-devel] 0.5 beta1
In-Reply-To: <0033CCD7-35FB-4BC1-B7A8-67FC3292A343@apple.com>
References: <10D89579-6FA0-44EE-A995-73895E38A9FF@t-online.de>
	<0033CCD7-35FB-4BC1-B7A8-67FC3292A343@apple.com>
Message-ID: <8917EF70-DA43-40AC-A3B2-EF2445200EA9@gmail.com>

or nightly build perhaps? ;P

Il giorno 08/ott/2009, alle ore 19.59, Laurent Sansonetti ha scritto:

> Hi Juergen,
>
> Looks like we forgot to bundle llc in the installer, sorry.
>
> We will make sure this is fixed by the next beta. In the meantime  
> you can install trunk manually (see README.rdoc file for  
> instructions).
>
> Laurent
>
> On Oct 8, 2009, at 8:44 AM, Juergen Dabel wrote:
>
>> Help,
>>
>> I get from the blog sample:
>>
>> dab:~ jdabel$ macrubyc t.rb -o t
>> Can't locate program `llc'
>>
>> My mac:
>> Hardware-?bersicht:
>>
>>  Modellname:	MacBook
>>  Modell-Identifizierung:	MacBook5,1
>>  Prozessortyp:	Intel Core 2 Duo
>>  Prozessorgeschwindigkeit:	2,4 GHz
>>  Anzahl der Prozessoren:	1
>>  Gesamtzahl der Kerne:	2
>>  L2-Cache:	3 MB
>>  Speicher:	4 GB
>>  Busgeschwindigkeit:	1,07 GHz
>>  Boot-ROM-Version:	MB51.0073.B06
>>  SMC-Version (System):	1.32f8
>>  ...
>>
>> what todo?
>>
>> Thank you
>>
>> Juergen Dabel
>> Schrobenhausen
>> Germany
>> j.dabel at t-online.de
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From lsansonetti at apple.com  Thu Oct  8 11:26:29 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 08 Oct 2009 11:26:29 -0700
Subject: [MacRuby-devel] 0.5 beta1
In-Reply-To: <8917EF70-DA43-40AC-A3B2-EF2445200EA9@gmail.com>
References: <10D89579-6FA0-44EE-A995-73895E38A9FF@t-online.de>
	<0033CCD7-35FB-4BC1-B7A8-67FC3292A343@apple.com>
	<8917EF70-DA43-40AC-A3B2-EF2445200EA9@gmail.com>
Message-ID: <B56D8D2F-D5DB-44FB-907B-24AE0F321CE9@apple.com>

I believe nightly builds have the same problem :(

Laurent

On Oct 8, 2009, at 11:21 AM, Claudio Poli wrote:

> or nightly build perhaps? ;P
>
> Il giorno 08/ott/2009, alle ore 19.59, Laurent Sansonetti ha scritto:
>
>> Hi Juergen,
>>
>> Looks like we forgot to bundle llc in the installer, sorry.
>>
>> We will make sure this is fixed by the next beta. In the meantime  
>> you can install trunk manually (see README.rdoc file for  
>> instructions).
>>
>> Laurent
>>
>> On Oct 8, 2009, at 8:44 AM, Juergen Dabel wrote:
>>
>>> Help,
>>>
>>> I get from the blog sample:
>>>
>>> dab:~ jdabel$ macrubyc t.rb -o t
>>> Can't locate program `llc'
>>>
>>> My mac:
>>> Hardware-?bersicht:
>>>
>>> Modellname:	MacBook
>>> Modell-Identifizierung:	MacBook5,1
>>> Prozessortyp:	Intel Core 2 Duo
>>> Prozessorgeschwindigkeit:	2,4 GHz
>>> Anzahl der Prozessoren:	1
>>> Gesamtzahl der Kerne:	2
>>> L2-Cache:	3 MB
>>> Speicher:	4 GB
>>> Busgeschwindigkeit:	1,07 GHz
>>> Boot-ROM-Version:	MB51.0073.B06
>>> SMC-Version (System):	1.32f8
>>> ...
>>>
>>> what todo?
>>>
>>> Thank you
>>>
>>> Juergen Dabel
>>> Schrobenhausen
>>> Germany
>>> j.dabel at t-online.de
>>>
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From masterkain at gmail.com  Thu Oct  8 11:31:05 2009
From: masterkain at gmail.com (Claudio Poli)
Date: Thu, 8 Oct 2009 20:31:05 +0200
Subject: [MacRuby-devel] 0.5 beta1
In-Reply-To: <B56D8D2F-D5DB-44FB-907B-24AE0F321CE9@apple.com>
References: <10D89579-6FA0-44EE-A995-73895E38A9FF@t-online.de>
	<0033CCD7-35FB-4BC1-B7A8-67FC3292A343@apple.com>
	<8917EF70-DA43-40AC-A3B2-EF2445200EA9@gmail.com>
	<B56D8D2F-D5DB-44FB-907B-24AE0F321CE9@apple.com>
Message-ID: <C2BA7B92-838B-4869-B0C8-4442741F7BBF@gmail.com>

ah, nevermind then, works on my local machine tho :)

Il giorno 08/ott/2009, alle ore 20.26, Laurent Sansonetti ha scritto:

> I believe nightly builds have the same problem :(
>
> Laurent
>
> On Oct 8, 2009, at 11:21 AM, Claudio Poli wrote:
>
>> or nightly build perhaps? ;P
>>
>> Il giorno 08/ott/2009, alle ore 19.59, Laurent Sansonetti ha scritto:
>>
>>> Hi Juergen,
>>>
>>> Looks like we forgot to bundle llc in the installer, sorry.
>>>
>>> We will make sure this is fixed by the next beta. In the meantime  
>>> you can install trunk manually (see README.rdoc file for  
>>> instructions).
>>>
>>> Laurent
>>>
>>> On Oct 8, 2009, at 8:44 AM, Juergen Dabel wrote:
>>>
>>>> Help,
>>>>
>>>> I get from the blog sample:
>>>>
>>>> dab:~ jdabel$ macrubyc t.rb -o t
>>>> Can't locate program `llc'
>>>>
>>>> My mac:
>>>> Hardware-?bersicht:
>>>>
>>>> Modellname:	MacBook
>>>> Modell-Identifizierung:	MacBook5,1
>>>> Prozessortyp:	Intel Core 2 Duo
>>>> Prozessorgeschwindigkeit:	2,4 GHz
>>>> Anzahl der Prozessoren:	1
>>>> Gesamtzahl der Kerne:	2
>>>> L2-Cache:	3 MB
>>>> Speicher:	4 GB
>>>> Busgeschwindigkeit:	1,07 GHz
>>>> Boot-ROM-Version:	MB51.0073.B06
>>>> SMC-Version (System):	1.32f8
>>>> ...
>>>>
>>>> what todo?
>>>>
>>>> Thank you
>>>>
>>>> Juergen Dabel
>>>> Schrobenhausen
>>>> Germany
>>>> j.dabel at t-online.de
>>>>
>>>>
>>>> _______________________________________________
>>>> MacRuby-devel mailing list
>>>> MacRuby-devel at lists.macosforge.org
>>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From deleeuw at stat.ucla.edu  Thu Oct  8 11:52:44 2009
From: deleeuw at stat.ucla.edu (Jan de Leeuw)
Date: Thu, 8 Oct 2009 11:52:44 -0700
Subject: [MacRuby-devel] not 32bit
Message-ID: <52A8D7C9-1F85-4C2A-B807-0FAE3A428E60@stat.ucla.edu>


Can I use rake to compile MacRuby for x86_64 only (my LLVM is
x86_64 only) ?

==========================================================
Jan de Leeuw, 11667 Steinhoff Rd, Frazier Park, CA 93225, 661-245-1725
.mac: jdeleeuw ++++++  aim: deleeuwjan ++++++ skype: j_deleeuw
homepages: http://www.cuddyvalley.org and http://gifi.stat.ucla.edu
==========================================================
               A bath when you're born,
          a bath when you die, 
               how stupid.          (Issa 1763-1827)




From lsansonetti at apple.com  Thu Oct  8 11:56:51 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 08 Oct 2009 11:56:51 -0700
Subject: [MacRuby-devel] not 32bit
In-Reply-To: <52A8D7C9-1F85-4C2A-B807-0FAE3A428E60@stat.ucla.edu>
References: <52A8D7C9-1F85-4C2A-B807-0FAE3A428E60@stat.ucla.edu>
Message-ID: <B59BFAD8-E1FA-4C11-BB6B-B2A70B019D2C@apple.com>

Try:

$ rake archs=x86_64

This used to work but I haven't checked since a long time :)

Note that MacRuby is only known to work under a certain revision of  
LLVM trunk (which is documented in the README.rdoc file).

Laurent

On Oct 8, 2009, at 11:52 AM, Jan de Leeuw wrote:

>
> Can I use rake to compile MacRuby for x86_64 only (my LLVM is
> x86_64 only) ?
>
> ==========================================================
> Jan de Leeuw, 11667 Steinhoff Rd, Frazier Park, CA 93225, 661-245-1725
> .mac: jdeleeuw ++++++  aim: deleeuwjan ++++++ skype: j_deleeuw
> homepages: http://www.cuddyvalley.org and http://gifi.stat.ucla.edu
> ==========================================================
>               A bath when you're born,
>          a bath when you die,
>               how stupid.          (Issa 1763-1827)
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From diego.virasoro at gmail.com  Thu Oct  8 09:38:00 2009
From: diego.virasoro at gmail.com (Diego Virasoro)
Date: Thu, 8 Oct 2009 17:38:00 +0100
Subject: [MacRuby-devel] macruby in a bubble
Message-ID: <2dfa27320910080938x38bbe985tc1aeeecf0bb1c971@mail.gmail.com>

Hello,
I'd like to try MacRuby (especially now that 0.5 beta 1 is out).
However I really really _really_ like to avoid having programs spread
their files across my fs. So, the questions are:
1) Is it possible to install macruby inside a specified directory?
2) Are any other files modified (say the .profile to extend the $PATH,
or others)?
3) Especially if the answer to 1) is negative, is there a script file
to erase/uninstall macruby?

Thanks and congrats for an awsome project

Diego

From lsansonetti at apple.com  Thu Oct  8 13:36:59 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 08 Oct 2009 13:36:59 -0700
Subject: [MacRuby-devel] macruby in a bubble
In-Reply-To: <2dfa27320910080938x38bbe985tc1aeeecf0bb1c971@mail.gmail.com>
References: <2dfa27320910080938x38bbe985tc1aeeecf0bb1c971@mail.gmail.com>
Message-ID: <A8C49798-43CC-4D26-BDC8-168844B548C8@apple.com>

Hi,

MacRuby installs itself inside a .framework bundle, in /Library/ 
Frameworks. It installs aliases to the executables in /usr/local/bin.  
Aliases have the "mac" prefix (irb -> macirb) to make sure MacRuby  
will not conflict with your system.

So, no system file is modified during installation. If you want to  
remove MacRuby after, you can simply delete /Library/Frameworks/ 
MacRuby.framework and /usr/local/bin/mac*.

Laurent

On Oct 8, 2009, at 9:38 AM, Diego Virasoro wrote:

> Hello,
> I'd like to try MacRuby (especially now that 0.5 beta 1 is out).
> However I really really _really_ like to avoid having programs spread
> their files across my fs. So, the questions are:
> 1) Is it possible to install macruby inside a specified directory?
> 2) Are any other files modified (say the .profile to extend the $PATH,
> or others)?
> 3) Especially if the answer to 1) is negative, is there a script file
> to erase/uninstall macruby?
>
> Thanks and congrats for an awsome project
>
> Diego
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From lsansonetti at apple.com  Thu Oct  8 13:39:54 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 08 Oct 2009 13:39:54 -0700
Subject: [MacRuby-devel] MacRuby 0.5 beta 1
In-Reply-To: <237413E7-69DB-4E7B-844E-7DD33C2B5ECE@gmail.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
	<237413E7-69DB-4E7B-844E-7DD33C2B5ECE@gmail.com>
Message-ID: <8B29EBD6-6741-4E13-BB72-F7D858AB60C6@apple.com>

Hi Wayne,

a) I don't know. Maybe pkgutil(1) can do that.

b) You can do `DESTDIR=~/.rvm/macruby-0.5b1 rake install' but you  
might need to configure some environment variables after (such as  
DYLD_FRAMEWORK_PATH). Note that this has never been tested.

Laurent

On Oct 8, 2009, at 3:36 AM, Wayne Seguin wrote:

> Excellent,
>
> Is it possible to a) install from command line and b) tell it to  
> install to a specific location?
> (--prefix=~/.rvm/macruby-0.5b1)
>
> Thanks,
>
>  ~Wayne
>
> On Oct 08, 2009, at 00:13 , Laurent Sansonetti wrote:
>
>> Hi,
>>
>> The first beta release of MacRuby 0.5 is out! I prepared some notes  
>> here:
>>
>> http://www.macruby.org/blog/2009/10/07/macruby05b1.html
>>
>> The goal is to go through a few beta releases before releasing the  
>> final 0.5.
>>
>> Please give it a try and report us bugs & feedback :)
>>
>> Laurent
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From wayneeseguin at gmail.com  Thu Oct  8 13:59:11 2009
From: wayneeseguin at gmail.com (Wayne Seguin)
Date: Thu, 8 Oct 2009 16:59:11 -0400
Subject: [MacRuby-devel] MacRuby 0.5 beta 1
In-Reply-To: <8B29EBD6-6741-4E13-BB72-F7D858AB60C6@apple.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
	<237413E7-69DB-4E7B-844E-7DD33C2B5ECE@gmail.com>
	<8B29EBD6-6741-4E13-BB72-F7D858AB60C6@apple.com>
Message-ID: <E15349A4-FCC9-4B5E-B4B0-976366A35EF1@gmail.com>

Laurent,

Thank you very much for the response. b) is *exactly* what I am  
looking for as it is all that inhibits me from adding macvim support  
to rvm. If someone has step by step instructions to do exactly this it  
would be awesomely helpful, otherwise I will try to look into it when  
I have some free time.

Great work with MacRuby, nicely done.

Thanks again!

   ~Wayne

On Oct 08, 2009, at 16:39 , Laurent Sansonetti wrote:
> Hi Wayne,
>
> a) I don't know. Maybe pkgutil(1) can do that.
>
> b) You can do `DESTDIR=~/.rvm/macruby-0.5b1 rake install' but you  
> might need to configure some environment variables after (such as  
> DYLD_FRAMEWORK_PATH). Note that this has never been tested.
>
> Laurent
>
> On Oct 8, 2009, at 3:36 AM, Wayne Seguin wrote:
>
>> Excellent,
>>
>> Is it possible to a) install from command line and b) tell it to  
>> install to a specific location?
>> (--prefix=~/.rvm/macruby-0.5b1)
>>
>> Thanks,
>>
>> ~Wayne
>>
>> On Oct 08, 2009, at 00:13 , Laurent Sansonetti wrote:
>>
>>> Hi,
>>>
>>> The first beta release of MacRuby 0.5 is out! I prepared some  
>>> notes here:
>>>
>>> http://www.macruby.org/blog/2009/10/07/macruby05b1.html
>>>
>>> The goal is to go through a few beta releases before releasing the  
>>> final 0.5.
>>>
>>> Please give it a try and report us bugs & feedback :)
>>>
>>> Laurent
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From prabhaka at apple.com  Thu Oct  8 14:25:00 2009
From: prabhaka at apple.com (Ernest N. Prabhakar, Ph.D.)
Date: Thu, 08 Oct 2009 14:25:00 -0700
Subject: [MacRuby-devel] install from command line Re:  MacRuby 0.5 beta 1
In-Reply-To: <E15349A4-FCC9-4B5E-B4B0-976366A35EF1@gmail.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
	<237413E7-69DB-4E7B-844E-7DD33C2B5ECE@gmail.com>
	<8B29EBD6-6741-4E13-BB72-F7D858AB60C6@apple.com>
	<E15349A4-FCC9-4B5E-B4B0-976366A35EF1@gmail.com>
Message-ID: <9A438C13-69EC-45D0-BB11-377EE1E52098@apple.com>

Hi Wayne,

On Oct 8, 2009, at 1:59 PM, Wayne Seguin wrote:
>>> Is it possible to a) install from command line
>> 

$ unzip ~/Downloads/MacRuby\ 0.5\ beta\ 1.zip 
$ cd ~/Downloads/MacRuby\ 0.5\ beta\ 1
$ sudo installer -pkg MacRuby\ 0.5\ beta\ 1.pkg  -target /

>> b) tell it to install to a specific location?
> 

Not sure how much flexibility you have with "-target", but you can try...

-enp


From occam at mac.com  Thu Oct  8 14:36:52 2009
From: occam at mac.com (Joseph Grace)
Date: Thu, 08 Oct 2009 14:36:52 -0700
Subject: [MacRuby-devel] FYI: official macruby git now available at
 git://git.macruby.org/macruby/MacRuby.git
Message-ID: <98554877323637228261249143534338622484-Webmail@me.com>

FYI: 

official macruby git is now available at: 

   git://git.macruby.org/macruby/MacRuby.git 

For more information, see: 

    https://www.macosforge.org/ 

Cheers, 

= Joe = 


From lsansonetti at apple.com  Thu Oct  8 16:19:29 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 08 Oct 2009 16:19:29 -0700
Subject: [MacRuby-devel] install from command line Re: MacRuby 0.5 beta 1
In-Reply-To: <9A438C13-69EC-45D0-BB11-377EE1E52098@apple.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
	<237413E7-69DB-4E7B-844E-7DD33C2B5ECE@gmail.com>
	<8B29EBD6-6741-4E13-BB72-F7D858AB60C6@apple.com>
	<E15349A4-FCC9-4B5E-B4B0-976366A35EF1@gmail.com>
	<9A438C13-69EC-45D0-BB11-377EE1E52098@apple.com>
Message-ID: <2A672E30-F65C-40EF-B8AA-C6394C3A7330@apple.com>

Hi Ernie,

On Oct 8, 2009, at 2:25 PM, Ernest N. Prabhakar, Ph.D. wrote:

> Hi Wayne,
>
> On Oct 8, 2009, at 1:59 PM, Wayne Seguin wrote:
>>>> Is it possible to a) install from command line
>>>
>
> $ unzip ~/Downloads/MacRuby\ 0.5\ beta\ 1.zip
> $ cd ~/Downloads/MacRuby\ 0.5\ beta\ 1
> $ sudo installer -pkg MacRuby\ 0.5\ beta\ 1.pkg  -target /

I totally didn't know about that.

Anyone to create a macruby_update_nightly script that would fetch the  
latest nightly build and merge it ? :)

Laurent

From wayneeseguin at gmail.com  Thu Oct  8 18:45:50 2009
From: wayneeseguin at gmail.com (Wayne Seguin)
Date: Thu, 8 Oct 2009 21:45:50 -0400
Subject: [MacRuby-devel] install from command line Re: MacRuby 0.5 beta 1
In-Reply-To: <9A438C13-69EC-45D0-BB11-377EE1E52098@apple.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
	<237413E7-69DB-4E7B-844E-7DD33C2B5ECE@gmail.com>
	<8B29EBD6-6741-4E13-BB72-F7D858AB60C6@apple.com>
	<E15349A4-FCC9-4B5E-B4B0-976366A35EF1@gmail.com>
	<9A438C13-69EC-45D0-BB11-377EE1E52098@apple.com>
Message-ID: <EA860485-183A-4349-B5DC-862767BCD4CE@gmail.com>

Ernst,

Thank you VERY much, I will give this a try first thing tomorrow  
morning!!!

Very much appreciated!

   ~Wayne

On Oct 08, 2009, at 17:25 , Ernest N. Prabhakar, Ph.D. wrote:

> Hi Wayne,
>
> On Oct 8, 2009, at 1:59 PM, Wayne Seguin wrote:
>>>> Is it possible to a) install from command line
>>>
>
> $ unzip ~/Downloads/MacRuby\ 0.5\ beta\ 1.zip
> $ cd ~/Downloads/MacRuby\ 0.5\ beta\ 1
> $ sudo installer -pkg MacRuby\ 0.5\ beta\ 1.pkg  -target /
>
>>> b) tell it to install to a specific location?
>>
>
> Not sure how much flexibility you have with "-target", but you can  
> try...
>
> -enp
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From paul-lists at tdgq.com.au  Thu Oct  8 19:08:05 2009
From: paul-lists at tdgq.com.au (Paul Howson)
Date: Fri, 9 Oct 2009 12:08:05 +1000
Subject: [MacRuby-devel] not 32bit
In-Reply-To: <B59BFAD8-E1FA-4C11-BB6B-B2A70B019D2C@apple.com>
References: <52A8D7C9-1F85-4C2A-B807-0FAE3A428E60@stat.ucla.edu>
	<B59BFAD8-E1FA-4C11-BB6B-B2A70B019D2C@apple.com>
Message-ID: <3C6207B7-6540-445B-8BC0-8FCD57573983@tdgq.com.au>

On 09/10/2009, at 4:56 AM, Laurent Sansonetti wrote:

> Note that MacRuby is only known to work under a certain revision of  
> LLVM trunk (which is documented in the README.rdoc file).

Does the MacRuby installer also install LLVM? If not, how is that kept  
up to date?

Paul Howson
Queensland, Australia.

From mred at dharmagaia.com  Thu Oct  8 19:47:20 2009
From: mred at dharmagaia.com (Edward Hynes)
Date: Thu, 8 Oct 2009 22:47:20 -0400
Subject: [MacRuby-devel] MacRuby not finding a method that Ruby is
In-Reply-To: <9DE16C12-3F71-480F-AC55-260A74DCB485@apple.com>
References: <7B512C30-87C0-4E0B-8D47-15A8D7E5B0DF@dharmagaia.com>
	<20fefa50910071951v18f12378yf64318d49c02197f@mail.gmail.com>
	<6AA0F2B6-0053-4978-91AC-39BB9FF03B8D@dharmagaia.com>
	<9DE16C12-3F71-480F-AC55-260A74DCB485@apple.com>
Message-ID: <EE2D89E7-CDE6-48F7-AA28-29FDD910D01E@dharmagaia.com>

Hi Laurent,

I just tried running it under 0.5 and am still getting an error.  I've  
narrowed the code down to the following:

###

  class A
    def initialize
      puts 'initialize'
    end

    def self.init
      define_method(:initialize) do |*params|
        super()
      end
    end
  end

  class B < A
    init
  end

  # Calling B.new without an argument, however, works.
  B.new nil

###

HTH,
Ed

On Oct 8, 2009, at 12:21 AM, Laurent Sansonetti wrote:

> We fixed a few 32-bit issues in trunk so you may want to give it a  
> try one more time.
>
> At least we are not maintaining 0.4 anymore, so it would be great if  
> you could try your code with trunk and let us know if the bug is  
> still there. Then we can try to reduce it and fix it :)
>
> Laurent
>
> On Oct 7, 2009, at 9:16 PM, Edward Hynes wrote:
>
>> I'm still on a 32-bit machine, so can't try 0.5 yet :^(
>>
>> I did manage to find a workaround, however, by creating an alias  
>> for the 'initialize' method and then calling it instead of 'super'  
>> inside of the 'define_method' call.
>>
>> Ed
>>
>> On Oct 7, 2009, at 10:51 PM, Matt Aimonetti wrote:
>>
>>> you might want to try your luck with 0.5
>>>
>>> - Matt
>>>
>>> On Wed, Oct 7, 2009 at 7:37 PM, Edward Hynes <mred at dharmagaia.com>  
>>> wrote:
>>> Hi,
>>>
>>> I'm attempting to use the RParsec gem under MacRuby, but am  
>>> getting a NoMethodError when it loads.  I've create a test file  
>>> that simply adds my local gem directory to the front of the  
>>> library search path and then calls "require 'rparsec'".  This file  
>>> runs fine under Ruby 1.9, but produces the following error when  
>>> called from MacRuby 0.4.
>>>
>>> /Users/ehynes/Test/Gems/rparsec/parser.rb:32:in `block in init':  
>>> super: no superclass method `initialize:' for  
>>> RParsec::ValueParser:RParsec::ValueParser (NoMethodError)
>>>       from /Users/ehynes/Test/Gems/rparsec/parsers.rb:621:in `new'
>>>       from /Users/ehynes/Test/Gems/rparsec/parsers.rb:621:in  
>>> `<module:RParsec>'
>>>       from /Users/ehynes/Test/Gems/rparsec/parsers.rb:3:in `<top  
>>> (required)>'
>>>       from /Users/ehynes/Test/Gems/rparsec.rb:3:in `require'
>>>       from /Users/ehynes/Test/Gems/rparsec.rb:3:in `block in <top  
>>> (required)>'
>>>       from /Users/ehynes/Test/Gems/rparsec.rb:2:in `each'
>>>       from /Users/ehynes/Test/Gems/rparsec.rb:2:in `<top (required) 
>>> >'
>>>       from AbcParser.rb:2:in `require'
>>>       from AbcParser.rb:2:in `<main>'
>>>
>>>
>>> The method with the error in the Parser class is:
>>>
>>> def self.init(*vars)
>>>   parser_checker = {}
>>>   vars.each_with_index do |var, i|
>>>     name = var.to_s
>>>     parser_checker[i] = var if name.include?('parser') && ! 
>>> name.include?('parsers')
>>>   end
>>>   define_method(:initialize) do |*params|
>>> --->  super()   # <--- line 32
>>>     vars.each_with_index do |var, i|
>>>       param = params[i]
>>>       if parser_checker.include? i
>>>         TypeChecker.check_arg_type Parser, param, self, i
>>>       end
>>>       instance_variable_set("@"+var.to_s, param)
>>>     end
>>>   end
>>> end
>>>
>>>
>>> Any ideas as to why Ruby can call super in the above method, but  
>>> MacRuby can't?  Is there a fix or workaround that I could use?  An  
>>> alternate parser?
>>>
>>> Thanks,
>>> Ed
>>>
>>>
>>> P.S.  I did have to change one line in the RParsec parser.rb file  
>>> to get it to run under Ruby 1.9, replacing a ':' with a 'then' in  
>>> a case statement.
>>>
>>>       $ diff parser_original.rb parser.rb
>>>       881c881
>>>       <     case c when String: c[0] else c end
>>>       ---
>>>       >     case c when String then c[0] else c end  # ':'  
>>> replaced with 'then'
>>>
>>>
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> -- 
>> Edward Hynes
>> Dharma Gaia LLC
>> "Software with the Earth in Mind"
>> http://dharmagaia.com
>>
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-- 
Edward Hynes
Dharma Gaia LLC
"Software with the Earth in Mind"
http://dharmagaia.com




From joshua.ballanco at apple.com  Thu Oct  8 22:58:03 2009
From: joshua.ballanco at apple.com (Josh Ballanco)
Date: Thu, 8 Oct 2009 22:58:03 -0700
Subject: [MacRuby-devel] Default Test Framework
Message-ID: <45103AB5-C61F-4229-BF50-952C72666B96@apple.com>

Hey all!

So, as I've been working on a recipe for testing with MacRuby, I  
realized that it would probably be good to discuss the topic of  
"blessing" a particular test suite. Obviously, with macgem all of the  
Ruby test suites are available to use, but for the purposes of  
tutorials and whatnot, having one default that ships with MacRuby  
would help reduce confusion and at least get people started on the  
road to testing. Personally, I think whatever ships with MacRuby  
should ideally be light-weight, extensible, and integrated. In other  
words, the heavy hitters like Test::Unit, RSpec, and Shoulda are out.  
That leaves:

-- minitest: The "blessed" test library of Matz Ruby. It's very  
minimal, but documentation is somewhat lacking. I also couldn't find  
an easy spot to hook into the API to customize output format. Still,  
if it's good enough for Matz Ruby...

-- bacon: Small, and output is easily customized. I'm currently  
looking at what would be required to get bacon's output to play nicer  
with Xcode. The one unknown (for me, at least) is popularity/ 
familiarity in the larger Ruby community.

-- OCUnit: This is the Objective C test library that ships with Xcode.  
We could put a thin wrapper around it, and then not worry about having  
to ship a separate test library. The major downside to OCUnit is that  
it's not very "Ruby-ish".

I'm quite enamored with bacon, but I'm worried about the possibility  
that developers coming from Matz Ruby might start to expect minitest  
to be included. That might be a remote possibility, though, as it  
seems like minitest isn't currently that popular. If there are others  
I missed, or if you disagree with any points, speak up!

Cheers,

Josh

From eloy.de.enige at gmail.com  Fri Oct  9 00:55:00 2009
From: eloy.de.enige at gmail.com (Eloy Duran)
Date: Fri, 9 Oct 2009 09:55:00 +0200
Subject: [MacRuby-devel] Default Test Framework
In-Reply-To: <45103AB5-C61F-4229-BF50-952C72666B96@apple.com>
References: <45103AB5-C61F-4229-BF50-952C72666B96@apple.com>
Message-ID: <B262BF28-E665-4D43-BD92-D968579AAC92@gmail.com>

Hi,

As we're targeting 1.9 compatibility, the library that will be shipped  
with MacRuby is minitest. Atm however, we still have an older version  
of the stdlib, which means we still ship test-unit.

I myself have put my trust in Bacon, and as far as a "blessing" goes,  
all critical bugs encountered with Bacon have been fixed.

Eloy

On 9 okt 2009, at 07:58, Josh Ballanco wrote:

> Hey all!
>
> So, as I've been working on a recipe for testing with MacRuby, I  
> realized that it would probably be good to discuss the topic of  
> "blessing" a particular test suite. Obviously, with macgem all of  
> the Ruby test suites are available to use, but for the purposes of  
> tutorials and whatnot, having one default that ships with MacRuby  
> would help reduce confusion and at least get people started on the  
> road to testing. Personally, I think whatever ships with MacRuby  
> should ideally be light-weight, extensible, and integrated. In other  
> words, the heavy hitters like Test::Unit, RSpec, and Shoulda are  
> out. That leaves:
>
> -- minitest: The "blessed" test library of Matz Ruby. It's very  
> minimal, but documentation is somewhat lacking. I also couldn't find  
> an easy spot to hook into the API to customize output format. Still,  
> if it's good enough for Matz Ruby...
>
> -- bacon: Small, and output is easily customized. I'm currently  
> looking at what would be required to get bacon's output to play  
> nicer with Xcode. The one unknown (for me, at least) is popularity/ 
> familiarity in the larger Ruby community.
>
> -- OCUnit: This is the Objective C test library that ships with  
> Xcode. We could put a thin wrapper around it, and then not worry  
> about having to ship a separate test library. The major downside to  
> OCUnit is that it's not very "Ruby-ish".
>
> I'm quite enamored with bacon, but I'm worried about the possibility  
> that developers coming from Matz Ruby might start to expect minitest  
> to be included. That might be a remote possibility, though, as it  
> seems like minitest isn't currently that popular. If there are  
> others I missed, or if you disagree with any points, speak up!
>
> Cheers,
>
> Josh
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From masterkain at gmail.com  Fri Oct  9 01:00:36 2009
From: masterkain at gmail.com (Claudio Poli)
Date: Fri, 9 Oct 2009 10:00:36 +0200
Subject: [MacRuby-devel] install from command line Re: MacRuby 0.5 beta 1
In-Reply-To: <2A672E30-F65C-40EF-B8AA-C6394C3A7330@apple.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
	<237413E7-69DB-4E7B-844E-7DD33C2B5ECE@gmail.com>
	<8B29EBD6-6741-4E13-BB72-F7D858AB60C6@apple.com>
	<E15349A4-FCC9-4B5E-B4B0-976366A35EF1@gmail.com>
	<9A438C13-69EC-45D0-BB11-377EE1E52098@apple.com>
	<2A672E30-F65C-40EF-B8AA-C6394C3A7330@apple.com>
Message-ID: <5AA624F9-382F-4CBB-ADA2-6A8486D650A3@gmail.com>

don't know what you mean with merge it, however there are apis to ease  
the download:
http://macruby.icoretech.org/api

a curl -O http://macruby.icoretech.org/latest/macruby_nightly- 
latest.pkg should suffice :)

claudio

Il giorno 09/ott/2009, alle ore 01.19, Laurent Sansonetti ha scritto:

> Hi Ernie,
>
> On Oct 8, 2009, at 2:25 PM, Ernest N. Prabhakar, Ph.D. wrote:
>
>> Hi Wayne,
>>
>> On Oct 8, 2009, at 1:59 PM, Wayne Seguin wrote:
>>>>> Is it possible to a) install from command line
>>>>
>>
>> $ unzip ~/Downloads/MacRuby\ 0.5\ beta\ 1.zip
>> $ cd ~/Downloads/MacRuby\ 0.5\ beta\ 1
>> $ sudo installer -pkg MacRuby\ 0.5\ beta\ 1.pkg  -target /
>
> I totally didn't know about that.
>
> Anyone to create a macruby_update_nightly script that would fetch  
> the latest nightly build and merge it ? :)
>
> Laurent
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From jread at dodgydev.net  Fri Oct  9 01:01:41 2009
From: jread at dodgydev.net (Jesse Read)
Date: Fri, 9 Oct 2009 04:01:41 -0400
Subject: [MacRuby-devel] Empty Ruby Template
Message-ID: <5133d9390910090101u7136e67bl8ac85c4d79d4b580@mail.gmail.com>

I saw in the trunk status update, this line:
"- Added an empty Ruby template file"

Which I believes corresponds to
this<https://www.macruby.org/trac/changeset/2721> changeset
on Trac, where Matt added an Xcode Ruby file template.

I manually installed the template, but are there any plans to add these into
the installers, either for 0.5b2 or the nightlies? I doubt much will change
with them, but other would probably enjoy them if they see them installed.

Thanks, and keep up the great work!

? Jesse
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091009/e94952b2/attachment.html>

From jkh at apple.com  Fri Oct  9 01:02:14 2009
From: jkh at apple.com (Jordan K. Hubbard)
Date: Fri, 9 Oct 2009 01:02:14 -0700
Subject: [MacRuby-devel] MacRuby 0.5 beta
In-Reply-To: <B262BF28-E665-4D43-BD92-D968579AAC92@gmail.com>
References: <45103AB5-C61F-4229-BF50-952C72666B96@apple.com>
	<B262BF28-E665-4D43-BD92-D968579AAC92@gmail.com>
Message-ID: <16BF2825-6C57-46F0-B39D-5AF0A3503FD9@apple.com>

Just judging by the initial round of twitter / blog postings, the #1  
problem people are having trouble with 0.5B1 is obtaining LLVM.    
Antonio has already put together a nice blog posting about it (http://antoniocangiano.com/2009/10/08/getting-macrubys-compiler-to-work/ 
), but shouldn't his instructions be on the MacRuby blog, seeing as  
how Laurent's announcement is the first thing many people are going to  
see?  Even better, maybe an LLVM package to go along with MacRuby,  
also linked to on the site?  Given that you need a very specific (e.g.  
recent, from trunk) version of LLVM for MacRuby to work at all, this  
seems pretty reasonable.  If the instructions were "just go grab llvm  
2.6" then I might feel differently.

- Jordan


From vincent.isambart at gmail.com  Fri Oct  9 01:24:21 2009
From: vincent.isambart at gmail.com (Vincent Isambart)
Date: Fri, 9 Oct 2009 17:24:21 +0900
Subject: [MacRuby-devel] MacRuby 0.5 beta
In-Reply-To: <16BF2825-6C57-46F0-B39D-5AF0A3503FD9@apple.com>
References: <45103AB5-C61F-4229-BF50-952C72666B96@apple.com>
	<B262BF28-E665-4D43-BD92-D968579AAC92@gmail.com>
	<16BF2825-6C57-46F0-B39D-5AF0A3503FD9@apple.com>
Message-ID: <7d9a1f530910090124m46a53033gb81fd93f8185536e@mail.gmail.com>

>?Even better, maybe an LLVM package to go along with MacRuby, also linked to
> on the site? ?Given that you need a very specific (e.g. recent, from trunk)
> version of LLVM for MacRuby to work at all, this seems pretty reasonable.

I think Laurent wants to include it directly in the next MacRuby installer.
Though I was just thinking we should be careful not to overwrite the
version of LLVM the user might have, putting our version in MacRuby's
directory, not at the place we MacRuby developers have it installed
currently (/usr/local).

> ?If the instructions were "just go grab llvm 2.6" then I might feel
> differently.

At first I was thinking we might be able to use the final 2.6, but
it's in a pretty bad shape. We could not use LLVM 2.5 because of
problems regarding exception handling. And it looks like we won't be
able to use LLVM 2.6 because of... problems regarding exception
handling...

From ruby-noreply at macosforge.org  Fri Oct  9 01:24:53 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 09 Oct 2009 08:24:53 -0000
Subject: [MacRuby-devel] [MacRuby] #370: Inconsistency between macruby and
 ruby in a simple class
Message-ID: <052.3daa3c7849cf67ac174b377fd7b472a3@macosforge.org>

#370: Inconsistency between macruby and ruby in a simple class
-----------------------------------+----------------------------------------
 Reporter:  kfowler@?              |       Owner:  lsansonetti@?        
     Type:  defect                 |      Status:  new                  
 Priority:  major                  |   Milestone:  MacRuby 0.5          
Component:  MacRuby                |    Keywords:                       
-----------------------------------+----------------------------------------
 running this script:
 {{{
 class W
   def initialize(w)
     @w = w
   end
 end

 class M
   def initialize(m)
     @m = m
   end
 end


 printf("%s\n" , W.new(W.new(1)).inspect)
 printf("%s\n" , M.new(M.new(1)).inspect)
 printf("%s\n" , W.new(M.new(1)).inspect)
 printf("%s\n" , M.new(W.new(1)).inspect)
 }}}

 on ruby1.9 from mac ports (ruby 1.9.1p243 (2009-07-16 revision 24175)
 [i386-darwin10]) yields this:
 {{{
 #<W:0x0000010084ecd8 @w=#<W:0x0000010084edf0 @w=1>>
 #<M:0x0000010084e370 @m=#<M:0x0000010084e3e0 @m=1>>
 #<W:0x0000010084dd88 @w=#<M:0x0000010084de30 @m=1>>
 #<M:0x0000010084d618 @m=#<W:0x0000010084d7a0 @w=1>>
 }}}

 on macruby 0.5 (MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0,
 x86_64]) built from source
 (http://svn.macosforge.org/repository/ruby/MacRuby/trunk at 2771) against
 llvm (https://llvm.org/svn/llvm-project/llvm/trunk at 82747) yields this:
 {{{
 ##-<W:0x20001cc00 @w=1>
 ##-<M:0x20001cfe0 @m=1>
 ##-<W:0x20001d260 @w=##-<M:0x20001d2a0 @m=1>>
 ##-<M:0x2000162a0 @m=##-<W:0x2000162e0 @w=1>>
 }}}

 Ruby 1.8.7 from 10.6:
 {{{
 #<W:0x1001558c8 @w=#<W:0x1001558f0 @w=1>>
 #<M:0x100155788 @m=#<M:0x1001557b0 @m=1>>
 #<W:0x100155670 @w=#<M:0x100155698 @m=1>>
 #<M:0x100155558 @m=#<W:0x100155580 @w=1>>
 }}}

 jruby 1.3.1:
 {{{
 #<W:0x141dddba @w=#<W:0x6d732ed2 @w=1>>
 #<M:0x60c9630a @m=#<M:0x4585572a @m=1>>
 #<W:0x351daa0e @w=#<M:0x2e879860 @m=1>>
 #<M:0x4824de7d @m=#<W:0x6c8b058b @w=1>>
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/370>
MacRuby <http://macruby.org/>


From mattaimonetti at gmail.com  Fri Oct  9 01:42:17 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Fri, 9 Oct 2009 01:42:17 -0700
Subject: [MacRuby-devel] Empty Ruby Template
In-Reply-To: <5133d9390910090101u7136e67bl8ac85c4d79d4b580@mail.gmail.com>
References: <5133d9390910090101u7136e67bl8ac85c4d79d4b580@mail.gmail.com>
Message-ID: <20fefa50910090142n5121ee8bi2a0309701213fcff@mail.gmail.com>

The file should be part of the nightly package. I have to admit I failed to
check tho.
Can you please check that it's not a right access instead of the file
missing from the package?

Thanks,

- Matt


On Fri, Oct 9, 2009 at 1:01 AM, Jesse Read <jread at dodgydev.net> wrote:

> I saw in the trunk status update, this line:
> "- Added an empty Ruby template file"
>
> Which I believes corresponds to this<https://www.macruby.org/trac/changeset/2721> changeset
> on Trac, where Matt added an Xcode Ruby file template.
>
> I manually installed the template, but are there any plans to add these
> into the installers, either for 0.5b2 or the nightlies? I doubt much will
> change with them, but other would probably enjoy them if they see them
> installed.
>
> Thanks, and keep up the great work!
>
> ? Jesse
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091009/238801ad/attachment.html>

From ruby-noreply at macosforge.org  Fri Oct  9 01:50:45 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 09 Oct 2009 08:50:45 -0000
Subject: [MacRuby-devel] [MacRuby] #370: Inconsistency between macruby
 and ruby in a simple class
In-Reply-To: <052.3daa3c7849cf67ac174b377fd7b472a3@macosforge.org>
References: <052.3daa3c7849cf67ac174b377fd7b472a3@macosforge.org>
Message-ID: <061.87a092ef6c9f6d806fe88032329360fd@macosforge.org>

#370: Inconsistency between macruby and ruby in a simple class
-----------------------------------+----------------------------------------
 Reporter:  kfowler@?              |       Owner:  lsansonetti@?        
     Type:  defect                 |      Status:  new                  
 Priority:  major                  |   Milestone:  MacRuby 0.5          
Component:  MacRuby                |    Keywords:                       
-----------------------------------+----------------------------------------

Comment(by kfowler@?):

 if I change M to extend W:
 {{{class M < W}}}...
 then I get:
 {{{
 ##-<W:0x2000166c0 @w=1>
 ##-<M:0x200016aa0 @m=1>
 ##-<M:0x200016e20 @m=1>
 ##-<M:0x200010980 @m=##-<W:0x2000109c0 @w=1>>
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/370#comment:1>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Fri Oct  9 01:56:09 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Fri, 09 Oct 2009 01:56:09 -0700
Subject: [MacRuby-devel] MacRuby 0.5 beta
In-Reply-To: <16BF2825-6C57-46F0-B39D-5AF0A3503FD9@apple.com>
References: <45103AB5-C61F-4229-BF50-952C72666B96@apple.com>
	<B262BF28-E665-4D43-BD92-D968579AAC92@gmail.com>
	<16BF2825-6C57-46F0-B39D-5AF0A3503FD9@apple.com>
Message-ID: <7A0E5CE4-8CBF-4027-A348-883EBD288434@apple.com>

Jordan,

Users should not need to obtain and install LLVM. MacRuby uses it  
statically. There was a mistake in the installer, we forgot to bundle  
llc (LLVM compiler tool) used by macrubyc, this will be fixed in the  
upcoming nightly builds then in the next beta.

Laurent

On Oct 9, 2009, at 1:02 AM, Jordan K. Hubbard wrote:

> Just judging by the initial round of twitter / blog postings, the #1  
> problem people are having trouble with 0.5B1 is obtaining LLVM.    
> Antonio has already put together a nice blog posting about it (http://antoniocangiano.com/2009/10/08/getting-macrubys-compiler-to-work/ 
> ), but shouldn't his instructions be on the MacRuby blog, seeing as  
> how Laurent's announcement is the first thing many people are going  
> to see?  Even better, maybe an LLVM package to go along with  
> MacRuby, also linked to on the site?  Given that you need a very  
> specific (e.g. recent, from trunk) version of LLVM for MacRuby to  
> work at all, this seems pretty reasonable.  If the instructions were  
> "just go grab llvm 2.6" then I might feel differently.
>
> - Jordan
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Fri Oct  9 02:18:22 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 09 Oct 2009 09:18:22 -0000
Subject: [MacRuby-devel] [MacRuby] #370: Inconsistency between macruby
 and ruby in a simple class
In-Reply-To: <052.3daa3c7849cf67ac174b377fd7b472a3@macosforge.org>
References: <052.3daa3c7849cf67ac174b377fd7b472a3@macosforge.org>
Message-ID: <061.bd6e14bd477107987850e0b4a99892af@macosforge.org>

#370: Inconsistency between macruby and ruby in a simple class
-----------------------------------+----------------------------------------
 Reporter:  kfowler@?              |       Owner:  lsansonetti@?        
     Type:  defect                 |      Status:  new                  
 Priority:  major                  |   Milestone:  MacRuby 0.5          
Component:  MacRuby                |    Keywords:                       
-----------------------------------+----------------------------------------

Comment(by kfowler@?):

 "return self" appears to be a work around:
 {{{
   def initialize(m)
     @m = m
     return self
   end
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/370#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct  9 04:05:16 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 09 Oct 2009 11:05:16 -0000
Subject: [MacRuby-devel] [MacRuby] #370: Inconsistency between macruby
 and ruby in a simple class
In-Reply-To: <052.3daa3c7849cf67ac174b377fd7b472a3@macosforge.org>
References: <052.3daa3c7849cf67ac174b377fd7b472a3@macosforge.org>
Message-ID: <061.8f891dc2afa6939504c9ea1b1d56317e@macosforge.org>

#370: Inconsistency between macruby and ruby in a simple class
-----------------------------------+----------------------------------------
 Reporter:  kfowler@?              |       Owner:  lsansonetti@?        
     Type:  defect                 |      Status:  new                  
 Priority:  major                  |   Milestone:  MacRuby 0.5          
Component:  MacRuby                |    Keywords:                       
-----------------------------------+----------------------------------------

Comment(by conradwt@?):

 Yes, there's seems to be an issue with the initialize method returning the
 instance to the caller.  However, you can rewrite the classes as follows
 and the initialize method seems to work as expected:

 {{{

 W = Class.new do
    define_method :initialize do |w|
       @w = w
    end
 end

 M = Class.new do
    define_method :initialize do |m|
       @m = m
    end
 end

 printf("%s\n" , W.new(W.new(1)).inspect)
 printf("%s\n" , M.new(M.new(1)).inspect)
 printf("%s\n" , W.new(M.new(1)).inspect)
 printf("%s\n" , M.new(W.new(1)).inspect)

 }}}

 Next, adding 'self' as the last executable statement within the
 'initialize' method provides a temporary workaround.  Finally, if I'm
 reading the code correctly, the function 'rb_class_new_instance0' within
 the 'object.c' file may be a starting point for resolving the issue.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/370#comment:3>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct  9 04:09:40 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 09 Oct 2009 11:09:40 -0000
Subject: [MacRuby-devel] [MacRuby] #371: Module methods included in the
 class Module are not visible to other classes.
Message-ID: <050.b29ce2179f990c014e2fd8737732541a@macosforge.org>

#371: Module methods included in the class Module are not visible to other
classes.
---------------------------------+------------------------------------------
 Reporter:  mred@?               |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------
 {{{
 module A
   def b
     puts 'b'
   end
 end

 class Module
   include A
 end

 class C
   b()
 end
 }}}

 Running the above on Ruby 1.9 prints out 'b'.  Running it on MacRuby 0.5
 generates an "undefined method `b' for C:Class (NoMethodError)"

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/371>
MacRuby <http://macruby.org/>


From hiroshi3110 at gmail.com  Fri Oct  9 04:22:21 2009
From: hiroshi3110 at gmail.com (hiroshi saito)
Date: Fri, 9 Oct 2009 20:22:21 +0900
Subject: [MacRuby-devel] Building MacRuby r2765 with llvm r82747 failed on
	core duo macbook, Leopard
Message-ID: <6e90f1240910090422g6c7a54cdxc7c521007fd1be60@mail.gmail.com>

Hi all,

I failed to build llvm r82747 and MacRuby r2765 following the
instruction of README.
I use core duo macbook and Leopard.

$ svn co -r 2765
http://svn.macosforge.org/repository/ruby/MacRuby/trunk MacRuby-trunk
$ svn co -r 82747 https://llvm.org/svn/llvm-project/llvm/trunk llvm-trunk
$ cd llvm-trunk
$ UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64" ENABLE_OPTIMIZED=1 make
...
llvm[2]: Compiling BasicBlockTracing.c for Release build (bytecode)
...
llvm-gcc-4.2: -E, -S, -save-temps and -M options are not allowed with
multiple -arch flags

To avoid the error, omited univsersal environment variables.

$ ENABLE_OPTIMIZED=1 make

It worked.

Next, build MacRuby itself. My llvm isn't universal binary anymore, so
I explicitly specified archs options;

$ PATH=$PATH:~/Desktop/wc/MacRuby/llvm-trunk/Release/bin rake archs=i386
...
/usr/bin/g++ -I/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include
-I/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include  -D_DEBUG
-D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -O3
-fno-common -Woverloaded-virtual -I. -I./include -g -Wall -arch i386
-Wno-parentheses -Wno-deprecated-declarations -Werror -Winline --param
inline-unit-growth=10000 --param large-function-growth=10000 -x
objective-c++ -c dispatcher.cpp -o dispatcher.o
cc1objplus: warnings being treated as errors
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:417:
warning: ?void llvm::PATypeHandle::addUser()? was used before it was
declared inline
...

I got warnings which stopped build. So added "allow_build_warnings=true";

$ PATH=$PATH:~/Desktop/wc/MacRuby/llvm-trunk/Release/bin rake
archs=i386 allow_build_warnings=true
...
./miniruby -I. -I./lib bin/rubyc --internal -C "rbconfig.rb" -o "./rbconfig.rbo"
terminate called after throwing an instance of 'RoxorReturnFromBlockException*'
rake aborted!

I stucked. I don't have any idea to avoid the exception yet.

Also, I tried some of ideas;
* use gcc-4.2 instead of default version of gcc 4.0 on Leopard, but
this doesn't seem to have any effect.
* append --disable-dependency-tracking to ./configure of llvm

Before continue to struggle, I want some help.
If someone succeeded to build MacRuby after releasing 0.5 beta1, please help me.
Or have any idea, I'll try it.

Thanks in advance.



====== Lines below are more details of the build fialures:

$ uname -a
Darwin hiroshi-macbook.local 9.8.0 Darwin Kernel Version 9.8.0: Wed
Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386
$ gcc -v
..
gcc version 4.0.1 (Apple Inc. build 5493)

$ svn co -r 2765
http://svn.macosforge.org/repository/ruby/MacRuby/trunk MacRuby-trunk
$ svn co -r 82747 https://llvm.org/svn/llvm-project/llvm/trunk llvm-trunk
$ cd llvm-trunk
$ ./configure
$ UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64" ENABLE_OPTIMIZED=1 make
...
llvm[2]: Compiling BasicBlockTracing.c for Release build (bytecode)
/Developer/usr/bin/llvm-gcc
-I/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include
-I/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/runtime/libprofile
-D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS
-O3  -fno-common   -mmacosx-version-min=10.5 -pedantic -Wno-long-long
-Wall -W -Wno-unused-parameter -Wwrite-strings  -arch i386 -arch
x86_64 BasicBlockTracing.c -o
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/runtime/libprofile/Release/BasicBlockTracing.ll
-S -emit-llvm
llvm-gcc-4.2: -E, -S, -save-temps and -M options are not allowed with
multiple -arch flags
make[2]: *** [/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/runtime/libprofile/Release/BasicBlockTracing.ll]
Error 1
make[1]: *** [libprofile/.makeall] Error 2
make: *** [all] Error 1

Instead of building llvm with multiple archs, I tried to build it
without universal flags:

$ ENABLE_OPTIMIZED=1 make

It works, but next, building macruby itself failed.

$ cd ..; cd MacRuby-trunk
$ PATH=$PATH:~/Desktop/wc/MacRuby/llvm-trunk/Release/bin rake archs=i386
...
/usr/bin/g++ -I/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include
-I/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include  -D_DEBUG
-D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -O3
-fno-common -Woverloaded-virtual -I. -I./include -g -Wall -arch i386
-Wno-parentheses -Wno-deprecated-declarations -Werror -Winline --param
inline-unit-growth=10000 --param large-function-growth=10000 -x
objective-c++ -c dispatcher.cpp -o dispatcher.o
cc1objplus: warnings being treated as errors
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:417:
warning: ?void llvm::PATypeHandle::addUser()? was used before it was
declared inline
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/AbstractTypeUser.h:95:
warning: previous non-inline declaration here
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:422:
warning: ?void llvm::PATypeHandle::removeUser()? was used before it
was declared inline
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/AbstractTypeUser.h:96:
warning: previous non-inline declaration here
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:434:
warning: ?llvm::Type* llvm::PATypeHolder::get() const? was used before
it was declared inline
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/AbstractTypeUser.h:159:
warning: previous non-inline declaration here
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:440:
warning: ?void llvm::PATypeHolder::addRef()? was used before it was
declared inline
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/AbstractTypeUser.h:182:
warning: previous non-inline declaration here
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:446:
warning: ?void llvm::PATypeHolder::dropRef()? was used before it was
declared inline
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/AbstractTypeUser.h:183:
warning: previous non-inline declaration here
rake aborted!

==========
Hiroshi Saito
hiroshi3110 at gmail.com
http://blog.yakitara.com/
http://github.com/hiroshi

From ruby-noreply at macosforge.org  Fri Oct  9 07:53:55 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 09 Oct 2009 14:53:55 -0000
Subject: [MacRuby-devel] [MacRuby] #372: Error while requiring rss module
Message-ID: <047.3b2f921f9c8845bbb26c1528e1e9e300@macosforge.org>

#372: Error while requiring rss module
------------------------------+---------------------------------------------
 Reporter:  dmlary@?          |       Owner:  lsansonetti@?          
     Type:  defect            |      Status:  new                    
 Priority:  minor             |   Milestone:  MacRuby 0.5            
Component:  MacRuby           |    Keywords:  rss, macruby 0.5 beta 1
------------------------------+---------------------------------------------
 Using macruby 0.5 beta 1,


 {{{
 ~> macruby --version
 MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
 ~> cat rss.rb
 require 'rss'
 ~> macruby rss.rb
 rss.rb:1:in `<main>': undefined method `split' for nil:NilClass
 (NoMethodError)
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/372>
MacRuby <http://macruby.org/>


From jread at dodgydev.net  Fri Oct  9 09:00:57 2009
From: jread at dodgydev.net (Jesse Read)
Date: Fri, 9 Oct 2009 12:00:57 -0400
Subject: [MacRuby-devel] Empty Ruby Template
In-Reply-To: <20fefa50910090142n5121ee8bi2a0309701213fcff@mail.gmail.com>
References: <5133d9390910090101u7136e67bl8ac85c4d79d4b580@mail.gmail.com>
	<20fefa50910090142n5121ee8bi2a0309701213fcff@mail.gmail.com>
Message-ID: <5133d9390910090900g71dc688aub300df906403fb63@mail.gmail.com>

I just checked the last nightly, and it only installs the following Xcode
templates:
/Library/Application Support/Developer/Xcode/3.0/Target Templates
/Library/Application Support/Developer/Xcode/3.0/Project Templates
/Library/Application Support/Developer/Xcode/Shared/Target Templates
/Library/Application Support/Developer/Xcode/Shared/Project Templates

No File Templates, I just manually copied the File Templates folder from
/misc/xcode-templates in trunk to the 3.0 and Shared folders, mimicking the
nightly installer.

? Jesse


On Fri, Oct 9, 2009 at 4:42 AM, Matt Aimonetti <mattaimonetti at gmail.com>wrote:

> The file should be part of the nightly package. I have to admit I failed to
> check tho.
> Can you please check that it's not a right access instead of the file
> missing from the package?
>
> Thanks,
>
> - Matt
>
>
> On Fri, Oct 9, 2009 at 1:01 AM, Jesse Read <jread at dodgydev.net> wrote:
>
>> I saw in the trunk status update, this line:
>> "- Added an empty Ruby template file"
>>
>> Which I believes corresponds to this<https://www.macruby.org/trac/changeset/2721> changeset
>> on Trac, where Matt added an Xcode Ruby file template.
>>
>> I manually installed the template, but are there any plans to add these
>> into the installers, either for 0.5b2 or the nightlies? I doubt much will
>> change with them, but other would probably enjoy them if they see them
>> installed.
>>
>> Thanks, and keep up the great work!
>>
>> ? Jesse
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091009/5eeeb07e/attachment.html>

From ruby-noreply at macosforge.org  Fri Oct  9 09:09:41 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 09 Oct 2009 16:09:41 -0000
Subject: [MacRuby-devel] [MacRuby] #371: Module methods included in the
 class Module are not visible to other classes.
In-Reply-To: <050.b29ce2179f990c014e2fd8737732541a@macosforge.org>
References: <050.b29ce2179f990c014e2fd8737732541a@macosforge.org>
Message-ID: <059.016ae5e14ed3d9586e2177e3713ce5b2@macosforge.org>

#371: Module methods included in the class Module are not visible to other
classes.
---------------------------------+------------------------------------------
 Reporter:  mred@?               |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------

Comment(by keith.gautreaux@?):

 It seems that MacRuby treats modules differently than Ruby 1.9.  You
 shouldn't be able to instantiate a named module using the new method, i.e.

 A = Module.new do
   def meth1
     "hello"
   end
 end

 a = A.new (shouldn't work)
 => NoMethodError: undefined method `new' for A:Module

 but it does in MacRuby returning an instance of A:Module which responds to
 the meth1 call
 => #<A:0x2003da160>

 a.meth1
 =>"hello"

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/371#comment:1>
MacRuby <http://macruby.org/>


From jkh at apple.com  Fri Oct  9 09:15:34 2009
From: jkh at apple.com (Jordan K. Hubbard)
Date: Fri, 9 Oct 2009 09:15:34 -0700
Subject: [MacRuby-devel] MacRuby 0.5 beta
In-Reply-To: <7A0E5CE4-8CBF-4027-A348-883EBD288434@apple.com>
References: <45103AB5-C61F-4229-BF50-952C72666B96@apple.com>
	<B262BF28-E665-4D43-BD92-D968579AAC92@gmail.com>
	<16BF2825-6C57-46F0-B39D-5AF0A3503FD9@apple.com>
	<7A0E5CE4-8CBF-4027-A348-883EBD288434@apple.com>
Message-ID: <5AD9D122-ED52-4189-A086-A73D02288936@apple.com>

Ah, OK.  Never mind then!

On Oct 9, 2009, at 1:56 AM, Laurent Sansonetti wrote:

> Jordan,
>
> Users should not need to obtain and install LLVM. MacRuby uses it  
> statically. There was a mistake in the installer, we forgot to  
> bundle llc (LLVM compiler tool) used by macrubyc, this will be fixed  
> in the upcoming nightly builds then in the next beta.
>
> Laurent
>
> On Oct 9, 2009, at 1:02 AM, Jordan K. Hubbard wrote:
>
>> Just judging by the initial round of twitter / blog postings, the  
>> #1 problem people are having trouble with 0.5B1 is obtaining  
>> LLVM.   Antonio has already put together a nice blog posting about  
>> it (http://antoniocangiano.com/2009/10/08/getting-macrubys-compiler-to-work/ 
>> ), but shouldn't his instructions be on the MacRuby blog, seeing as  
>> how Laurent's announcement is the first thing many people are going  
>> to see?  Even better, maybe an LLVM package to go along with  
>> MacRuby, also linked to on the site?  Given that you need a very  
>> specific (e.g. recent, from trunk) version of LLVM for MacRuby to  
>> work at all, this seems pretty reasonable.  If the instructions  
>> were "just go grab llvm 2.6" then I might feel differently.
>>
>> - Jordan
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From mattaimonetti at gmail.com  Fri Oct  9 10:19:00 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Fri, 9 Oct 2009 10:19:00 -0700
Subject: [MacRuby-devel] Empty Ruby Template
In-Reply-To: <5133d9390910090900g71dc688aub300df906403fb63@mail.gmail.com>
References: <5133d9390910090101u7136e67bl8ac85c4d79d4b580@mail.gmail.com>
	<20fefa50910090142n5121ee8bi2a0309701213fcff@mail.gmail.com>
	<5133d9390910090900g71dc688aub300df906403fb63@mail.gmail.com>
Message-ID: <20fefa50910091019q28db2aefh2d104901164d1457@mail.gmail.com>

thx, I'll look at  that tonight after work.

- Matt

On Fri, Oct 9, 2009 at 9:00 AM, Jesse Read <jread at dodgydev.net> wrote:

> I just checked the last nightly, and it only installs the following Xcode
> templates:
> /Library/Application Support/Developer/Xcode/3.0/Target Templates
> /Library/Application Support/Developer/Xcode/3.0/Project Templates
> /Library/Application Support/Developer/Xcode/Shared/Target Templates
> /Library/Application Support/Developer/Xcode/Shared/Project Templates
>
> No File Templates, I just manually copied the File Templates folder from
> /misc/xcode-templates in trunk to the 3.0 and Shared folders, mimicking the
> nightly installer.
>
> ? Jesse
>
>
>
> On Fri, Oct 9, 2009 at 4:42 AM, Matt Aimonetti <mattaimonetti at gmail.com>wrote:
>
>> The file should be part of the nightly package. I have to admit I failed
>> to check tho.
>> Can you please check that it's not a right access instead of the file
>> missing from the package?
>>
>> Thanks,
>>
>> - Matt
>>
>>
>> On Fri, Oct 9, 2009 at 1:01 AM, Jesse Read <jread at dodgydev.net> wrote:
>>
>>> I saw in the trunk status update, this line:
>>> "- Added an empty Ruby template file"
>>>
>>> Which I believes corresponds to this<https://www.macruby.org/trac/changeset/2721> changeset
>>> on Trac, where Matt added an Xcode Ruby file template.
>>>
>>> I manually installed the template, but are there any plans to add these
>>> into the installers, either for 0.5b2 or the nightlies? I doubt much will
>>> change with them, but other would probably enjoy them if they see them
>>> installed.
>>>
>>> Thanks, and keep up the great work!
>>>
>>> ? Jesse
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091009/15e92b9d/attachment.html>

From ruby-noreply at macosforge.org  Fri Oct  9 11:50:35 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 09 Oct 2009 18:50:35 -0000
Subject: [MacRuby-devel] [MacRuby] #370: Inconsistency between macruby
 and ruby in a simple class
In-Reply-To: <052.3daa3c7849cf67ac174b377fd7b472a3@macosforge.org>
References: <052.3daa3c7849cf67ac174b377fd7b472a3@macosforge.org>
Message-ID: <061.318c46eec3d5564ea5638778ebc4e117@macosforge.org>

#370: Inconsistency between macruby and ruby in a simple class
-----------------------------------+----------------------------------------
 Reporter:  kfowler@?              |       Owner:  lsansonetti@?        
     Type:  defect                 |      Status:  new                  
 Priority:  major                  |   Milestone:  MacRuby 0.5          
Component:  MacRuby                |    Keywords:                       
-----------------------------------+----------------------------------------

Comment(by lsansonetti@?):

 Good catch, the problem is definitely in object.c:1896

 {{{
     if (init_obj != Qnil) {
         p = CLASS_OF(init_obj);
         while (p != 0) {
             if (p == klass) {
                 return init_obj;
             }
             p = RCLASS_SUPER(p);
         }
     }
 }}}

 If I remember correctly, this was added because some classes (Array for
 example) return different objects during #initialize that should be taken
 into account. The code should probably be altered to only handle these
 objects.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/370#comment:4>
MacRuby <http://macruby.org/>


From mattaimonetti at gmail.com  Fri Oct  9 11:55:17 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Fri, 9 Oct 2009 11:55:17 -0700
Subject: [MacRuby-devel] MacRuby gem only
Message-ID: <20fefa50910091155n3dd43d17y9343e5e0392dea64@mail.gmail.com>

Any idea how we should flag gems that are MacRuby only like textorize-mr? I
don't think the platform flag is legit so I'm not sure what to use.
Any ideas?

- Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091009/0f8488c6/attachment.html>

From ruby-noreply at macosforge.org  Fri Oct  9 11:57:55 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 09 Oct 2009 18:57:55 -0000
Subject: [MacRuby-devel] [MacRuby] #373: protected methods aren't
Message-ID: <050.8b7f488c73e4ed24e710e6f09b814147@macosforge.org>

#373: protected methods aren't
---------------------------------+------------------------------------------
 Reporter:  chrisw@?             |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:  protected access     
---------------------------------+------------------------------------------
 Working through a trivial variation on the example class presented in
 Chapter 3 of PragProg's Programming Ruby 1.9, I noticed that MacRuby 0.5
 beta 1 doesn't enforce protected protection status of a method.  It does
 however enforce private protection status.  I do not have this problem
 with the same code run by Ruby 1.8.7 as shipped with Mac OS X 10.6.  I
 presume that the example in the PragProg book is valid for Ruby 1.9.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/373>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct  9 12:23:47 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 09 Oct 2009 19:23:47 -0000
Subject: [MacRuby-devel] [MacRuby] #373: protected methods aren't
In-Reply-To: <050.8b7f488c73e4ed24e710e6f09b814147@macosforge.org>
References: <050.8b7f488c73e4ed24e710e6f09b814147@macosforge.org>
Message-ID: <059.5ecea2f81d4a5ca4dafb883b14eb8046@macosforge.org>

#373: protected methods aren't
---------------------------------+------------------------------------------
 Reporter:  chrisw@?             |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:  protected access     
---------------------------------+------------------------------------------

Comment(by lsansonetti@?):

 Oops, looks like we forgot to implement the "protected" visibility :) I
 added this to the TODO list, thanks for the report.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/373#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct  9 12:43:01 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 09 Oct 2009 19:43:01 -0000
Subject: [MacRuby-devel] [MacRuby] #374: Adding a binding (in IB) prevents
	instance variables
Message-ID: <054.93150c8756026f602791b72169529a56@macosforge.org>

#374: Adding a binding (in IB) prevents instance variables
-------------------------------------+--------------------------------------
 Reporter:  parzival@?               |       Owner:  lsansonetti@?        
     Type:  defect                   |      Status:  new                  
 Priority:  major                    |   Milestone:                       
Component:  MacRuby                  |    Keywords:                       
-------------------------------------+--------------------------------------
 I've got a (MacRuby) subclass of NSWindowController.  If a binding is
 added using Interface Builder, it becomes impossible to have any instance
 variables in my subclass.  What's kind of strange, too, is that removing
 the binding doesn't fix it; so far it seems necessary to delete the object
 in IB and then re-create it.

 I'm using r2771, on a MBP(2007) running 10.6.1.  This was working at some
 point in 0.4, but I think it's been broken for at least a couple weeks or
 more.

 Here's some code in my class to demonstrate.  This gets called in
 awakeFromNib, though I tried adding an instance variable in initWithWindow
 and it came back nil as well :

 {{{
 testSPC = SourcePaneController.new
 puts "testSPC:"
 p testSPC
 @testSPC_iv = SourcePaneController.new
 puts "@testSPC_iv:"
 p @testSPC_iv

 testInt = 3
 puts "testInt:"
 p testInt
 @testInt_iv = 5
 puts "@testInt_iv:"
 p @testInt

 puts "Instance variables are :"
 p self.instance_variables
 }}}




 And the output:
 {{{
 in MainWinController.initWithWindow
 in SourcePaneController.init
 testSPC:
 #<SourcePaneController:0x2003df0a0>
 in SourcePaneController.init
 @testSPC_iv:
 nil
 testInt:
 3
 @testInt_iv:
 nil
 Instance variables are :
 []
 }}}

 As can be seen, the calls to my other class's initializer are working, but
 it's not getting assigned to the instance variable.
 A potentially revealing error occurred when I mistyped one of my test
 variable names.  This is what happens after ' @testSPC_iv = nothing'
 (where 'nothing' is an unassigned variable) :

 {{{
 2009-10-09 12:22:01.975 resynch[1015:a0f] +[MainWinController
 _getValue:forKey:]: unrecognized selector sent to class 0x200238940
 2009-10-09 12:22:01.978 resynch[1015:a0f] +[MainWinController
 _getValue:forKey:]: unrecognized selector sent to class 0x200238940
 2009-10-09 12:22:01.979 resynch[1015:a0f] An uncaught exception was raised
 2009-10-09 12:22:01.979 resynch[1015:a0f] +[MainWinController
 _getValue:forKey:]: unrecognized selector sent to class 0x200238940
 2009-10-09 12:22:01.981 resynch[1015:a0f] *** Terminating app due to
 uncaught exception 'NSInvalidArgumentException', reason:
 '+[MainWinController _getValue:forKey:]: unrecognized selector sent to
 class 0x200238940'
 *** Call stack at first throw:
 (
         0   CoreFoundation                      0x00007fff83dbf5a4
 __exceptionPreprocess + 180
         1   libobjc.A.dylib                     0x00007fff87c7c313
 objc_exception_throw + 45
         2   CoreFoundation                      0x00007fff83e18330
 __CFFullMethodName + 0
         3   CoreFoundation                      0x00007fff83d9230f
 ___forwarding___ + 751
         4   CoreFoundation                      0x00007fff83d8e458
 _CF_forwarding_prep_0 + 232
         5   CoreFoundation                      0x00007fff83d53ffd
 CFDictionaryGetValueIfPresent + 93
         6   libmacruby.dylib                    0x000000010010b4ee
 classname + 126
         7   libmacruby.dylib                    0x000000010010b728
 rb_class_path + 24
         8   libmacruby.dylib                    0x000000010010ba3e
 rb_obj_classname + 46
         9   libmacruby.dylib                    0x000000010006f89f
 rb_any_to_string + 15
         10  libmacruby.dylib                    0x000000010015f697
 rb_vm_call_with_cache2 + 4663
         11  libmacruby.dylib                    0x0000000100121199
 rb_funcall + 425
         12  libmacruby.dylib                    0x000000010015f697
 rb_vm_call_with_cache2 + 4663
         13  libmacruby.dylib                    0x0000000100121199
 rb_funcall + 425
         14  libmacruby.dylib                    0x000000010006a8f6
 rb_inspect + 22
         15  libmacruby.dylib                    0x000000010003e2a1
 name_err_mesg_to_str + 161
         16  libmacruby.dylib                    0x0000000100162d6f
 rb_vm_call + 4783
         17  libmacruby.dylib                    0x0000000100070df9
 rb_convert_type + 121
         18  libmacruby.dylib                    0x00000001000f010b
 rb_string_value + 107
         19  libmacruby.dylib                    0x000000010003c62e
 name_err_to_s + 78
         20  libmacruby.dylib                    0x000000010015f697
 rb_vm_call_with_cache2 + 4663
         21  libmacruby.dylib                    0x0000000100121199
 rb_funcall + 425
         22  libmacruby.dylib                    0x0000000100162d6f
 rb_vm_call + 4783
         23  libmacruby.dylib                    0x0000000100175e23
 rb_vm_print_current_exception + 99
         24  libmacruby.dylib                    0x0000000100176108
 macruby_main + 392
         25  resynch                             0x0000000100000e3e main +
 40
         26  resynch                             0x0000000100000ad8 start +
 52
         27  ???                                 0x0000000000000001 0x0 + 1
 )
 terminate called after throwing an instance of 'NSException'
 Program received signal:  ?SIGABRT?.
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/374>
MacRuby <http://macruby.org/>


From prabhaka at apple.com  Fri Oct  9 13:06:29 2009
From: prabhaka at apple.com (Ernest N. Prabhakar, Ph.D.)
Date: Fri, 09 Oct 2009 13:06:29 -0700
Subject: [MacRuby-devel] install from command line Re: MacRuby 0.5 beta 1
In-Reply-To: <5AA624F9-382F-4CBB-ADA2-6A8486D650A3@gmail.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
	<237413E7-69DB-4E7B-844E-7DD33C2B5ECE@gmail.com>
	<8B29EBD6-6741-4E13-BB72-F7D858AB60C6@apple.com>
	<E15349A4-FCC9-4B5E-B4B0-976366A35EF1@gmail.com>
	<9A438C13-69EC-45D0-BB11-377EE1E52098@apple.com>
	<2A672E30-F65C-40EF-B8AA-C6394C3A7330@apple.com>
	<5AA624F9-382F-4CBB-ADA2-6A8486D650A3@gmail.com>
Message-ID: <8775A9E7-094B-4DA7-9CC3-576A6490CCF8@apple.com>

>> Anyone to create a macruby_update_nightly script that would fetch the latest nightly build and merge it ? :)

Okay, here's a script that should do what Laurent asks:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: macruby_get_nightly.sh
Type: application/octet-stream
Size: 327 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091009/7b24d15a/attachment.obj>
-------------- next part --------------


Note you need to be present to enter the sudo password; not sure if there's an easy way around that, or if we should be installing somewhere else.

Try it and let me know if/how it works!

-- Ernie P.

On Oct 9, 2009, at 1:00 AM, Claudio Poli wrote:

> don't know what you mean with merge it, however there are apis to ease the download:
> http://macruby.icoretech.org/api
> 
> a curl -O http://macruby.icoretech.org/latest/macruby_nightly-latest.pkg should suffice :)
> 
> claudio
> 
> Il giorno 09/ott/2009, alle ore 01.19, Laurent Sansonetti ha scritto:
> 
>> Hi Ernie,
>> 
>> On Oct 8, 2009, at 2:25 PM, Ernest N. Prabhakar, Ph.D. wrote:
>> 
>>> Hi Wayne,
>>> 
>>> On Oct 8, 2009, at 1:59 PM, Wayne Seguin wrote:
>>>>>> Is it possible to a) install from command line
>>>>> 
>>> 
>>> $ unzip ~/Downloads/MacRuby\ 0.5\ beta\ 1.zip
>>> $ cd ~/Downloads/MacRuby\ 0.5\ beta\ 1
>>> $ sudo installer -pkg MacRuby\ 0.5\ beta\ 1.pkg  -target /
>> 
>> I totally didn't know about that.
>> 
>> Anyone to create a macruby_update_nightly script that would fetch the latest nightly build and merge it ? :)
>> 
>> Laurent
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> 
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Fri Oct  9 13:43:08 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 09 Oct 2009 20:43:08 -0000
Subject: [MacRuby-devel] [MacRuby] #375: MacRuby 0.5 beta 1 HotCocoa
	examples seg fault
Message-ID: <046.4930a390548bc5216a7ef4e5b5b916e8@macosforge.org>

#375: MacRuby 0.5 beta 1 HotCocoa examples seg fault
-----------------------------+----------------------------------------------
 Reporter:  macruby@?        |       Owner:  lsansonetti@?        
     Type:  defect           |      Status:  new                  
 Priority:  blocker          |   Milestone:                       
Component:  MacRuby          |    Keywords:                       
-----------------------------+----------------------------------------------
 MacRuby 0.5 beta 1 HotCocoa examples seg fault.
 Example:


 Process:         Calculator [1696]
 Path:
 /Users/dculbert/dev/MacRuby/HotCocoa/calculator/Calculator.app/Contents/MacOS/Calculator
 Identifier:      com.yourcompany.Calculator
 Version:         ??? (???)
 Code Type:       X86-64 (Native)
 Parent Process:  launchd [86]

 Date/Time:       2009-10-09 13:42:45.548 -0700
 OS Version:      Mac OS X 10.6.1 (10B504)
 Report Version:  6
 Sleep/Wake UUID: 84FF5771-DEEE-4B2D-B040-6722A1DD51CA

 Interval Since Last Report:          2227 sec
 Crashes Since Last Report:           1
 Per-App Crashes Since Last Report:   1
 Anonymous UUID:                      3D195BF2-A865-4AF8-9EB6-0D3EFC48B294

 Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
 Exception Codes: 0x000000000000000d, 0x0000000000000000
 Crashed Thread:  0  Dispatch queue: com.apple.main-thread

 Application Specific Information:
 objc_msgSend() selector name: length
 objc[1696]: garbage collection is ON

 Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
 0   libobjc.A.dylib                     0x00007fff81db033c objc_msgSend +
 40
 1   libmacruby.dylib                    0x00000001000ba3f0 rb_reg_search2
 + 144
 2   libmacruby.dylib                    0x00000001000f4add str_gsub + 157
 3   libmacruby.dylib                    0x000000010016d80f rb_vm_dispatch
 + 5679
 4   ???                                 0x000000010110363c 0 + 4312806972
 5   ???                                 0x00000001011028bd 0 + 4312803517
 6   ???                                 0x00000001011013b9 0 + 4312798137
 7   ???                                 0x0000000101100869 0 + 4312795241

 Thread 1:
 0   libSystem.B.dylib                   0x00007fff8814594a
 __workq_kernreturn + 10
 1   libSystem.B.dylib                   0x00007fff88145d5c
 _pthread_wqthread + 917
 2   libSystem.B.dylib                   0x00007fff881459c5 start_wqthread
 + 13

 Thread 0 crashed with X86 Thread State (64-bit):
   rax: 0x00007fff87a99a88  rbx: 0x0000000200021d40  rcx:
 0x0000000000000000  rdx: 0x0000000000000006
   rdi: 0x000000020011a800  rsi: 0x00007fff87a99a88  rbp:
 0x00007fff5fbfdb40  rsp: 0x00007fff5fbfda38
    r8: 0x850cd77ff45c0bf4   r9: 0x0000000000000006  r10:
 0x0000000000000006  r11: 0x726f5020230a2300
   r12: 0x00007fff5fbfdd20  r13: 0x000000010161d000  r14:
 0x0000000000000000  r15: 0x000000020009c9c0
   rip: 0x00007fff81db033c  rfl: 0x0000000000010206  cr2:
 0x00000001000bab30

 Binary Images:
        0x100000000 -        0x100000fff +com.yourcompany.Calculator ???
 (1.0) <88630F38-909F-129F-826E-AAD31BFB4579>
 /Users/dculbert/dev/MacRuby/HotCocoa/calculator/Calculator.app/Contents/MacOS/Calculator
        0x100003000 -        0x100aeef3f +libmacruby.dylib ??? (???)
 <D6BCA044-D363-8D9E-BA4B-406077B433A3>
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/libmacruby.dylib
     0x7fff5fc00000 -     0x7fff5fc3bdef  dyld 132.1 (???) <B633F790-4DDB-
 53CD-7ACF-2A3682BCEA9F> /usr/lib/dyld
     0x7fff805f9000 -     0x7fff806c5fff  com.apple.CFNetwork 454.4 (454.4)
 <E7721AD8-3177-8749-60F7-5EF323E6492B>
 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
     0x7fff806c6000 -     0x7fff806d5fff  com.apple.NetFS 3.2 (3.2)
 <61E3D8BE-A529-20BF-1A11-026EC774820D>
 /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
     0x7fff80cc4000 -     0x7fff80d05ff7  com.apple.SystemConfiguration
 1.10 (1.10) <E3FF1FC8-C760-2047-F954-0D283DD0F714>
 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
     0x7fff80e3f000 -     0x7fff810c0fe7  com.apple.Foundation 6.6 (751)
 <CCE98C5C-DFEA-6C80-A014-A5985437072E>
 /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
     0x7fff8120e000 -     0x7fff81540fef  com.apple.CoreServices.CarbonCore
 859.1 (859.1) <5712C4C1-B18B-88EE-221F-DA04A8EDA029>
 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
     0x7fff81b4a000 -     0x7fff81b58ff7  libkxld.dylib ??? (???)
 <823B6BE6-E952-3B3C-3633-8F4D6C4606A8> /usr/lib/system/libkxld.dylib
     0x7fff81dac000 -     0x7fff81e62fe7  libobjc.A.dylib ??? (???)
 <261D97A3-225B-8A00-56AA-F9F27973063F> /usr/lib/libobjc.A.dylib
     0x7fff81eb5000 -     0x7fff81ecbfef  libbsm.0.dylib ??? (???)
 <42D3023A-A1F7-4121-6417-FCC6B51B3E90> /usr/lib/libbsm.0.dylib
     0x7fff82df3000 -     0x7fff82f66fef  com.apple.CoreFoundation 6.6
 (550) <04EC0CC2-6CE4-4EE0-03B9-6C5109398CB1>
 /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
     0x7fff83936000 -     0x7fff83961ff7  libxslt.1.dylib ??? (???)
 <87A0B228-B24A-C426-C3FB-B40D7258DD49> /usr/lib/libxslt.1.dylib
     0x7fff83b57000 -     0x7fff83b68fef  libz.1.dylib ??? (???)
 <3A7A4C48-A4C8-A78A-8B87-C0DDF6601AC8> /usr/lib/libz.1.dylib
     0x7fff83b69000 -     0x7fff83b6dff7  libmathCommon.A.dylib ??? (???)
 <95718673-FEEE-B6ED-B127-BCDBDB60D4E5>
 /usr/lib/system/libmathCommon.A.dylib
     0x7fff842a1000 -     0x7fff842c9fff  com.apple.DictionaryServices 1.1
 (1.1) <D57BA55A-4CC5-5C17-8077-AEEA27A01C7A>
 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
     0x7fff84eac000 -     0x7fff84ef9ff7  libauto.dylib ??? (???)
 <8658DB85-C611-1212-44E5-5B2539018FA0> /usr/lib/libauto.dylib
     0x7fff85745000 -     0x7fff85780fef  com.apple.AE 496 (496)
 <6AFD62E0-DD92-4F04-A73A-90224D80593D>
 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
     0x7fff85849000 -     0x7fff8584afff  libffi.dylib ??? (???) <B683A5FD-
 A83D-7989-A91F-BAED12E37054> /usr/lib/libffi.dylib
     0x7fff859d1000 -     0x7fff859d7ff7  com.apple.DiskArbitration 2.3
 (2.3) <857F6E43-1EF4-7D53-351B-10DE0A8F992A>
 /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
     0x7fff860cb000 -     0x7fff86187ff7  com.apple.CoreServices.OSServices
 352 (352) <CD933BBD-B260-552F-E64E-291D6ED3091A>
 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
     0x7fff862c5000 -     0x7fff86365fff  com.apple.LaunchServices 360.3
 (360.3) <02FFE657-CC7A-5266-F06E-8732E28F70A9>
 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
     0x7fff86387000 -     0x7fff8649efef  libxml2.2.dylib ??? (???)
 <6D4C196C-B061-CBCD-AAFD-A21736A8425C> /usr/lib/libxml2.2.dylib
     0x7fff864ea000 -     0x7fff86534ff7  com.apple.Metadata 10.6.0 (507.1)
 <AA0DF8E0-9B5B-2377-9B20-884919E28994>
 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
     0x7fff86ae8000 -     0x7fff86b45fef  com.apple.framework.IOKit 2.0
 (???) <65AA6170-12E3-BFB5-F982-E0C433610A1F>
 /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
     0x7fff86b46000 -     0x7fff86dcafff  com.apple.security 6.0 (36910)
 <F7431448-BC2E-835D-E7A2-E47E0A5CB984>
 /System/Library/Frameworks/Security.framework/Versions/A/Security
     0x7fff86e7a000 -     0x7fff86f33fff  libsqlite3.dylib ??? (???)
 <5A15E12A-AE8F-1A36-BBC7-564E7D7AD0FB> /usr/lib/libsqlite3.dylib
     0x7fff86f34000 -     0x7fff86fb1fef  libstdc++.6.dylib ??? (???)
 <35ECA411-2C08-FD7D-11B1-1B7A04921A5C> /usr/lib/libstdc++.6.dylib
     0x7fff8719e000 -     0x7fff8719eff7  com.apple.CoreServices 44 (44)
 <210A4C56-BECB-E3E4-B6EE-7EC53E02265D>
 /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
     0x7fff8719f000 -     0x7fff8735cfff  libicucore.A.dylib ??? (???)
 <224721C0-EC21-94D0-6484-66C603C34CBE> /usr/lib/libicucore.A.dylib
     0x7fff8812b000 -     0x7fff882e9ff7  libSystem.B.dylib ??? (???)
 <66102D4E-6C8B-77D0-6766-2A1788B20C6F> /usr/lib/libSystem.B.dylib
     0x7fff88511000 -     0x7fff885a1fff  com.apple.SearchKit 1.3.0 (1.3.0)
 <4175DC31-1506-228A-08FD-C704AC9DF642>
 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
     0x7fffffe00000 -     0x7fffffe01fff  libSystem.B.dylib ??? (???)
 <66102D4E-6C8B-77D0-6766-2A1788B20C6F> /usr/lib/libSystem.B.dylib

 Model: Macmini3,1, BootROM MM31.0081.B06, 2 processors, Intel Core 2 Duo,
 2 GHz, 4 GB, SMC 1.35b2
 Graphics: NVIDIA GeForce 9400, NVIDIA GeForce 9400, PCI, 256 MB
 Memory Module: global_name
 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x90),
 Broadcom BCM43xx 1.0 (5.10.91.19)
 Bluetooth: Version 2.2.1f7, 2 service, 1 devices, 1 incoming serial ports
 Network Service: Ethernet, Ethernet, en0
 Network Service: AirPort, AirPort, en1
 Serial ATA Device: Hitachi HTS543225L9SA02, 232.89 GB
 Serial ATA Device: OPTIARC DVD RW AD-5670S
 USB Device: Keyboard Hub, 0x05ac  (Apple Inc.), 0x1006, 0x26400000
 USB Device: Apple Optical USB Mouse, 0x05ac  (Apple Inc.), 0x0307,
 0x26430000
 USB Device: Apple Keyboard, 0x05ac  (Apple Inc.), 0x0220, 0x26420000
 USB Device: IR Receiver, 0x05ac  (Apple Inc.), 0x8242, 0x04500000
 USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x06100000
 USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.), 0x8216,
 0x06110000

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/375>
MacRuby <http://macruby.org/>


From keith.gautreaux at gmail.com  Fri Oct  9 15:03:11 2009
From: keith.gautreaux at gmail.com (Keith Gautreaux)
Date: Fri, 9 Oct 2009 17:03:11 -0500
Subject: [MacRuby-devel] MacRuby gem only
In-Reply-To: <20fefa50910091155n3dd43d17y9343e5e0392dea64@mail.gmail.com>
References: <20fefa50910091155n3dd43d17y9343e5e0392dea64@mail.gmail.com>
Message-ID: <a3fb9cde0910091503o7308a322w72d5e99da8870530@mail.gmail.com>

Presumably Macruby gems will be installed with macgem?  Certainly, we
would not want to fork RubyGems, but since the Gem::Platform spec
exists shouldn't macgem only install gems whose Gem::Platform::RUBY is
MacRuby?

For projects like JRuby and Rubinius it makes sense to always have
Gem::Platform::RUBY == 'ruby', but isn't MacRuby a superset of Ruby
the way Objective-C is a superset of C?

As long as RubyGems prevents installation of gems whose
Gem::Platform::RUBY == 'MacRuby' on stock YARV installations I think
this approach is reasonable, but IANEH (I Am Not Eric Hodel).

On Fri, Oct 9, 2009 at 1:55 PM, Matt Aimonetti <mattaimonetti at gmail.com> wrote:
> Any idea how we should flag gems that are MacRuby only like textorize-mr? I
> don't think the platform flag is legit so I'm not sure what to use.
> Any ideas?
>
> - Matt
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>



-- 
Keith

From conradwt at gmail.com  Fri Oct  9 16:22:28 2009
From: conradwt at gmail.com (Conrad Taylor)
Date: Fri, 9 Oct 2009 16:22:28 -0700
Subject: [MacRuby-devel] MacRuby gem only
In-Reply-To: <a3fb9cde0910091503o7308a322w72d5e99da8870530@mail.gmail.com>
References: <20fefa50910091155n3dd43d17y9343e5e0392dea64@mail.gmail.com>
	<a3fb9cde0910091503o7308a322w72d5e99da8870530@mail.gmail.com>
Message-ID: <7317d7610910091622q2af5dbadg77498fac7be15d1e@mail.gmail.com>

Hi, I was thinking that it may time to update the GemSpec to support another
variable called required_ruby_implementation.  Thus, I filled an enhancement
request
https://rubyforge.org/tracker/?func=detail&aid=27269&group_id=126&atid=578

At this time, the GemSpec supports required_ruby_version but says nothing
about the implementation.  Also, it may be a good time to start upgrading
RubyGems as new Ruby implementation are currently in development or has been
released like JRuby.

On Fri, Oct 9, 2009 at 3:03 PM, Keith Gautreaux
<keith.gautreaux at gmail.com>wrote:

> Presumably Macruby gems will be installed with macgem?  Certainly, we
> would not want to fork RubyGems, but since the Gem::Platform spec
> exists shouldn't macgem only install gems whose Gem::Platform::RUBY is
> MacRuby?
>
>
The platform here seems to refer more to the type of OS.  Thus,
Gem::Platform::Ruby means
any OS which is a bit misleading.  Are we talking about the OS or the Ruby
implementation?


> For projects like JRuby and Rubinius it makes sense to always have
> Gem::Platform::RUBY == 'ruby', but isn't MacRuby a superset of Ruby
> the way Objective-C is a superset of C?
>
>
Yes, MacRuby would be considered a superset because Ruby has been
implemented on top
of the Objective-C runtime.  This is similar to JRuby, IronRuby, and so on.
 Furthermore, it
might be wise to consider that both Rubinius and JRuby may create gems that
are specific
to their respective implementations.


> As long as RubyGems prevents installation of gems whose
> Gem::Platform::RUBY == 'MacRuby' on stock YARV installations I think
> this approach is reasonable, but IANEH (I Am Not Eric Hodel).


'macgem list -r' to retrieve all the gems that are compatible with MacRuby.
 I have dealt with
this issue with Ruby 1.8.6 and 1.9.1 and it was a nightmare because
required_ruby_version
wasn't added to the GemSpec for the gem in question.  Now, the complexity
grows with new
implementations of Ruby.

Just my 2 cents,

-Conrad


> On Fri, Oct 9, 2009 at 1:55 PM, Matt Aimonetti <mattaimonetti at gmail.com>
> wrote:
> > Any idea how we should flag gems that are MacRuby only like textorize-mr?
> I
> > don't think the platform flag is legit so I'm not sure what to use.
> > Any ideas?
> >
> > - Matt
> >
> > _______________________________________________
> > MacRuby-devel mailing list
> > MacRuby-devel at lists.macosforge.org
> > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> >
> >
>
>
>
> --
> Keith
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091009/b0f6fa64/attachment.html>

From ruby-noreply at macosforge.org  Fri Oct  9 16:40:04 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 09 Oct 2009 23:40:04 -0000
Subject: [MacRuby-devel] [MacRuby] #370: Inconsistency between macruby
 and ruby in a simple class
In-Reply-To: <052.3daa3c7849cf67ac174b377fd7b472a3@macosforge.org>
References: <052.3daa3c7849cf67ac174b377fd7b472a3@macosforge.org>
Message-ID: <061.e3c77fe51701180ed39591a51df854a6@macosforge.org>

#370: Inconsistency between macruby and ruby in a simple class
-----------------------------------+----------------------------------------
 Reporter:  kfowler@?              |        Owner:  lsansonetti@?        
     Type:  defect                 |       Status:  closed               
 Priority:  major                  |    Milestone:  MacRuby 0.5          
Component:  MacRuby                |   Resolution:  fixed                
 Keywords:                         |  
-----------------------------------+----------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 After a quick investigation it looks like this code was not necessary
 anymore, I deleted it in r2775.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/370#comment:5>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Fri Oct  9 16:46:19 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Fri, 09 Oct 2009 16:46:19 -0700
Subject: [MacRuby-devel] Building MacRuby r2765 with llvm r82747 failed
	on	core duo macbook, Leopard
In-Reply-To: <6e90f1240910090422g6c7a54cdxc7c521007fd1be60@mail.gmail.com>
References: <6e90f1240910090422g6c7a54cdxc7c521007fd1be60@mail.gmail.com>
Message-ID: <75213076-B6F9-4945-9B72-87396B4392BB@apple.com>

Hi,

On Oct 9, 2009, at 4:22 AM, hiroshi saito wrote:

> Hi all,
>
> I failed to build llvm r82747 and MacRuby r2765 following the
> instruction of README.
> I use core duo macbook and Leopard.
>
> $ svn co -r 2765
> http://svn.macosforge.org/repository/ruby/MacRuby/trunk MacRuby-trunk
> $ svn co -r 82747 https://llvm.org/svn/llvm-project/llvm/trunk llvm- 
> trunk
> $ cd llvm-trunk
> $ UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64" ENABLE_OPTIMIZED=1 make
> ...
> llvm[2]: Compiling BasicBlockTracing.c for Release build (bytecode)
> ...
> llvm-gcc-4.2: -E, -S, -save-temps and -M options are not allowed with
> multiple -arch flags

Looks like the LLVM build system it picking llvm-gcc instead of gcc.  
This is probably why it's failing.

You probably want to remote llvm-gcc out of your $PATH and try again.

> To avoid the error, omited univsersal environment variables.
>
> $ ENABLE_OPTIMIZED=1 make
>
> It worked.
>
> Next, build MacRuby itself. My llvm isn't universal binary anymore, so
> I explicitly specified archs options;
>
> $ PATH=$PATH:~/Desktop/wc/MacRuby/llvm-trunk/Release/bin rake  
> archs=i386
> ...
> /usr/bin/g++ -I/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include
> -I/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include  -D_DEBUG
> -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -O3
> -fno-common -Woverloaded-virtual -I. -I./include -g -Wall -arch i386
> -Wno-parentheses -Wno-deprecated-declarations -Werror -Winline --param
> inline-unit-growth=10000 --param large-function-growth=10000 -x
> objective-c++ -c dispatcher.cpp -o dispatcher.o
> cc1objplus: warnings being treated as errors
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:417:
> warning: ?void llvm::PATypeHandle::addUser()? was used before it was
> declared inline

Mmh, this never happened to me. But I never tried to build MacRuby for  
a single architecture like this yet.

I recommend to rebuild LLVM without llvm-gcc and try again.

Good luck,

Laurent

From ruby-noreply at macosforge.org  Fri Oct  9 17:15:18 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 00:15:18 -0000
Subject: [MacRuby-devel] [MacRuby] #371: Module methods included in the
 class Module are not visible to other classes.
In-Reply-To: <050.b29ce2179f990c014e2fd8737732541a@macosforge.org>
References: <050.b29ce2179f990c014e2fd8737732541a@macosforge.org>
Message-ID: <059.bde513546d7e67bde969a5dc59fdf981@macosforge.org>

#371: Module methods included in the class Module are not visible to other
classes.
---------------------------------+------------------------------------------
 Reporter:  mred@?               |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------

Comment(by lsansonetti@?):

 These are 2 different bugs.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/371#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct  9 19:10:56 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 02:10:56 -0000
Subject: [MacRuby-devel] [MacRuby] #376: The second 'pointer' of a double
 pointer type is ignored
Message-ID: <050.e457ce96cd16850e431e499f112c297c@macosforge.org>

#376: The second 'pointer' of a double pointer type is ignored
---------------------------------+------------------------------------------
 Reporter:  mred@?               |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------
 The following code worked in 0.4
 {{{
 framework 'Foundation'
 framework 'AudioToolbox'

 load_bridge_support_file '../BridgeSupport/MusicPlayer.bridgesupport'

 class MusicPlayer
   def initialize
     musicPlayer = Pointer.new_with_type '^{OpaqueMusicPlayer}'      # This
 should create a double pointer
     puts musicPlayer.type                                           # But
 it doesn't
     (result = NewMusicPlayer musicPlayer) == 0 or raise result.to_s
     @musicPlayer = musicPlayer[0]                                   #
 Causing problems here
   end
 end

 musicPlayer = MusicPlayer.new
 }}}

 But it now generates the following error

 {{{
 $ macruby x.rb
 ^{OpaqueMusicPlayer}
 x.rb:8:in `initialize': unrecognized runtime type `{OpaqueMusicPlayer}'
 (TypeError)
         from core:in `__new__:'
         from x.rb:1:in `<main>'
 }}}

 The error is occuring during the attempt to dereference the double pointer
 at line 10 (despite the error message reporting line 8)

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/376>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct  9 19:40:07 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 02:40:07 -0000
Subject: [MacRuby-devel] [MacRuby] #374: Adding a binding (in IB)
 prevents instance variables
In-Reply-To: <054.93150c8756026f602791b72169529a56@macosforge.org>
References: <054.93150c8756026f602791b72169529a56@macosforge.org>
Message-ID: <063.5ed89ad3bf1437dd68e14e4fb3e7b1dc@macosforge.org>

#374: Adding a binding (in IB) prevents instance variables
-------------------------------------+--------------------------------------
 Reporter:  parzival@?               |        Owner:  lsansonetti@?        
     Type:  defect                   |       Status:  closed               
 Priority:  major                    |    Milestone:  MacRuby 0.5          
Component:  MacRuby                  |   Resolution:  fixed                
 Keywords:                           |  
-------------------------------------+--------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Matthias Neeracher was kind enough to contribute some KVO specs that were
 reproducing your crash, and I fixed the bugs in r2778. Please give it a
 try again and let us know if you still have problems.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/374#comment:1>
MacRuby <http://macruby.org/>


From paul-lists at tdgq.com.au  Fri Oct  9 21:39:18 2009
From: paul-lists at tdgq.com.au (Paul Howson)
Date: Sat, 10 Oct 2009 14:39:18 +1000
Subject: [MacRuby-devel] Do the nightly builds continue from the latest beta
Message-ID: <059F1FEE-EBD0-4D4D-B115-E97780583253@tdgq.com.au>

This might be an obvious question, but are the nightly builds (and the  
nightly build installers) an evolution from whatever is the latest  
beta? In other words, are the official betas just particular snapshots  
of the ongoing nightly build process?

----------------------------------------------------------------
Paul Howson
Warwick Qld Australia


From mattaimonetti at gmail.com  Fri Oct  9 21:52:55 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Fri, 9 Oct 2009 21:52:55 -0700
Subject: [MacRuby-devel] Do the nightly builds continue from the latest
	beta
In-Reply-To: <059F1FEE-EBD0-4D4D-B115-E97780583253@tdgq.com.au>
References: <059F1FEE-EBD0-4D4D-B115-E97780583253@tdgq.com.au>
Message-ID: <20fefa50910092152j32adecacj9b7cf76fb13c83aa@mail.gmail.com>

The answer is yes :) With a different packager tho.

- Matt

On Fri, Oct 9, 2009 at 9:39 PM, Paul Howson <paul-lists at tdgq.com.au> wrote:

> This might be an obvious question, but are the nightly builds (and the
> nightly build installers) an evolution from whatever is the latest beta? In
> other words, are the official betas just particular snapshots of the ongoing
> nightly build process?
>
> ----------------------------------------------------------------
> Paul Howson
> Warwick Qld Australia
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091009/da0d69ed/attachment.html>

From parzival at mindspring.com  Fri Oct  9 22:13:49 2009
From: parzival at mindspring.com (Michael Winterstein)
Date: Fri, 9 Oct 2009 22:13:49 -0700
Subject: [MacRuby-devel] [MacRuby] #374: Adding a binding (in IB)
	prevents instance variables
In-Reply-To: <063.5ed89ad3bf1437dd68e14e4fb3e7b1dc@macosforge.org>
References: <054.93150c8756026f602791b72169529a56@macosforge.org>
	<063.5ed89ad3bf1437dd68e14e4fb3e7b1dc@macosforge.org>
Message-ID: <38D0D9F0-2289-4C5B-99DC-6AA640E6A2F8@mindspring.com>

r2778 works fine. Great to have some specs in there.

On Oct 9, 2009, at 7:40 PM, MacRuby wrote:

> #374: Adding a binding (in IB) prevents instance variables
> ------------------------------------- 
> +--------------------------------------
> Reporter:  parzival@?               |        Owner:  lsansonetti@?
>     Type:  defect                   |       Status:  closed
> Priority:  major                    |    Milestone:  MacRuby 0.5
> Component:  MacRuby                  |   Resolution:  fixed
> Keywords:                           |
> ------------------------------------- 
> +--------------------------------------
> Changes (by lsansonetti@?):
>
>  * status:  new => closed
>  * resolution:  => fixed
>  * milestone:  => MacRuby 0.5
>
>
> Comment:
>
> Matthias Neeracher was kind enough to contribute some KVO specs that  
> were
> reproducing your crash, and I fixed the bugs in r2778. Please give  
> it a
> try again and let us know if you still have problems.
>
> -- 
> Ticket URL: <http://www.macruby.org/trac/ticket/374#comment:1>
> MacRuby <http://macruby.org/>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Sat Oct 10 04:14:26 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 11:14:26 -0000
Subject: [MacRuby-devel] [MacRuby] #377: macgem crashes while installing any
	gem
Message-ID: <063.07f5d3ecfb29cc0c83bf30ea769b0bbd@macosforge.org>

#377: macgem crashes while installing any gem
----------------------------------------------+-----------------------------
 Reporter:  amadeusz.jasak+macruby@?          |       Owner:  lsansonetti@?        
     Type:  defect                            |      Status:  new                  
 Priority:  blocker                           |   Milestone:  MacRuby 0.5          
Component:  MacRuby                           |    Keywords:  macgem, gem          
----------------------------------------------+-----------------------------
 Hi,
 I've installed the latest daily build of MacRuby (09.10.09), I used to use
 MacRuby few months ago without any problems. I've upgraded to Snow Leopard
 and Xcode 3.2 so I needed the newest build.
 There is a problem while installing any gem (dm-core, haml, sinatra...)
 eg.
 {{{
 bash-3.2# macruby -v
 MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]

 bash-3.2# macgem install dm-core
 ERROR:  While executing gem ... (ArgumentError)
     Illformed requirement [nil]
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/377>
MacRuby <http://macruby.org/>


From hiroshi3110 at gmail.com  Sat Oct 10 07:17:10 2009
From: hiroshi3110 at gmail.com (hiroshi saito)
Date: Sat, 10 Oct 2009 23:17:10 +0900
Subject: [MacRuby-devel] Building MacRuby r2765 with llvm r82747 failed
	on core duo macbook, Leopard
In-Reply-To: <75213076-B6F9-4945-9B72-87396B4392BB@apple.com>
References: <6e90f1240910090422g6c7a54cdxc7c521007fd1be60@mail.gmail.com>
	<75213076-B6F9-4945-9B72-87396B4392BB@apple.com>
Message-ID: <6e90f1240910100717y4a734ab9yea5617936841cdf2@mail.gmail.com>

Hi Laurent,

Thanks for pointing out possibility about llvm-gcc somewhere in the
PATH. That's right. I found llvm-gcc in /Developer/usr/bin.
After removing /Developer/usr/bin from the PATH, I could successfully
build llvm as an universal binary.

However, as for MacRuby itself, libmacruby.dylib and macruby is OK
with allow_build_warnings=true option, but aot_compile_stdlib is
failed.
I used MacRuby trunk r2779 this time.


$ PATH=$PATH:~/Desktop/wc/MacRuby/llvm-trunk/Release/bin rake
allow_build_warnings=true -t
...
** Invoke macruby:dylib
** Execute aot_compile_stdlib
./miniruby -I. -I./lib bin/rubyc --internal -C "rbconfig.rb" -o "./rbconfig.rbo"
/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c:2: error:
expected initializer before ?-? token
/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c: In function
?void __init__()?:
/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c:5: error:
?MREP_? was not declared in this scope
/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c:5: error:
?107041289? cannot be used as a function
Error when executing `/usr/bin/g++
/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c -dynamic
-bundle -undefined suppress -flat_namespace -arch x86_64 -L. -lmacruby
/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.o -o
./rbconfig.rbo'
rake aborted!


The content of /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c is:
extern "C" {
  void *MREP_-107041289(void *, void *);
  void *rb_vm_top_self(void);
  __attribute__((constructor)) static void __init__(void) {
    MREP_-107041289(rb_vm_top_self(), 0);
  }
}


FYI, the warnings I forced to ignore with allow_build_warnings=true
are those below. I wonder this is happened by not installing llvm, but
specifying it's location with "PATH".


/usr/bin/g++ -I/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include
-I/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include  -D_DEBUG
-D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -O3
-fno-common -Woverloaded-virtual -I. -I./include -g -Wall -arch i386
-arch x86_64 -Winline --param inline-unit-growth=10000 --param
large-function-growth=10000 -x objective-c++ -c dispatcher.cpp -o
dispatcher.o
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:417:
warning: ?void llvm::PATypeHandle::addUser()? was used before it was
declared inline
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/AbstractTypeUser.h:95:
warning: previous non-inline declaration here
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:422:
warning: ?void llvm::PATypeHandle::removeUser()? was used before it
was declared inline
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/AbstractTypeUser.h:96:
warning: previous non-inline declaration here
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:434:
warning: ?llvm::Type* llvm::PATypeHolder::get() const? was used before
it was declared inline
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/AbstractTypeUser.h:159:
warning: previous non-inline declaration here
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:440:
warning: ?void llvm::PATypeHolder::addRef()? was used before it was
declared inline
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/AbstractTypeUser.h:182:
warning: previous non-inline declaration here
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:446:
warning: ?void llvm::PATypeHolder::dropRef()? was used before it was
declared inline
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/AbstractTypeUser.h:183:
warning: previous non-inline declaration here
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:417:
warning: ?void llvm::PATypeHandle::addUser()? was used before it was
declared inline
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/AbstractTypeUser.h:95:
warning: previous non-inline declaration here
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:422:
warning: ?void llvm::PATypeHandle::removeUser()? was used before it
was declared inline
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/AbstractTypeUser.h:96:
warning: previous non-inline declaration here
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:434:
warning: ?llvm::Type* llvm::PATypeHolder::get() const? was used before
it was declared inline
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/AbstractTypeUser.h:159:
warning: previous non-inline declaration here
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:440:
warning: ?void llvm::PATypeHolder::addRef()? was used before it was
declared inline
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/AbstractTypeUser.h:182:
warning: previous non-inline declaration here
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:446:
warning: ?void llvm::PATypeHolder::dropRef()? was used before it was
declared inline
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/AbstractTypeUser.h:183:
warning: previous non-inline declaration here

From ruby-noreply at macosforge.org  Sat Oct 10 07:41:38 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 14:41:38 -0000
Subject: [MacRuby-devel] [MacRuby] #94: Bug with non-ASCII in the
	regular expressions
In-Reply-To: <057.e066a1dcf4cd70ca67213c93ef53863e@macosforge.org>
References: <057.e066a1dcf4cd70ca67213c93ef53863e@macosforge.org>
Message-ID: <066.8b801f9a255620c4373a1db6c8a959c0@macosforge.org>

#94: Bug with non-ASCII in the regular expressions
----------------------------------------+-----------------------------------
 Reporter:  vincent.isambart@?          |       Owner:  lsansonetti@?        
     Type:  defect                      |      Status:  new                  
 Priority:  blocker                     |   Milestone:  MacRuby 0.4          
Component:  MacRuby                     |    Keywords:                       
----------------------------------------+-----------------------------------

Comment(by hiroshi3110@?):

 This doesn't seem to resolved even in MacRuby 0.5 (trunk r82747).

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/94#comment:4>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 10 09:01:38 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 16:01:38 -0000
Subject: [MacRuby-devel] [MacRuby] #371: Module methods included in the
 class Module are not visible to other classes.
In-Reply-To: <050.b29ce2179f990c014e2fd8737732541a@macosforge.org>
References: <050.b29ce2179f990c014e2fd8737732541a@macosforge.org>
Message-ID: <059.dfd4c81c18bbf623b27856154ed1a57e@macosforge.org>

#371: Module methods included in the class Module are not visible to other
classes.
---------------------------------+------------------------------------------
 Reporter:  mred@?               |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------

Comment(by keith.gautreaux@?):

 I'm sorry Laurent.  I will open a separate ticket for the second bug.
 Thanks.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/371#comment:3>
MacRuby <http://macruby.org/>


From jazzbox at 7zz.de  Sat Oct 10 09:02:25 2009
From: jazzbox at 7zz.de (B. Ohr)
Date: Sat, 10 Oct 2009 18:02:25 +0200
Subject: [MacRuby-devel] Flash on the iPhone via LLVM
Message-ID: <1EDDF616-4F8F-4CB9-A3CA-4BA771D55626@7zz.de>

Hi,

I found this interesting article http://www.appleinsider.com/articles/09/10/06/html5_assault_on_adobe_flash_heats_up_with_clicktoflash.html&page=2 
  , describing how Adobe plans to port it's Flash to the iPhone via  
LLVM.

I have never programmed for Flash (I hate Flash), but I know, that  
they are using garbage collection for their ActionScript. They are  
planning a first release for end of the year, so I think they are  
running already gc-Code on the iPhone.

That means: it is time for the first port of MacRuby for the iPhone!

Bernd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091010/2f7b7bbc/attachment.html>

From ruby-noreply at macosforge.org  Sat Oct 10 09:26:52 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 16:26:52 -0000
Subject: [MacRuby-devel] [MacRuby] #378: Macruby 0.5 allows instantiation of
 a Module instance
Message-ID: <056.b6b4d62f7733b375cf6d91488345844b@macosforge.org>

#378: Macruby 0.5 allows instantiation of a Module instance
---------------------------------------+------------------------------------
 Reporter:  keith.gautreaux@?          |       Owner:  lsansonetti@?        
     Type:  defect                     |      Status:  new                  
 Priority:  minor                      |   Milestone:  MacRuby 0.5          
Component:  MacRuby                    |    Keywords:                       
---------------------------------------+------------------------------------
 It seems that MacRuby treats modules differently than Ruby 1.9. You
 shouldn't be able to instantiate a named module using the new method, i.e.

 {{{
 A = Module.new do
   def meth1
     "hello"
   end
 end
 }}}

 YARV:
 {{{
 a = A.new => NoMethodError: undefined method `new' for A:Module
 }}}

 but it does in MacRuby returning an instance of A:Module which responds to
 the meth1 call:

 {{{
   a.meth1 =>"hello"
 }}}

 I believe the proper behavior (based on the 1.9 pickaxe documentation) is
 to allow extending of an object with A's methods but not instantiation.

 {{{
 a = NSObject.new
 a.extend(A)
 a.meth1 => "hello"
 }}}

 Once I figure out how to write specs I'll see if I can submit a failing
 one.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/378>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 10 09:28:00 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 16:28:00 -0000
Subject: [MacRuby-devel] [MacRuby] #378: Macruby 0.5 allows
 instantiation of a Module instance
In-Reply-To: <056.b6b4d62f7733b375cf6d91488345844b@macosforge.org>
References: <056.b6b4d62f7733b375cf6d91488345844b@macosforge.org>
Message-ID: <065.e781048d2fc1672c56215b998ac15268@macosforge.org>

#378: Macruby 0.5 allows instantiation of a Module instance
---------------------------------------+------------------------------------
 Reporter:  keith.gautreaux@?          |       Owner:  lsansonetti@?        
     Type:  defect                     |      Status:  new                  
 Priority:  minor                      |   Milestone:  MacRuby 0.5          
Component:  MacRuby                    |    Keywords:                       
---------------------------------------+------------------------------------

Comment(by keith.gautreaux@?):

 Note: The above is a new ticket copied from a comment on Ticket #371.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/378#comment:1>
MacRuby <http://macruby.org/>


From martinhess at me.com  Sat Oct 10 10:13:24 2009
From: martinhess at me.com (Martin Hess)
Date: Sat, 10 Oct 2009 10:13:24 -0700
Subject: [MacRuby-devel] MacRuby 0.5 beta 1
In-Reply-To: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
Message-ID: <1E49EBB6-0B25-4322-A1AE-34F3E115B6BB@me.com>

Congratulations! Truly an amazing effort.

Just curious, is there a webpage to view the daily rubyspec results in  
detail?

On Oct 7, 2009, at 9:13 PM, Laurent Sansonetti wrote:

> Hi,
>
> The first beta release of MacRuby 0.5 is out! I prepared some notes  
> here:
>
> http://www.macruby.org/blog/2009/10/07/macruby05b1.html
>
> The goal is to go through a few beta releases before releasing the  
> final 0.5.
>
> Please give it a try and report us bugs & feedback :)
>
> Laurent
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Sat Oct 10 10:29:40 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 17:29:40 -0000
Subject: [MacRuby-devel] [MacRuby] #377: macgem crashes while installing
	any gem
In-Reply-To: <063.07f5d3ecfb29cc0c83bf30ea769b0bbd@macosforge.org>
References: <063.07f5d3ecfb29cc0c83bf30ea769b0bbd@macosforge.org>
Message-ID: <072.0670a23f65b42d21a9676971f733ffa1@macosforge.org>

#377: macgem crashes while installing any gem
----------------------------------------------+-----------------------------
 Reporter:  amadeusz.jasak+macruby@?          |       Owner:  lsansonetti@?        
     Type:  defect                            |      Status:  new                  
 Priority:  blocker                           |   Milestone:  MacRuby 0.5          
Component:  MacRuby                           |    Keywords:  macgem, gem          
----------------------------------------------+-----------------------------

Comment(by amadeusz.jasak+macruby@?):

 Adding to [ticket:377 amadeusz.jasak+macruby@?]:
 > Hi,
 > I've installed the latest daily build of MacRuby (09.10.09), I used to
 use MacRuby few months ago without any problems. I've upgraded to Snow
 Leopard and Xcode 3.2 so I needed the newest build.
 > There is a problem while installing any gem (dm-core, haml, sinatra...)
 eg.
 > {{{
 > bash-3.2# macruby -v
 > MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
 >
 > bash-3.2# macgem install dm-core
 > ERROR:  While executing gem ... (ArgumentError)
 >     Illformed requirement [nil]
 > }}}
 Not working on Macruby 0.5 beta 1 too... :(

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/377#comment:2>
MacRuby <http://macruby.org/>


From mattaimonetti at gmail.com  Sat Oct 10 11:54:57 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Sat, 10 Oct 2009 11:54:57 -0700
Subject: [MacRuby-devel] MacRuby 0.5 beta 1
In-Reply-To: <1E49EBB6-0B25-4322-A1AE-34F3E115B6BB@me.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
	<1E49EBB6-0B25-4322-A1AE-34F3E115B6BB@me.com>
Message-ID: <20fefa50910101154t6b694679j97bd5fd14f2d4917@mail.gmail.com>

Wayne, did you try Ernie's script?

Martin, we actually do, if you check the nightly builds page, and click on
details, you can see the logs and the spec results.

- Matt

On Sat, Oct 10, 2009 at 10:13 AM, Martin Hess <martinhess at me.com> wrote:

> Congratulations! Truly an amazing effort.
>
> Just curious, is there a webpage to view the daily rubyspec results in
> detail?
>
>
> On Oct 7, 2009, at 9:13 PM, Laurent Sansonetti wrote:
>
>  Hi,
>>
>> The first beta release of MacRuby 0.5 is out! I prepared some notes here:
>>
>> http://www.macruby.org/blog/2009/10/07/macruby05b1.html
>>
>> The goal is to go through a few beta releases before releasing the final
>> 0.5.
>>
>> Please give it a try and report us bugs & feedback :)
>>
>> Laurent
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091010/29be30c7/attachment.html>

From ruby-noreply at macosforge.org  Sat Oct 10 12:48:15 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 19:48:15 -0000
Subject: [MacRuby-devel] [MacRuby] #376: The second 'pointer' of a
 double pointer type is ignored
In-Reply-To: <050.e457ce96cd16850e431e499f112c297c@macosforge.org>
References: <050.e457ce96cd16850e431e499f112c297c@macosforge.org>
Message-ID: <059.4c44f55aca25ff2905377a681e2f1ec9@macosforge.org>

#376: The second 'pointer' of a double pointer type is ignored
---------------------------------+------------------------------------------
 Reporter:  mred@?               |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------

Comment(by lsansonetti@?):

 This looks like a regression in trunk. We should cover this behavior in
 spec/macruby/core/pointer_spec.rb.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/376#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 10 12:57:59 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 19:57:59 -0000
Subject: [MacRuby-devel] [MacRuby] #379: Nil symbol error.
Message-ID: <056.2718fa79ad0bd8b64a2104687014b985@macosforge.org>

#379: Nil symbol error.
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?              
     Type:  defect                     |      Status:  new                        
 Priority:  minor                      |   Milestone:  MacRuby 0.5                
Component:  MacRuby                    |    Keywords:  nil, symbol error, selector
---------------------------------------+------------------------------------
 When trying to use beginSheet method in this fashion:

 {{{
                 NSApp.beginSheet(@bookmarkSheet,
                         modalForWindow:@mainWindow,
                         modalDelegate:self,
                         didEndSelector:"bookmark_created",
                         contextInfo:nil)
 }}}

 when the containing method is run, I get an error:
 '''nil is not a symbol'''

 I have defined
 {{{
         attr_accessor :bookmarkSheet, :mainWindow
 }}}
 and have linked them in IB.

 Workaround is to create a dummy selector/method for the didEndSelector:
 parameter. Will work fine then.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/379>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 10 13:09:15 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 20:09:15 -0000
Subject: [MacRuby-devel] [MacRuby] #379: Nil symbol error.
In-Reply-To: <056.2718fa79ad0bd8b64a2104687014b985@macosforge.org>
References: <056.2718fa79ad0bd8b64a2104687014b985@macosforge.org>
Message-ID: <065.29b36e841dc2c6fc4d47843c37c8e647@macosforge.org>

#379: Nil symbol error.
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?              
     Type:  defect                     |      Status:  new                        
 Priority:  minor                      |   Milestone:  MacRuby 0.5                
Component:  MacRuby                    |    Keywords:  nil, symbol error, selector
---------------------------------------+------------------------------------

Comment(by mattaimonetti@?):

 Tanks for the bug report, we are going to look into it. For documentation
 sake, here is a link to the stackoverflow discussion:
 http://stackoverflow.com/questions/1548391/macruby-sheet-error

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/379#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 10 13:28:54 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 20:28:54 -0000
Subject: [MacRuby-devel] [MacRuby] #379: Nil symbol error.
In-Reply-To: <056.2718fa79ad0bd8b64a2104687014b985@macosforge.org>
References: <056.2718fa79ad0bd8b64a2104687014b985@macosforge.org>
Message-ID: <065.cc2a48e657a1c1081d7a7fdcd210908d@macosforge.org>

#379: Nil symbol error.
-----------------------------------------+----------------------------------
 Reporter:  hungerandthirst@?            |        Owner:  lsansonetti@?        
     Type:  defect                       |       Status:  closed               
 Priority:  minor                        |    Milestone:  MacRuby 0.5          
Component:  MacRuby                      |   Resolution:  fixed                
 Keywords:  nil, symbol error, selector  |  
-----------------------------------------+----------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Should be fixed in r2780.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/379#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 10 13:31:18 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 20:31:18 -0000
Subject: [MacRuby-devel] [MacRuby] #377: macgem crashes while installing
	any gem
In-Reply-To: <063.07f5d3ecfb29cc0c83bf30ea769b0bbd@macosforge.org>
References: <063.07f5d3ecfb29cc0c83bf30ea769b0bbd@macosforge.org>
Message-ID: <072.99f5a75b43451a2265b8588a34d20c41@macosforge.org>

#377: macgem crashes while installing any gem
----------------------------------------------+-----------------------------
 Reporter:  amadeusz.jasak+macruby@?          |       Owner:  lsansonetti@?        
     Type:  defect                            |      Status:  new                  
 Priority:  blocker                           |   Milestone:  MacRuby 0.5          
Component:  MacRuby                           |    Keywords:  macgem, gem          
----------------------------------------------+-----------------------------

Comment(by lsansonetti@?):

 Could you paste your ~/.gemrc file if you have one? Also, could you pass
 -V to `macgem install' and paste us the output?

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/377#comment:3>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 10 13:33:17 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 20:33:17 -0000
Subject: [MacRuby-devel] [MacRuby] #377: macgem crashes while installing
	any gem
In-Reply-To: <063.07f5d3ecfb29cc0c83bf30ea769b0bbd@macosforge.org>
References: <063.07f5d3ecfb29cc0c83bf30ea769b0bbd@macosforge.org>
Message-ID: <072.317b56cb895e6640b96a811ea42868f7@macosforge.org>

#377: macgem crashes while installing any gem
----------------------------------------------+-----------------------------
 Reporter:  amadeusz.jasak+macruby@?          |       Owner:  lsansonetti@?        
     Type:  defect                            |      Status:  new                  
 Priority:  blocker                           |   Milestone:  MacRuby 0.5          
Component:  MacRuby                           |    Keywords:  macgem, gem          
----------------------------------------------+-----------------------------

Comment(by lsansonetti@?):

 Also, were you able to install a gem before getting this problem? Is there
 anything in ~/.gem/macruby/1.9.0/gems or
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems?

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/377#comment:4>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Sat Oct 10 13:39:07 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Sat, 10 Oct 2009 13:39:07 -0700
Subject: [MacRuby-devel] Building MacRuby r2765 with llvm r82747
 failed	on core duo macbook, Leopard
In-Reply-To: <6e90f1240910100717y4a734ab9yea5617936841cdf2@mail.gmail.com>
References: <6e90f1240910090422g6c7a54cdxc7c521007fd1be60@mail.gmail.com>
	<75213076-B6F9-4945-9B72-87396B4392BB@apple.com>
	<6e90f1240910100717y4a734ab9yea5617936841cdf2@mail.gmail.com>
Message-ID: <6879A248-1C08-4100-83C4-689596158A1B@apple.com>

Hi,

On Oct 10, 2009, at 7:17 AM, hiroshi saito wrote:

> Hi Laurent,
>
> Thanks for pointing out possibility about llvm-gcc somewhere in the
> PATH. That's right. I found llvm-gcc in /Developer/usr/bin.
> After removing /Developer/usr/bin from the PATH, I could successfully
> build llvm as an universal binary.

Cool.

> However, as for MacRuby itself, libmacruby.dylib and macruby is OK
> with allow_build_warnings=true option, but aot_compile_stdlib is
> failed.
> I used MacRuby trunk r2779 this time.
>
>
> $ PATH=$PATH:~/Desktop/wc/MacRuby/llvm-trunk/Release/bin rake
> allow_build_warnings=true -t
> ...
> ** Invoke macruby:dylib
> ** Execute aot_compile_stdlib
> ./miniruby -I. -I./lib bin/rubyc --internal -C "rbconfig.rb" -o "./ 
> rbconfig.rbo"
> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c:2: error:
> expected initializer before ?-? token
> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c: In function
> ?void __init__()?:
> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c:5: error:
> ?MREP_? was not declared in this scope
> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c:5: error:
> ?107041289? cannot be used as a function
> Error when executing `/usr/bin/g++
> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c -dynamic
> -bundle -undefined suppress -flat_namespace -arch x86_64 -L. -lmacruby
> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.o -o
> ./rbconfig.rbo'
> rake aborted!

Strange. Could you try the following in the same directory and paste  
us the output?

$ ./miniruby -I. -I./lib bin/rubyc --internal -C "rbconfig.rb" -o "./ 
rbconfig.rbo" -V

> The content of /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/ 
> main.c is:
> extern "C" {
>  void *MREP_-107041289(void *, void *);
>  void *rb_vm_top_self(void);
>  __attribute__((constructor)) static void __init__(void) {
>    MREP_-107041289(rb_vm_top_self(), 0);
>  }
> }

Looks like the unique ID is negative. Maybe a bug of macrubyc.

> FYI, the warnings I forced to ignore with allow_build_warnings=true
> are those below. I wonder this is happened by not installing llvm, but
> specifying it's location with "PATH".
>
>
> /usr/bin/g++ -I/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include
> -I/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include  -D_DEBUG
> -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -O3
> -fno-common -Woverloaded-virtual -I. -I./include -g -Wall -arch i386
> -arch x86_64 -Winline --param inline-unit-growth=10000 --param
> large-function-growth=10000 -x objective-c++ -c dispatcher.cpp -o
> dispatcher.o
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:417:
> warning: ?void llvm::PATypeHandle::addUser()? was used before it was
> declared inline
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/ 
> AbstractTypeUser.h:95:
> warning: previous non-inline declaration here
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:422:
> warning: ?void llvm::PATypeHandle::removeUser()? was used before it
> was declared inline
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/ 
> AbstractTypeUser.h:96:
> warning: previous non-inline declaration here
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:434:
> warning: ?llvm::Type* llvm::PATypeHolder::get() const? was used before
> it was declared inline
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/ 
> AbstractTypeUser.h:159:
> warning: previous non-inline declaration here
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:440:
> warning: ?void llvm::PATypeHolder::addRef()? was used before it was
> declared inline
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/ 
> AbstractTypeUser.h:182:
> warning: previous non-inline declaration here
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:446:
> warning: ?void llvm::PATypeHolder::dropRef()? was used before it was
> declared inline
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/ 
> AbstractTypeUser.h:183:
> warning: previous non-inline declaration here
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:417:
> warning: ?void llvm::PATypeHandle::addUser()? was used before it was
> declared inline
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/ 
> AbstractTypeUser.h:95:
> warning: previous non-inline declaration here
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:422:
> warning: ?void llvm::PATypeHandle::removeUser()? was used before it
> was declared inline
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/ 
> AbstractTypeUser.h:96:
> warning: previous non-inline declaration here
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:434:
> warning: ?llvm::Type* llvm::PATypeHolder::get() const? was used before
> it was declared inline
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/ 
> AbstractTypeUser.h:159:
> warning: previous non-inline declaration here
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:440:
> warning: ?void llvm::PATypeHolder::addRef()? was used before it was
> declared inline
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/ 
> AbstractTypeUser.h:182:
> warning: previous non-inline declaration here
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/Type.h:446:
> warning: ?void llvm::PATypeHolder::dropRef()? was used before it was
> declared inline
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/include/llvm/ 
> AbstractTypeUser.h:183:
> warning: previous non-inline declaration here

I never got these warnings before on several machines, we build with - 
Werror since months and nobody reported this problem too.

I suspect it has something to do with your LLVM installation, but I'm  
not sure. These warnings are probably because of -Winline that we only  
pass when building dispatcher.cpp (to make sure gcc won't lie to us).

Laurent

From ruby-noreply at macosforge.org  Sat Oct 10 13:47:14 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 20:47:14 -0000
Subject: [MacRuby-devel] [MacRuby] #377: macgem crashes while installing
	any gem
In-Reply-To: <063.07f5d3ecfb29cc0c83bf30ea769b0bbd@macosforge.org>
References: <063.07f5d3ecfb29cc0c83bf30ea769b0bbd@macosforge.org>
Message-ID: <072.861a03736f89d31733425143eacefb6c@macosforge.org>

#377: macgem crashes while installing any gem
----------------------------------------------+-----------------------------
 Reporter:  amadeusz.jasak+macruby@?          |       Owner:  lsansonetti@?        
     Type:  defect                            |      Status:  new                  
 Priority:  blocker                           |   Milestone:  MacRuby 0.5          
Component:  MacRuby                           |    Keywords:  macgem, gem          
----------------------------------------------+-----------------------------

Comment(by amadeusz.jasak+macruby@?):

 I could use gems in previous versions.
 There were some gems in gems directories, but none of them were working :(
 So I removed contents of gems/ and after
 {{{
 $ sudo macgem install -V dm-core
 Installing gem extlib-0.9.13
 Downloading gem extlib-0.9.13.gem
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/LICENSE
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/README
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/Rakefile
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/History.txt
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/array.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/assertions.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/blank.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/boolean.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/byte_array.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/class.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/datetime.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/dictionary.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/hash.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/hook.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/inflection.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/lazy_array.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/lazy_module.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/logger.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/mash.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/module.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/nil.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/numeric.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/object.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/object_space.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/pathname.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/pooling.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/rubygems.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/simple_set.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/string.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/struct.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/symbol.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/tasks/release.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/time.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/version.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib/virtual_file.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/lib/extlib.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/array_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/blank_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/byte_array_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/class_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/datetime_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/hash_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/hook_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/inflection/plural_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/inflection/singular_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/inflection_extras_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/lazy_array_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/lazy_module_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/mash_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/module_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/object_space_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/object_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/pooling_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/simple_set_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/spec.opts
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/spec_helper.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/string_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/struct_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/symbol_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/time_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/try_call_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/try_dup_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/extlib-0.9.13/spec/virtual_file_spec.rb

 Installing gem addressable-2.1.0
 Downloading gem addressable-2.1.0.gem
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/lib/addressable/idna.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/lib/addressable/template.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/lib/addressable/uri.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/lib/addressable/version.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/spec/addressable/idna_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/spec/addressable/template_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/spec/addressable/uri_spec.rb
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/spec/data/rfc3986.txt
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/tasks/clobber.rake
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/tasks/gem.rake
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/tasks/git.rake
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/tasks/metrics.rake
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/tasks/rdoc.rake
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/tasks/rubyforge.rake
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/tasks/spec.rake
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/website/index.html
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/CHANGELOG
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/LICENSE
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/Rakefile
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0/gems/addressable-2.1.0/README
 ERROR:  While executing gem ... (ArgumentError)
     Illformed requirement [nil]
 }}}

 Now there are both addressable and extlib gems installed, but not dm-core,
 because macgem crashed. What is interesting
 {{{
 $ macirb
 irb(main):001:0> require 'rubygems'
 => true
 irb(main):002:0> require 'extlib'
 => true
 irb(main):003:0> require 'addressable/uri'
 LoadError: no such file to load -- addressable/uri
         from core:in `raise:'
         from core:in `require:'
 }}}
 So I can load only the first gem not the second, what is pretty strange -
 dm-core is still not installed.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/377#comment:5>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 10 13:53:48 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 20:53:48 -0000
Subject: [MacRuby-devel] [MacRuby] #377: macgem crashes while installing
	any gem
In-Reply-To: <063.07f5d3ecfb29cc0c83bf30ea769b0bbd@macosforge.org>
References: <063.07f5d3ecfb29cc0c83bf30ea769b0bbd@macosforge.org>
Message-ID: <072.a79d80edd98bb4a3ea5aca488e4671b5@macosforge.org>

#377: macgem crashes while installing any gem
----------------------------------------------+-----------------------------
 Reporter:  amadeusz.jasak+macruby@?          |       Owner:  lsansonetti@?        
     Type:  defect                            |      Status:  new                  
 Priority:  blocker                           |   Milestone:  MacRuby 0.5          
Component:  MacRuby                           |    Keywords:  macgem, gem          
----------------------------------------------+-----------------------------

Comment(by lsansonetti@?):

 I was able to install the dm-core gem on my environment but it cannot be
 loaded after because bigdecimal has not been implemented yet.

 {{{
 $ macgem install dm-core
 WARNING:  Installing to ~/.gem since
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0
 and
           /usr/bin aren't both writable.
 WARNING:  You don't have /Users/lrz/.gem/macruby/1.9.0/bin in your PATH,
           gem executables will not run.
 Successfully installed extlib-0.9.13
 Successfully installed addressable-2.1.0
 Successfully installed dm-core-0.10.1
 3 gems installed
 $ macruby -r rubygems -e "require 'dm-core'; p 42"
 core:in `raise:': no such file to load -- bigdecimal (LoadError)
         from core:in `require:'
 }}}

 It looks like there is something wrong in your environment. It would be
 interesting to investigate where exactly in rubygems this "Illformed
 requirement [nil]" exception is raised.

 Also, could you try the following: `VM_DISABLE_RBO=1 macgem install dm-
 core' and let us know if it still fails.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/377#comment:6>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 10 14:03:15 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 10 Oct 2009 21:03:15 -0000
Subject: [MacRuby-devel] [MacRuby] #377: macgem crashes while installing
	any gem
In-Reply-To: <063.07f5d3ecfb29cc0c83bf30ea769b0bbd@macosforge.org>
References: <063.07f5d3ecfb29cc0c83bf30ea769b0bbd@macosforge.org>
Message-ID: <072.476ed51c4fddc3bf4a95c62a02ff7e1e@macosforge.org>

#377: macgem crashes while installing any gem
----------------------------------------------+-----------------------------
 Reporter:  amadeusz.jasak+macruby@?          |       Owner:  lsansonetti@?        
     Type:  defect                            |      Status:  new                  
 Priority:  blocker                           |   Milestone:  MacRuby 0.5          
Component:  MacRuby                           |    Keywords:  macgem, gem          
----------------------------------------------+-----------------------------

Comment(by amadeusz.jasak+macruby@?):

 `VM_DISABLE_RBO=1 macgem install dm-core` doesn't change anything... Good
 to know that DataMapper woudn't work anyway. But I still want to solve my
 problem.

 According to
 [http://www.google.com/codesearch?hl=en&sa=N&q=%22Illformed+requirement%22++lang:ruby&ct=rr&cs_r=lang:ruby]
 this error means there is something wrong with version string parser.
 Because it's nil (`Illformed requirement [nil]`, isn't it?) it cannot work
 correctly. The question is why it's nil?

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/377#comment:7>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 10 18:45:16 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 11 Oct 2009 01:45:16 -0000
Subject: [MacRuby-devel] [MacRuby] #380: issues with Set
Message-ID: <054.8d7f82f758d7cc81f6817e299532c1a8@macosforge.org>

#380: issues with Set
-------------------------------------+--------------------------------------
 Reporter:  mattaimonetti@?          |       Owner:  lsansonetti@?        
     Type:  defect                   |      Status:  new                  
 Priority:  blocker                  |   Milestone:  MacRuby 0.5          
Component:  MacRuby                  |    Keywords:                       
-------------------------------------+--------------------------------------
 {{{
 macruby -e "require 'rubygems'; require 'set'; raw =
 Set.new(Gem.cache.map{|gem_data| gem_data}); puts raw.inspect"
 }}}


 {{{
 uncaught Objective-C/C++ exception...
 2009-10-10 18:42:47.441 macruby[48074:903] *** Terminating app due to
 uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSCFSet
 count]: method sent to an uninitialized mutable set object'
 *** Call stack at first throw:
 (
         0   CoreFoundation                      0x00007fff8454f5a4
 __exceptionPreprocess + 180
         1   libobjc.A.dylib                     0x00007fff804e1313
 objc_exception_throw + 45
         2   CoreFoundation                      0x00007fff845a8c33
 -[__NSPlaceholderSet count] + 163
         3   CoreFoundation                      0x00007fff8455bb99 -[NSSet
 countByEnumeratingWithState:objects:count:] + 169
         4   CoreFoundation                      0x00007fff845a9662 -[NSSet
 _applyValues:context:] + 114
         5   CoreFoundation                      0x00007fff844d6929
 CFSetApplyFunction + 89
         6   libmacruby.dylib                    0x00000001000e2220
 rb_set_each + 48
         7   libmacruby.dylib                    0x000000010015faa7
 rb_vm_call_with_cache2 + 4663
         8   libmacruby.dylib                    0x0000000100037696
 enum_to_a + 86
         9   libmacruby.dylib                    0x000000010016d62c
 rb_vm_dispatch + 5996
         10  ???                                 0x000000010112dcb9 0x0 +
 4312980665
         11  ???                                 0x0000000101100239 0x0 +
 4312793657
         12  libmacruby.dylib                    0x000000010003f8d9
 ruby_run_node + 73
         13  macruby                             0x0000000100000dd8 main +
 152
         14  macruby                             0x0000000100000d34 start +
 52
         15  ???                                 0x0000000000000003 0x0 + 3
 )
 terminate called after throwing an instance of 'NSException'
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/380>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 10 21:15:44 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 11 Oct 2009 04:15:44 -0000
Subject: [MacRuby-devel] [MacRuby] #380: issues with Set
In-Reply-To: <054.8d7f82f758d7cc81f6817e299532c1a8@macosforge.org>
References: <054.8d7f82f758d7cc81f6817e299532c1a8@macosforge.org>
Message-ID: <063.a59956e80eeff1385a144c3dcd1a6d37@macosforge.org>

#380: issues with Set
-------------------------------------+--------------------------------------
 Reporter:  mattaimonetti@?          |       Owner:  lsansonetti@?        
     Type:  defect                   |      Status:  new                  
 Priority:  blocker                  |   Milestone:  MacRuby 0.5          
Component:  MacRuby                  |    Keywords:                       
-------------------------------------+--------------------------------------

Old description:

> {{{
> macruby -e "require 'rubygems'; require 'set'; raw =
> Set.new(Gem.cache.map{|gem_data| gem_data}); puts raw.inspect"
> }}}
>

> {{{
> uncaught Objective-C/C++ exception...
> 2009-10-10 18:42:47.441 macruby[48074:903] *** Terminating app due to
> uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSCFSet
> count]: method sent to an uninitialized mutable set object'
> *** Call stack at first throw:
> (
>         0   CoreFoundation                      0x00007fff8454f5a4
> __exceptionPreprocess + 180
>         1   libobjc.A.dylib                     0x00007fff804e1313
> objc_exception_throw + 45
>         2   CoreFoundation                      0x00007fff845a8c33
> -[__NSPlaceholderSet count] + 163
>         3   CoreFoundation                      0x00007fff8455bb99
> -[NSSet countByEnumeratingWithState:objects:count:] + 169
>         4   CoreFoundation                      0x00007fff845a9662
> -[NSSet _applyValues:context:] + 114
>         5   CoreFoundation                      0x00007fff844d6929
> CFSetApplyFunction + 89
>         6   libmacruby.dylib                    0x00000001000e2220
> rb_set_each + 48
>         7   libmacruby.dylib                    0x000000010015faa7
> rb_vm_call_with_cache2 + 4663
>         8   libmacruby.dylib                    0x0000000100037696
> enum_to_a + 86
>         9   libmacruby.dylib                    0x000000010016d62c
> rb_vm_dispatch + 5996
>         10  ???                                 0x000000010112dcb9 0x0 +
> 4312980665
>         11  ???                                 0x0000000101100239 0x0 +
> 4312793657
>         12  libmacruby.dylib                    0x000000010003f8d9
> ruby_run_node + 73
>         13  macruby                             0x0000000100000dd8 main +
> 152
>         14  macruby                             0x0000000100000d34 start
> + 52
>         15  ???                                 0x0000000000000003 0x0 +
> 3
> )
> terminate called after throwing an instance of 'NSException'
> }}}

New description:

 {{{
 macruby -e "require 'rubygems'; require 'set'; raw =
 Set.new(Gem.cache.map{|gem_data| gem_data}); puts raw.inspect"
 }}}


 {{{
 uncaught Objective-C/C++ exception...
 2009-10-10 18:42:47.441 macruby[48074:903] *** Terminating app due to
 uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSCFSet
 count]: method sent to an uninitialized mutable set object'
 *** Call stack at first throw:
 (
         0   CoreFoundation                      0x00007fff8454f5a4
 __exceptionPreprocess + 180
         1   libobjc.A.dylib                     0x00007fff804e1313
 objc_exception_throw + 45
         2   CoreFoundation                      0x00007fff845a8c33
 -[__NSPlaceholderSet count] + 163
         3   CoreFoundation                      0x00007fff8455bb99 -[NSSet
 countByEnumeratingWithState:objects:count:] + 169
         4   CoreFoundation                      0x00007fff845a9662 -[NSSet
 _applyValues:context:] + 114
         5   CoreFoundation                      0x00007fff844d6929
 CFSetApplyFunction + 89
         6   libmacruby.dylib                    0x00000001000e2220
 rb_set_each + 48
         7   libmacruby.dylib                    0x000000010015faa7
 rb_vm_call_with_cache2 + 4663
         8   libmacruby.dylib                    0x0000000100037696
 enum_to_a + 86
         9   libmacruby.dylib                    0x000000010016d62c
 rb_vm_dispatch + 5996
         10  ???                                 0x000000010112dcb9 0x0 +
 4312980665
         11  ???                                 0x0000000101100239 0x0 +
 4312793657
         12  libmacruby.dylib                    0x000000010003f8d9
 ruby_run_node + 73
         13  macruby                             0x0000000100000dd8 main +
 152
         14  macruby                             0x0000000100000d34 start +
 52
         15  ???                                 0x0000000000000003 0x0 + 3
 )
 terminate called after throwing an instance of 'NSException'
 }}}

--

Comment(by lsansonetti@?):

 I think it's time to get rid of set.c and use the pure ruby implementation
 again.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/380#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sun Oct 11 00:14:43 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 11 Oct 2009 07:14:43 -0000
Subject: [MacRuby-devel] [MacRuby] #381: Losing track of a defined constant
 - possibly related to Module.autoload
Message-ID: <052.ae2dc3fa4ad8e9ad59e8ff9e3fd9f5ff@macosforge.org>

#381: Losing track of a defined constant - possibly related to Module.autoload
-----------------------------------+----------------------------------------
 Reporter:  kamal.fariz@?          |       Owner:  lsansonetti@?             
     Type:  defect                 |      Status:  new                       
 Priority:  minor                  |   Milestone:  MacRuby 0.5               
Component:  MacRuby                |    Keywords:  autoload require constants
-----------------------------------+----------------------------------------
 There seems to be a bug in the interaction of autoload and requires. I
 tried hard to reduce this with no success. However, here is the smallest
 snippet that will illustrate this bug:

 {{{
 $ macruby -rubygems -rrack -r"rack/builder" -e "Rack::Builder"
 core:in `require:': uninitialized constant Rack::Builder (NameError)
 }}}

 If you remove the require to "rack/builder", MacRuby will autoload
 Rack::Builder normally and no exception will be raised.

 {{{
 $ macruby -rubygems -rrack -e "Rack::Builder"
 }}}

 in rack.rb, it defines

 {{{
 autoload :Builder, "rack/builder"
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/381>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sun Oct 11 01:48:41 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 11 Oct 2009 08:48:41 -0000
Subject: [MacRuby-devel] [MacRuby] #370: Inconsistency between macruby
 and ruby in a simple class
In-Reply-To: <052.3daa3c7849cf67ac174b377fd7b472a3@macosforge.org>
References: <052.3daa3c7849cf67ac174b377fd7b472a3@macosforge.org>
Message-ID: <061.fe52fc66a3d69a7f844493e550d90d3b@macosforge.org>

#370: Inconsistency between macruby and ruby in a simple class
-----------------------------------+----------------------------------------
 Reporter:  kfowler@?              |        Owner:  lsansonetti@?        
     Type:  defect                 |       Status:  closed               
 Priority:  major                  |    Milestone:  MacRuby 0.5          
Component:  MacRuby                |   Resolution:  fixed                
 Keywords:                         |  
-----------------------------------+----------------------------------------

Comment(by conradwt@?):

 I noticed that the output is printing extra '#-'.  For example,

 {{{

 ##-<M:0x200010980 @m=##-<W:0x2000109c0 @w=1>>

 }}}

 when it should be represented as

 {{{

 #<M:0x200010980 @m=#<W:0x2000109c0 @w=1>>

 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/370#comment:6>
MacRuby <http://macruby.org/>


From johnmacshea at gmail.com  Sun Oct 11 01:53:43 2009
From: johnmacshea at gmail.com (John Shea)
Date: Sun, 11 Oct 2009 10:53:43 +0200
Subject: [MacRuby-devel] macruby on iphone (again) - options and way forward
Message-ID: <2C127891-467F-422A-A5CC-69FFCDD7C1A4@gmail.com>

Hello everyone.

So I think this topic is going to rear its ugly/pretty head until a  
solution becomes available, and I myself would really like to be able  
to use macruby code on the iphone.

So I have put down my naive thoughts as to what are the issues.

I am a complete novice when it comes to GC, so I am sorry if this is  
all obvious or erroneous - but the important part is the discussion -  
which i hope many of you will add to.

Anyway it could be that I don't know enough about the subject to make  
sense of it. But a way to perhaps getting more people to work on  
getting macruby on the phone could be:

1. Describe the current GC situation on the mac & macruby in terms of  
architecture.
2. Describe an appropriate architecture for how GC would work on the  
iphone, how the programmer interacts with it in coding or compiling.
3. Describe the various parts of work that have to be done to to  
implement 2.
4. Make some suggestions of similar coding efforts or current code  
files or other references that people can use/copy to build a proof of  
principle

The following are my versions of 1 and 2:

Point 1:
My assumption is that currently macruby hooks into objective c's GC -  
autozone (this one ? http://www.opensource.apple.com/source/autozone/autozone-77.1/) 
  via ruby's ObjectSpace.

Point 2:
The iphone does not have GC so therefore in order to run macruby  
something needs to collect the garbage.

My other assumption is that you cannot run interpreted code on the  
iphone (or iphone simulator) so when developing for iphone the ruby  
code would need to be compiled during the build phase.

So I can think of two ways to do collect the garbage.

Firstly port autozone to the iphone - integrate macruby more or less  
as now - include it as a framework or something.
However,
   - i am concerned that the separate autozone thread(s) may not play  
well with the iphone processor
   - in addition the threads need to be interruptible, when phone  
calls come in or the home button is pressed - i can imagine including  
the autozone controller in the responder chain (in order to receive  
the shutdown command) would not be trivial.

I am wondering if the above complexity is why Laurent always refers to  
"emulating" autozone rather than including it or porting it.

The other option i can think of is in the build phase insert the  
necessary retains, releases and autoreleases into the code. By either:

	i) the developer including the calls manually, which are then  
compiled/translated to the appropriate C/ObjC commands. (I have gone  
off this idea a bit because the code would be hard to test in  
isolation (unless there were special compiler codes normally ignored  
by the ruby interpreter), and would make it hard to drop in any nice  
ruby code/libraries, and later on hard to fix code if an official GC  
ever arrives).

	ii) have a script which traverses the ruby code - and adds dealloc  
methods for instance methods, adds releases to scope bound variables  
etc, etc.
(I like this option the best, though i have little idea how to  
implement)

So do you all think i have described the situation properly?

If so perhaps someone (more knowledgeable) could provide some hints to  
points 3 and 4 above?

Or if i haven't described the situation properly then the whole stack  
of points 1-4 would (I think) help us move forward - and help people  
contribute to a solution.

Cheers,
John

From eloy.de.enige at gmail.com  Sun Oct 11 01:59:15 2009
From: eloy.de.enige at gmail.com (Eloy Duran)
Date: Sun, 11 Oct 2009 10:59:15 +0200
Subject: [MacRuby-devel] MacRuby 0.5 beta 1
In-Reply-To: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
Message-ID: <f52746ff0910110159x521dd84dt9b6c2d054e30c6f5@mail.gmail.com>

Laurent,

as they say in french; congratulations on le grande effort! \m/

Eloy

On Thursday, October 8, 2009, Laurent Sansonetti <lsansonetti at apple.com> wrote:
> Hi,
>
> The first beta release of MacRuby 0.5 is out! I prepared some notes here:
>
> http://www.macruby.org/blog/2009/10/07/macruby05b1.html
>
> The goal is to go through a few beta releases before releasing the final 0.5.
>
> Please give it a try and report us bugs & feedback :)
>
> Laurent
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>

From mattaimonetti at gmail.com  Sun Oct 11 02:02:19 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Sun, 11 Oct 2009 02:02:19 -0700
Subject: [MacRuby-devel] macruby on iphone (again) - options and way
	forward
In-Reply-To: <2C127891-467F-422A-A5CC-69FFCDD7C1A4@gmail.com>
References: <2C127891-467F-422A-A5CC-69FFCDD7C1A4@gmail.com>
Message-ID: <20fefa50910110202u134c1176j33931f0127ba7f9d@mail.gmail.com>

John, thanks for sharing, look for an email from Laurent from about a week
where he's explaining the plan for the iphone and what needs to be done to
release/retain objects. I think the thread should help you and you might
want to work with the other developer who already started looking into that.

- Matt

On Sun, Oct 11, 2009 at 1:53 AM, John Shea <johnmacshea at gmail.com> wrote:

> Hello everyone.
>
> So I think this topic is going to rear its ugly/pretty head until a
> solution becomes available, and I myself would really like to be able to use
> macruby code on the iphone.
>
> So I have put down my naive thoughts as to what are the issues.
>
> I am a complete novice when it comes to GC, so I am sorry if this is all
> obvious or erroneous - but the important part is the discussion - which i
> hope many of you will add to.
>
> Anyway it could be that I don't know enough about the subject to make sense
> of it. But a way to perhaps getting more people to work on getting macruby
> on the phone could be:
>
> 1. Describe the current GC situation on the mac & macruby in terms of
> architecture.
> 2. Describe an appropriate architecture for how GC would work on the
> iphone, how the programmer interacts with it in coding or compiling.
> 3. Describe the various parts of work that have to be done to to implement
> 2.
> 4. Make some suggestions of similar coding efforts or current code files or
> other references that people can use/copy to build a proof of principle
>
> The following are my versions of 1 and 2:
>
> Point 1:
> My assumption is that currently macruby hooks into objective c's GC -
> autozone (this one ?
> http://www.opensource.apple.com/source/autozone/autozone-77.1/) via ruby's
> ObjectSpace.
>
> Point 2:
> The iphone does not have GC so therefore in order to run macruby something
> needs to collect the garbage.
>
> My other assumption is that you cannot run interpreted code on the iphone
> (or iphone simulator) so when developing for iphone the ruby code would need
> to be compiled during the build phase.
>
> So I can think of two ways to do collect the garbage.
>
> Firstly port autozone to the iphone - integrate macruby more or less as now
> - include it as a framework or something.
> However,
>  - i am concerned that the separate autozone thread(s) may not play well
> with the iphone processor
>  - in addition the threads need to be interruptible, when phone calls come
> in or the home button is pressed - i can imagine including the autozone
> controller in the responder chain (in order to receive the shutdown command)
> would not be trivial.
>
> I am wondering if the above complexity is why Laurent always refers to
> "emulating" autozone rather than including it or porting it.
>
> The other option i can think of is in the build phase insert the necessary
> retains, releases and autoreleases into the code. By either:
>
>        i) the developer including the calls manually, which are then
> compiled/translated to the appropriate C/ObjC commands. (I have gone off
> this idea a bit because the code would be hard to test in isolation (unless
> there were special compiler codes normally ignored by the ruby interpreter),
> and would make it hard to drop in any nice ruby code/libraries, and later on
> hard to fix code if an official GC ever arrives).
>
>        ii) have a script which traverses the ruby code - and adds dealloc
> methods for instance methods, adds releases to scope bound variables etc,
> etc.
> (I like this option the best, though i have little idea how to implement)
>
> So do you all think i have described the situation properly?
>
> If so perhaps someone (more knowledgeable) could provide some hints to
> points 3 and 4 above?
>
> Or if i haven't described the situation properly then the whole stack of
> points 1-4 would (I think) help us move forward - and help people contribute
> to a solution.
>
> Cheers,
> John
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091011/d8a79d3d/attachment.html>

From wayneeseguin at gmail.com  Sun Oct 11 03:30:32 2009
From: wayneeseguin at gmail.com (Wayne Seguin)
Date: Sun, 11 Oct 2009 06:30:32 -0400
Subject: [MacRuby-devel] MacRuby 0.5 beta 1
In-Reply-To: <20fefa50910101154t6b694679j97bd5fd14f2d4917@mail.gmail.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
	<1E49EBB6-0B25-4322-A1AE-34F3E115B6BB@me.com>
	<20fefa50910101154t6b694679j97bd5fd14f2d4917@mail.gmail.com>
Message-ID: <0D6A7856-4B2F-45D6-9C47-7273DF34EFC6@gmail.com>

Not just yet but will be doing so asap.

   ~Wayne

On Oct 10, 2009, at 14:54 , Matt Aimonetti wrote:
> Wayne, did you try Ernie's script?
>
> Martin, we actually do, if you check the nightly builds page, and  
> click on details, you can see the logs and the spec results.
>
> - Matt
>
> On Sat, Oct 10, 2009 at 10:13 AM, Martin Hess <martinhess at me.com>  
> wrote:
> Congratulations! Truly an amazing effort.
>
> Just curious, is there a webpage to view the daily rubyspec results  
> in detail?
>
>
> On Oct 7, 2009, at 9:13 PM, Laurent Sansonetti wrote:
>
> Hi,
>
> The first beta release of MacRuby 0.5 is out! I prepared some notes  
> here:
>
> http://www.macruby.org/blog/2009/10/07/macruby05b1.html
>
> The goal is to go through a few beta releases before releasing the  
> final 0.5.
>
> Please give it a try and report us bugs & feedback :)
>
> Laurent
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091011/44e096cc/attachment-0001.html>

From jazzbox at 7zz.de  Sun Oct 11 08:55:21 2009
From: jazzbox at 7zz.de (B. Ohr)
Date: Sun, 11 Oct 2009 17:55:21 +0200
Subject: [MacRuby-devel] MacRuby 0.5 beta 1
In-Reply-To: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
Message-ID: <1F6A2A9D-98DB-4532-A256-9B1B51F7D6E4@7zz.de>

Hi Laurent,

I have to thank you (and all the others) for your great effort!

When I first saw Obj-C (~1993, I don?t remember exactly, I got a NeXT  
computer for testing purposes), my first thought was: What a weird  
language! At this moment absolutely nobody could foresee, that this  
will be the future language of choice for the Apple Macintosh.

I really hope, that MacRuby will become a fully useable alternative to  
Obj-C on the Mac! And the 0.5 is already very useable for a beta.  
Every time when I am doing something in MacRuby (and have to look at  
Obj-C examples), I can only say: I love that language!

Bernd

Am 08.10.2009 um 06:13 schrieb Laurent Sansonetti:

> Hi,
>
> The first beta release of MacRuby 0.5 is out! I prepared some notes  
> here:
>
> http://www.macruby.org/blog/2009/10/07/macruby05b1.html
>
> The goal is to go through a few beta releases before releasing the  
> final 0.5.
>
> Please give it a try and report us bugs & feedback :)
>
> Laurent
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From rice.audio at pobox.com  Sun Oct 11 09:19:58 2009
From: rice.audio at pobox.com (Robert Rice)
Date: Sun, 11 Oct 2009 12:19:58 -0400
Subject: [MacRuby-devel] NSTimer
Message-ID: <EC43033B-FD99-49F9-B2A9-925B146845CB@pobox.com>

Congratulations MacRuby Development Team:

My application almost runs now in MacRuby.

Is NSTimer class supported in MacRuby?

I was doing background processing using NSTimer as follows:

@timer = NSTimer.scheduledTimerWithTimeInterval( 5.0, :target,  
self, :selector, :periodicUpdate, :userInfo, nil, :repeats, true )

but this now gives me the error:

undefined method `scheduledTimerWithTimeInterval' for NSTimer:Class  
(NoMethodError)

Do you have a preferred method for doing backgound tasks in MacRuby -  
perhaps separate threads?

Thanks,
Bob Rice

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091011/0ea8908c/attachment.html>

From johnmacshea at gmail.com  Sun Oct 11 09:58:12 2009
From: johnmacshea at gmail.com (John Shea)
Date: Sun, 11 Oct 2009 18:58:12 +0200
Subject: [MacRuby-devel] NSTimer
In-Reply-To: <EC43033B-FD99-49F9-B2A9-925B146845CB@pobox.com>
References: <EC43033B-FD99-49F9-B2A9-925B146845CB@pobox.com>
Message-ID: <73E3617F-4E95-4D33-8ED1-1AAF102EDC44@gmail.com>

Hi Bob,

(you are going to kick yourself) you have misplaced the colon between  
target and self  - there is a comma there, and the colon has been  
placed in front of "target", so the method is not being recognised.

eg:
     @synchro_timer =  
NSTimer.scheduledTimerWithTimeInterval(TIME_INTERVAL, target:self,  
selector:"synchronise_with_server:", userInfo:nil, repeats:true)


as for threads - maybe someone else could chime in with a preference -  
but I do it the Cocoa way (eg http Connection delegates or timers) -  
but for data crunching using all cores I will use something like  
Laurent's barber shop code: http://www.macruby.org/blog/2009/10/07/macruby05b1.html 
.


J

On Oct 11, 2009, at 6:19 PM, Robert Rice wrote:

> Congratulations MacRuby Development Team:
>
> My application almost runs now in MacRuby.
>
> Is NSTimer class supported in MacRuby?
>
> I was doing background processing using NSTimer as follows:
>
> @timer = NSTimer.scheduledTimerWithTimeInterval( 5.0, :target,  
> self, :selector, :periodicUpdate, :userInfo, nil, :repeats, true )
>
> but this now gives me the error:
>
> undefined method `scheduledTimerWithTimeInterval' for NSTimer:Class  
> (NoMethodError)
>
> Do you have a preferred method for doing backgound tasks in MacRuby  
> - perhaps separate threads?
>
> Thanks,
> Bob Rice
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091011/ba4006de/attachment.html>

From jkh at apple.com  Sun Oct 11 11:01:56 2009
From: jkh at apple.com (Jordan K. Hubbard)
Date: Sun, 11 Oct 2009 11:01:56 -0700
Subject: [MacRuby-devel] NSTimer
In-Reply-To: <EC43033B-FD99-49F9-B2A9-925B146845CB@pobox.com>
References: <EC43033B-FD99-49F9-B2A9-925B146845CB@pobox.com>
Message-ID: <B7548B5F-E18C-48B6-9ADA-BF8971567722@apple.com>


On Oct 11, 2009, at 9:19 AM, Robert Rice wrote:

> Do you have a preferred method for doing backgound tasks in MacRuby  
> - perhaps separate threads?

I would say GCD is probably your best bet for this, since you can  
simply arrange to have a ruby block execute when your timer fires.

Of course, now that I go looking for documentation in the MacRuby  
source tree which describes how to do timers "the ruby way", I can't  
find any, but I'm sure it's hiding in there somewhere, right guys? :)

- Jordan


From rice.audio at pobox.com  Sun Oct 11 11:45:59 2009
From: rice.audio at pobox.com (Robert Rice)
Date: Sun, 11 Oct 2009 14:45:59 -0400
Subject: [MacRuby-devel] NSTimer
In-Reply-To: <73E3617F-4E95-4D33-8ED1-1AAF102EDC44@gmail.com>
References: <EC43033B-FD99-49F9-B2A9-925B146845CB@pobox.com>
	<73E3617F-4E95-4D33-8ED1-1AAF102EDC44@gmail.com>
Message-ID: <AB361ECE-A359-47C0-8266-09D0C2721171@pobox.com>

Thanks John::

I wasn't familiar with this new syntax. I was using the old syntax  
"NSTimer.scheduledTimerWithTimeInterval_target_selector_userInfo_repeats 
" but I see it doesn't work in MacRuby.

MarRuby is giving me error messages without a traceback. Is there a  
way to enable tracebacks?

Bob Rice

On Oct 11, 2009, at 12:58 PM, John Shea wrote:

> Hi Bob,
>
> (you are going to kick yourself) you have misplaced the colon  
> between target and self  - there is a comma there, and the colon has  
> been placed in front of "target", so the method is not being  
> recognised.
>
> eg:
>     @synchro_timer = NSTimer.scheduledTimerWithTimeInterval 
> (TIME_INTERVAL, target:self, selector:"synchronise_with_server:",  
> userInfo:nil, repeats:true)
>
>
> as for threads - maybe someone else could chime in with a preference  
> - but I do it the Cocoa way (eg http Connection delegates or timers)  
> - but for data crunching using all cores I will use something like  
> Laurent's barber shop code: http://www.macruby.org/blog/2009/10/07/macruby05b1.html 
> .
>
>
> J
>
> On Oct 11, 2009, at 6:19 PM, Robert Rice wrote:
>
>> Congratulations MacRuby Development Team:
>>
>> My application almost runs now in MacRuby.
>>
>> Is NSTimer class supported in MacRuby?
>>
>> I was doing background processing using NSTimer as follows:
>>
>> @timer = NSTimer.scheduledTimerWithTimeInterval( 5.0, :target,  
>> self, :selector, :periodicUpdate, :userInfo, nil, :repeats, true )
>>
>> but this now gives me the error:
>>
>> undefined method `scheduledTimerWithTimeInterval' for NSTimer:Class  
>> (NoMethodError)
>>
>> Do you have a preferred method for doing backgound tasks in MacRuby  
>> - perhaps separate threads?
>>
>> Thanks,
>> Bob Rice
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091011/743d8222/attachment-0001.html>

From mattaimonetti at gmail.com  Sun Oct 11 11:49:55 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Sun, 11 Oct 2009 11:49:55 -0700
Subject: [MacRuby-devel] NSTimer
In-Reply-To: <AB361ECE-A359-47C0-8266-09D0C2721171@pobox.com>
References: <EC43033B-FD99-49F9-B2A9-925B146845CB@pobox.com>
	<73E3617F-4E95-4D33-8ED1-1AAF102EDC44@gmail.com>
	<AB361ECE-A359-47C0-8266-09D0C2721171@pobox.com>
Message-ID: <20fefa50910111149h91912c6ldb84240c8e59812@mail.gmail.com>

The "NSTimer.scheduledTimerWithTimeInterval_target_selector_userInfo_repeats"syntax
is the RubyCocoa syntax, you need to use the selector approach in MacRuby,
very much like obj-C.

If you are on 0.5 beta or a recent nightly build, you should get a
traceback, otherwise, you can still try to catch the exception and print out
the error message and backtrace:

begin
  raise "this is a test"
rescue Exception => e
  raise "#{e.message} #{e.backtrace}"
end

- Matt



On Sun, Oct 11, 2009 at 11:45 AM, Robert Rice <rice.audio at pobox.com> wrote:

> Thanks John::
> I wasn't familiar with this new syntax. I was using the old syntax
> "NSTimer.scheduledTimerWithTimeInterval_target_selector_userInfo_repeats"
> but I see it doesn't work in MacRuby.
>
> MarRuby is giving me error messages without a traceback. Is there a way to
> enable tracebacks?
>
> Bob Rice
>
> On Oct 11, 2009, at 12:58 PM, John Shea wrote:
>
> Hi Bob,
> (you are going to kick yourself) you have misplaced the colon between
> target and self  - there is a comma there, and the colon has been placed in
> front of "target", so the method is not being recognised.
>
> eg:
>     @synchro_timer = NSTimer.scheduledTimerWithTimeInterval(TIME_INTERVAL,
> target:self, selector:"synchronise_with_server:", userInfo:nil,
> repeats:true)
>
>
> as for threads - maybe someone else could chime in with a preference - but
> I do it the Cocoa way (eg http Connection delegates or timers) - but for
> data crunching using all cores I will use something like Laurent's barber
> shop code: http://www.macruby.org/blog/2009/10/07/macruby05b1.html.
>
>
> J
>
> On Oct 11, 2009, at 6:19 PM, Robert Rice wrote:
>
> Congratulations MacRuby Development Team:
> My application almost runs now in MacRuby.
>
> Is NSTimer class supported in MacRuby?
>
> I was doing background processing using NSTimer as follows:
>
> @timer = NSTimer.scheduledTimerWithTimeInterval( 5.0, :target, self,
> :selector, :periodicUpdate, :userInfo, nil, :repeats, true )
>
> but this now gives me the error:
>
> *undefined method `scheduledTimerWithTimeInterval' for NSTimer:Class
> (NoMethodError)*
> *
> *
> *Do you have a preferred method for doing backgound tasks in MacRuby -
> perhaps separate threads?
>
> Thanks,
> Bob Rice
>
> *
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091011/45e5cd56/attachment.html>

From ruby-noreply at macosforge.org  Sun Oct 11 12:48:40 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 11 Oct 2009 19:48:40 -0000
Subject: [MacRuby-devel] [MacRuby] #370: Inconsistency between macruby
 and ruby in a simple class
In-Reply-To: <052.3daa3c7849cf67ac174b377fd7b472a3@macosforge.org>
References: <052.3daa3c7849cf67ac174b377fd7b472a3@macosforge.org>
Message-ID: <061.331c4db9bcb36dff26e4d7a16d22f224@macosforge.org>

#370: Inconsistency between macruby and ruby in a simple class
-----------------------------------+----------------------------------------
 Reporter:  kfowler@?              |        Owner:  lsansonetti@?        
     Type:  defect                 |       Status:  closed               
 Priority:  major                  |    Milestone:  MacRuby 0.5          
Component:  MacRuby                |   Resolution:  fixed                
 Keywords:                         |  
-----------------------------------+----------------------------------------

Comment(by lsansonetti@?):

 Indeed, there seems to be a problem in #inspect when the receiver has at
 least one instance variable:

 {{{
 $ ./miniruby -e "class Foo; def initialize; @foo=42; end; end; p
 Foo.new.inspect"
 "##-<Foo:0x200025d20 @foo=42>"
 $ ruby19 -e "class Foo; def initialize; @foo=42; end; end; p
 Foo.new.inspect"
 "#<Foo:0x0000010086a3c0 @foo=42>"
 }}}

 Could you open a new ticket about this?

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/370#comment:7>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Sun Oct 11 12:54:39 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Sun, 11 Oct 2009 12:54:39 -0700
Subject: [MacRuby-devel] macruby on iphone (again) - options and way
	forward
In-Reply-To: <2C127891-467F-422A-A5CC-69FFCDD7C1A4@gmail.com>
References: <2C127891-467F-422A-A5CC-69FFCDD7C1A4@gmail.com>
Message-ID: <7ED40EC4-6AB2-44F1-A1AB-9929D38E5C36@apple.com>

Hi John :)

On Oct 11, 2009, at 1:53 AM, John Shea wrote:

> Hello everyone.
>
> So I think this topic is going to rear its ugly/pretty head until a  
> solution becomes available, and I myself would really like to be  
> able to use macruby code on the iphone.
>
> So I have put down my naive thoughts as to what are the issues.
>
> I am a complete novice when it comes to GC, so I am sorry if this is  
> all obvious or erroneous - but the important part is the discussion  
> - which i hope many of you will add to.
>
> Anyway it could be that I don't know enough about the subject to  
> make sense of it. But a way to perhaps getting more people to work  
> on getting macruby on the phone could be:
>
> 1. Describe the current GC situation on the mac & macruby in terms  
> of architecture.
> 2. Describe an appropriate architecture for how GC would work on the  
> iphone, how the programmer interacts with it in coding or compiling.
> 3. Describe the various parts of work that have to be done to to  
> implement 2.
> 4. Make some suggestions of similar coding efforts or current code  
> files or other references that people can use/copy to build a proof  
> of principle

I agree that having a description of the plan somewhere might help.

> The following are my versions of 1 and 2:
>
> Point 1:
> My assumption is that currently macruby hooks into objective c's GC  
> - autozone (this one ? http://www.opensource.apple.com/source/autozone/autozone-77.1/ 
> ) via ruby's ObjectSpace.
>
> Point 2:
> The iphone does not have GC so therefore in order to run macruby  
> something needs to collect the garbage.

These are correct.

> My other assumption is that you cannot run interpreted code on the  
> iphone (or iphone simulator) so when developing for iphone the ruby  
> code would need to be compiled during the build phase.

Also correct.

> So I can think of two ways to do collect the garbage.
>
> Firstly port autozone to the iphone - integrate macruby more or less  
> as now - include it as a framework or something.
> However,
>  - i am concerned that the separate autozone thread(s) may not play  
> well with the iphone processor
>  - in addition the threads need to be interruptible, when phone  
> calls come in or the home button is pressed - i can imagine  
> including the autozone controller in the responder chain (in order  
> to receive the shutdown command) would not be trivial.

One could technically port autozone to the iPhone so that the MacRuby  
runtime can still use it, but it wouldn't work for Cocoa APIs still.  
The version of Cocoa on the iPhone is not autozone-aware (objects  
can't be allocated from the autozone, no write barriers, etc.) so this  
solution would still need to use the default malloc zone for pure  
Objective-C objects and retain/release them.

> I am wondering if the above complexity is why Laurent always refers  
> to "emulating" autozone rather than including it or porting it.
>
> The other option i can think of is in the build phase insert the  
> necessary retains, releases and autoreleases into the code. By either:
>
> 	i) the developer including the calls manually, which are then  
> compiled/translated to the appropriate C/ObjC commands. (I have gone  
> off this idea a bit because the code would be hard to test in  
> isolation (unless there were special compiler codes normally ignored  
> by the ruby interpreter), and would make it hard to drop in any nice  
> ruby code/libraries, and later on hard to fix code if an official GC  
> ever arrives).
>
> 	ii) have a script which traverses the ruby code - and adds dealloc  
> methods for instance methods, adds releases to scope bound variables  
> etc, etc.
> (I like this option the best, though i have little idea how to  
> implement)

This is definitely the idea I have in mind. I think we can do both.  
First the compiler should be smart enough to automatically insert  
autorelease pools in the code. Second, the developer will still have  
the possibility to create an autorelease pool by himself for edge  
cases that the compiler is not able to handle.

Laurent

From rice.audio at pobox.com  Sun Oct 11 12:55:32 2009
From: rice.audio at pobox.com (Robert Rice)
Date: Sun, 11 Oct 2009 15:55:32 -0400
Subject: [MacRuby-devel] NSTimer
In-Reply-To: <20fefa50910111149h91912c6ldb84240c8e59812@mail.gmail.com>
References: <EC43033B-FD99-49F9-B2A9-925B146845CB@pobox.com>
	<73E3617F-4E95-4D33-8ED1-1AAF102EDC44@gmail.com>
	<AB361ECE-A359-47C0-8266-09D0C2721171@pobox.com>
	<20fefa50910111149h91912c6ldb84240c8e59812@mail.gmail.com>
Message-ID: <F645F4AC-181C-41A6-A790-A6D87CD9ED0C@pobox.com>

Hi Matt:

I  am using the most recent build.

I get a traceback for compile errors but not for execution errors on  
the NS run loop.

Bob

On Oct 11, 2009, at 2:49 PM, Matt Aimonetti wrote:

> The "NSTimer.
> scheduledTimerWithTimeInterval_target_selector_userInfo_repeats 
> "syntax is the RubyCocoa syntax, you need to use the selector  
> approach in MacRuby, very much like obj-C.
>
> If you are on 0.5 beta or a recent nightly build, you should get a  
> traceback, otherwise, you can still try to catch the exception and  
> print out the error message and backtrace:
>
> begin
>   raise "this is a test"
> rescue Exception => e
>   raise "#{e.message} #{e.backtrace}"
> end
>
> - Matt
>
>
>
> On Sun, Oct 11, 2009 at 11:45 AM, Robert Rice <rice.audio at pobox.com>  
> wrote:
> Thanks John::
>
> I wasn't familiar with this new syntax. I was using the old syntax  
> "NSTimer.scheduledTimerWithTimeInterval_target_selector_userInfo_repeats 
> " but I see it doesn't work in MacRuby.
>
> MarRuby is giving me error messages without a traceback. Is there a  
> way to enable tracebacks?
>
> Bob Rice
>
> On Oct 11, 2009, at 12:58 PM, John Shea wrote:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091011/3d024029/attachment.html>

From lsansonetti at apple.com  Sun Oct 11 12:58:33 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Sun, 11 Oct 2009 12:58:33 -0700
Subject: [MacRuby-devel] NSTimer
In-Reply-To: <F645F4AC-181C-41A6-A790-A6D87CD9ED0C@pobox.com>
References: <EC43033B-FD99-49F9-B2A9-925B146845CB@pobox.com>
	<73E3617F-4E95-4D33-8ED1-1AAF102EDC44@gmail.com>
	<AB361ECE-A359-47C0-8266-09D0C2721171@pobox.com>
	<20fefa50910111149h91912c6ldb84240c8e59812@mail.gmail.com>
	<F645F4AC-181C-41A6-A790-A6D87CD9ED0C@pobox.com>
Message-ID: <467B82C2-65C8-460A-B647-41D4DC67766D@apple.com>

In theory any runtime exception should be caught by the runloop and  
you should see a line in your Xcode console.

As for your timer question, using NSTimer is definitely good in case  
your callback doesn't do too much. Since this will all be run in the  
main thread through the run loop, if you see some performance problems  
it might be better to switch to a Thread instead.

Laurent

On Oct 11, 2009, at 12:55 PM, Robert Rice wrote:

> Hi Matt:
>
> I  am using the most recent build.
>
> I get a traceback for compile errors but not for execution errors on  
> the NS run loop.
>
> Bob
>
> On Oct 11, 2009, at 2:49 PM, Matt Aimonetti wrote:
>
>> The "NSTimer.
>> scheduledTimerWithTimeInterval_target_selector_userInfo_repeats 
>> "syntax is the RubyCocoa syntax, you need to use the selector  
>> approach in MacRuby, very much like obj-C.
>>
>> If you are on 0.5 beta or a recent nightly build, you should get a  
>> traceback, otherwise, you can still try to catch the exception and  
>> print out the error message and backtrace:
>>
>> begin
>>   raise "this is a test"
>> rescue Exception => e
>>   raise "#{e.message} #{e.backtrace}"
>> end
>>
>> - Matt
>>
>>
>>
>> On Sun, Oct 11, 2009 at 11:45 AM, Robert Rice  
>> <rice.audio at pobox.com> wrote:
>> Thanks John::
>>
>> I wasn't familiar with this new syntax. I was using the old syntax  
>> "NSTimer.scheduledTimerWithTimeInterval_target_selector_userInfo_repeats 
>> " but I see it doesn't work in MacRuby.
>>
>> MarRuby is giving me error messages without a traceback. Is there a  
>> way to enable tracebacks?
>>
>> Bob Rice
>>
>> On Oct 11, 2009, at 12:58 PM, John Shea wrote:
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From martinhess at me.com  Sun Oct 11 13:43:36 2009
From: martinhess at me.com (Martin Hess)
Date: Sun, 11 Oct 2009 13:43:36 -0700
Subject: [MacRuby-devel] MacRuby 0.5 beta 1
In-Reply-To: <20fefa50910101154t6b694679j97bd5fd14f2d4917@mail.gmail.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
	<1E49EBB6-0B25-4322-A1AE-34F3E115B6BB@me.com>
	<20fefa50910101154t6b694679j97bd5fd14f2d4917@mail.gmail.com>
Message-ID: <40907D63-99F1-46B6-AEBC-F97512C3CBB6@me.com>

Matt, Is this the page? http://macruby.icoretech.org/details/29 It  
doesn't really show which tests are failing/skipped.

On Oct 10, 2009, at 11:54 AM, Matt Aimonetti wrote:

> Wayne, did you try Ernie's script?
>
> Martin, we actually do, if you check the nightly builds page, and  
> click on details, you can see the logs and the spec results.
>
> - Matt
>
> On Sat, Oct 10, 2009 at 10:13 AM, Martin Hess <martinhess at me.com>  
> wrote:
> Congratulations! Truly an amazing effort.
>
> Just curious, is there a webpage to view the daily rubyspec results  
> in detail?
>
>
> On Oct 7, 2009, at 9:13 PM, Laurent Sansonetti wrote:
>
> Hi,
>
> The first beta release of MacRuby 0.5 is out! I prepared some notes  
> here:
>
> http://www.macruby.org/blog/2009/10/07/macruby05b1.html
>
> The goal is to go through a few beta releases before releasing the  
> final 0.5.
>
> Please give it a try and report us bugs & feedback :)
>
> Laurent
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091011/1333da3c/attachment.html>

From rice.audio at pobox.com  Sun Oct 11 13:45:50 2009
From: rice.audio at pobox.com (Robert Rice)
Date: Sun, 11 Oct 2009 16:45:50 -0400
Subject: [MacRuby-devel] NSTimer
In-Reply-To: <467B82C2-65C8-460A-B647-41D4DC67766D@apple.com>
References: <EC43033B-FD99-49F9-B2A9-925B146845CB@pobox.com>
	<73E3617F-4E95-4D33-8ED1-1AAF102EDC44@gmail.com>
	<AB361ECE-A359-47C0-8266-09D0C2721171@pobox.com>
	<20fefa50910111149h91912c6ldb84240c8e59812@mail.gmail.com>
	<F645F4AC-181C-41A6-A790-A6D87CD9ED0C@pobox.com>
	<467B82C2-65C8-460A-B647-41D4DC67766D@apple.com>
Message-ID: <EABBA7F8-5586-4F1F-9207-A45F27DF0C9E@pobox.com>

Hi Laurent:

NSTimer wil work well for my app except I will still need to use a  
thread to read data from my GPS receiver unless I can find a non- 
blocking serial I/O package.

I see that Apple has developed a "Core Location Framework" for the  
iPhone but I don't see any documentation to indicate that I could use  
it in a Cocoa environment. That would be a preferable solution not  
only for portability but also to solve the problem I have had for  
years with multiple applications trying to read data from my receiver  
at the same time. The Core Location Framework should work on OSX if it  
can find any suitable GPS receiver attached to the local network; then  
GPS nav apps could get the position info from the framework as on the  
iPhone. Is there any way to suggest this project to Apple?

Bob Rice


On Oct 11, 2009, at 3:58 PM, Laurent Sansonetti wrote:

> In theory any runtime exception should be caught by the runloop and  
> you should see a line in your Xcode console.
>
> As for your timer question, using NSTimer is definitely good in case  
> your callback doesn't do too much. Since this will all be run in the  
> main thread through the run loop, if you see some performance  
> problems it might be better to switch to a Thread instead.
>
> Laurent
>
> On Oct 11, 2009, at 12:55 PM, Robert Rice wrote:
>
>> Hi Matt:
>>
>> I  am using the most recent build.
>>
>> I get a traceback for compile errors but not for execution errors  
>> on the NS run loop.
>>
>> Bob
>>
>> On Oct 11, 2009, at 2:49 PM, Matt Aimonetti wrote:
>>


From jkh at apple.com  Sun Oct 11 14:10:09 2009
From: jkh at apple.com (Jordan K. Hubbard)
Date: Sun, 11 Oct 2009 14:10:09 -0700
Subject: [MacRuby-devel] NSTimer
In-Reply-To: <EABBA7F8-5586-4F1F-9207-A45F27DF0C9E@pobox.com>
References: <EC43033B-FD99-49F9-B2A9-925B146845CB@pobox.com>
	<73E3617F-4E95-4D33-8ED1-1AAF102EDC44@gmail.com>
	<AB361ECE-A359-47C0-8266-09D0C2721171@pobox.com>
	<20fefa50910111149h91912c6ldb84240c8e59812@mail.gmail.com>
	<F645F4AC-181C-41A6-A790-A6D87CD9ED0C@pobox.com>
	<467B82C2-65C8-460A-B647-41D4DC67766D@apple.com>
	<EABBA7F8-5586-4F1F-9207-A45F27DF0C9E@pobox.com>
Message-ID: <C670BEDA-2AD9-414E-AD76-9040864D980B@apple.com>


On Oct 11, 2009, at 1:45 PM, Robert Rice wrote:

> NSTimer wil work well for my app except I will still need to use a  
> thread to read data from my GPS receiver unless I can find a non- 
> blocking serial I/O package.

[ jkh jumps up and down yelling "GCD!  GCD!" until he is dragged away]

> The Core Location Framework should work on OSX if it can find any  
> suitable GPS receiver attached to the local network; then GPS nav  
> apps could get the position info from the framework as on the  
> iPhone. Is there any way to suggest this project to Apple?

File an enhancement request radar via http://bugreport.apple.com.   
Believe it or not, those do get read!

- Jordan


From cwdinfo at gmail.com  Sun Oct 11 14:29:55 2009
From: cwdinfo at gmail.com (s.ross)
Date: Sun, 11 Oct 2009 14:29:55 -0700
Subject: [MacRuby-devel] NSTimer
In-Reply-To: <C670BEDA-2AD9-414E-AD76-9040864D980B@apple.com>
References: <EC43033B-FD99-49F9-B2A9-925B146845CB@pobox.com>
	<73E3617F-4E95-4D33-8ED1-1AAF102EDC44@gmail.com>
	<AB361ECE-A359-47C0-8266-09D0C2721171@pobox.com>
	<20fefa50910111149h91912c6ldb84240c8e59812@mail.gmail.com>
	<F645F4AC-181C-41A6-A790-A6D87CD9ED0C@pobox.com>
	<467B82C2-65C8-460A-B647-41D4DC67766D@apple.com>
	<EABBA7F8-5586-4F1F-9207-A45F27DF0C9E@pobox.com>
	<C670BEDA-2AD9-414E-AD76-9040864D980B@apple.com>
Message-ID: <07D02979-419E-49EA-8023-151F3D9270EE@gmail.com>

Well in the meantime, doesn't a daemon that issues distributed  
notifications accomplish a similar goal?

Hunted and pecked from my iPhone

On Oct 11, 2009, at 2:10 PM, "Jordan K. Hubbard" <jkh at apple.com> wrote:

>
> On Oct 11, 2009, at 1:45 PM, Robert Rice wrote:
>
>> NSTimer wil work well for my app except I will still need to use a  
>> thread to read data from my GPS receiver unless I can find a non- 
>> blocking serial I/O package.
>
> [ jkh jumps up and down yelling "GCD!  GCD!" until he is dragged away]
>
>> The Core Location Framework should work on OSX if it can find any  
>> suitable GPS receiver attached to the local network; then GPS nav  
>> apps could get the position info from the framework as on the  
>> iPhone. Is there any way to suggest this project to Apple?
>
> File an enhancement request radar via http://bugreport.apple.com.   
> Believe it or not, those do get read!
>
> - Jordan
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

From rice.audio at pobox.com  Sun Oct 11 14:42:49 2009
From: rice.audio at pobox.com (Robert Rice)
Date: Sun, 11 Oct 2009 17:42:49 -0400
Subject: [MacRuby-devel] NSTimer
In-Reply-To: <C670BEDA-2AD9-414E-AD76-9040864D980B@apple.com>
References: <EC43033B-FD99-49F9-B2A9-925B146845CB@pobox.com>
	<73E3617F-4E95-4D33-8ED1-1AAF102EDC44@gmail.com>
	<AB361ECE-A359-47C0-8266-09D0C2721171@pobox.com>
	<20fefa50910111149h91912c6ldb84240c8e59812@mail.gmail.com>
	<F645F4AC-181C-41A6-A790-A6D87CD9ED0C@pobox.com>
	<467B82C2-65C8-460A-B647-41D4DC67766D@apple.com>
	<EABBA7F8-5586-4F1F-9207-A45F27DF0C9E@pobox.com>
	<C670BEDA-2AD9-414E-AD76-9040864D980B@apple.com>
Message-ID: <4599FD17-740B-42F1-B917-AF5F16DC8EB6@pobox.com>

Thanks: I filed the request.
Bob Rice

On Oct 11, 2009, at 5:10 PM, Jordan K. Hubbard wrote:

>
> On Oct 11, 2009, at 1:45 PM, Robert Rice wrote:
>
>> NSTimer wil work well for my app except I will still need to use a  
>> thread to read data from my GPS receiver unless I can find a non- 
>> blocking serial I/O package.
>
> [ jkh jumps up and down yelling "GCD!  GCD!" until he is dragged away]
>
>> The Core Location Framework should work on OSX if it can find any  
>> suitable GPS receiver attached to the local network; then GPS nav  
>> apps could get the position info from the framework as on the  
>> iPhone. Is there any way to suggest this project to Apple?
>
> File an enhancement request radar via http://bugreport.apple.com.   
> Believe it or not, those do get read!
>
> - Jordan
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>


From mattaimonetti at gmail.com  Sun Oct 11 15:59:41 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Sun, 11 Oct 2009 15:59:41 -0700
Subject: [MacRuby-devel] MacRuby 0.5 beta 1
In-Reply-To: <40907D63-99F1-46B6-AEBC-F97512C3CBB6@me.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
	<1E49EBB6-0B25-4322-A1AE-34F3E115B6BB@me.com>
	<20fefa50910101154t6b694679j97bd5fd14f2d4917@mail.gmail.com>
	<40907D63-99F1-46B6-AEBC-F97512C3CBB6@me.com>
Message-ID: <20fefa50910111559w7d1dee2cjc2fc1bd022d9d945@mail.gmail.com>

That's the page, it will list all the failing specs, to see the details of
the skipped tag, check:
http://svn.macosforge.org/repository/ruby/MacRuby/trunk/spec/frozen/tags/macruby/

- Matt



On Sun, Oct 11, 2009 at 1:43 PM, Martin Hess <martinhess at me.com> wrote:

> Matt, Is this the page? http://macruby.icoretech.org/details/29 It doesn't
> really show which tests are failing/skipped.
> On Oct 10, 2009, at 11:54 AM, Matt Aimonetti wrote:
>
> Wayne, did you try Ernie's script?
>
> Martin, we actually do, if you check the nightly builds page, and click on
> details, you can see the logs and the spec results.
>
> - Matt
>
> On Sat, Oct 10, 2009 at 10:13 AM, Martin Hess <martinhess at me.com> wrote:
>
>> Congratulations! Truly an amazing effort.
>>
>> Just curious, is there a webpage to view the daily rubyspec results in
>> detail?
>>
>>
>> On Oct 7, 2009, at 9:13 PM, Laurent Sansonetti wrote:
>>
>>  Hi,
>>>
>>> The first beta release of MacRuby 0.5 is out! I prepared some notes here:
>>>
>>> http://www.macruby.org/blog/2009/10/07/macruby05b1.html
>>>
>>> The goal is to go through a few beta releases before releasing the final
>>> 0.5.
>>>
>>> Please give it a try and report us bugs & feedback :)
>>>
>>> Laurent
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091011/7be20d24/attachment-0001.html>

From hiroshi3110 at gmail.com  Sun Oct 11 19:11:03 2009
From: hiroshi3110 at gmail.com (hiroshi saito)
Date: Mon, 12 Oct 2009 11:11:03 +0900
Subject: [MacRuby-devel] Building MacRuby r2765 with llvm r82747 failed
	on core duo macbook, Leopard
In-Reply-To: <6879A248-1C08-4100-83C4-689596158A1B@apple.com>
References: <6e90f1240910090422g6c7a54cdxc7c521007fd1be60@mail.gmail.com>
	<75213076-B6F9-4945-9B72-87396B4392BB@apple.com>
	<6e90f1240910100717y4a734ab9yea5617936841cdf2@mail.gmail.com>
	<6879A248-1C08-4100-83C4-689596158A1B@apple.com>
Message-ID: <6e90f1240910111911he1037c1x6bd5657fa0c40d5a@mail.gmail.com>

Hi Laurent,

> Strange. Could you try the following in the same directory and paste us the
> output?
>
> $ ./miniruby -I. -I./lib bin/rubyc --internal -C "rbconfig.rb" -o
> "./rbconfig.rbo" -V

MacRuby - Laurent ????????????

Hi Laurent,



$ ./miniruby -I. -I./lib bin/rubyc --internal -C "rbconfig.rb" -o
"./rbconfig.rbo" -V

$ PATH=$PATH:~/Desktop/wc/MacRuby/llvm-trunk/Release/bin ./miniruby
-I. -I./lib bin/rubyc --internal -C "rbconfig.rb" -o "./rbconfig.rbo"
-V
./miniruby --emit-llvm
"/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.bc"
MREP_-107041289 "rbconfig.rb"
/Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/Release/bin/llc -f
/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.bc
-o=/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.s
-march=x86-64 -enable-eh
/usr/bin/gcc -c -arch x86_64
/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.s -o
/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.o
/usr/bin/g++ /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c
-dynamic -bundle -undefined suppress -flat_namespace -arch x86_64 -L.
-lmacruby /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.o
-o ./rbconfig.rbo
/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c:2: error:
expected initializer before ?-? token
/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c: In function
?void __init__()?:
/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c:5: error:
?MREP_? was not declared in this scope
/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c:5: error:
?107041289? cannot be used as a function
Error when executing `/usr/bin/g++
/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c -dynamic
-bundle -undefined suppress -flat_namespace -arch x86_64 -L. -lmacruby
/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.o -o
./rbconfig.rbo'

At the line around 100 of bin/rubyc:

    init_func = "MREP_#{File.read(path).hash}"

I extracted this line and execute it with -e option

$ ./miniruby -I. -I./lib -e "p File.read('rbconfig.rb').hash"
-107041289

I suppose that String#hash method will return an integer, that could
be nagative value. I don't know why on other environments
the method return positive value everytime...

Anyway, I hack the line of code to continue like that:

Index: bin/rubyc
===================================================================
--- bin/rubyc   (revision 2779)
+++ bin/rubyc   (working copy)
@@ -96,7 +96,7 @@
     output ||= File.join(File.dirname(path), base + '.o')

     # Generate init function (must be unique).
-    init_func = "MREP_#{File.read(path).hash}"
+    init_func = "MREP_#{File.read(path).hash.abs}"

     # Compile the file into LLVM bitcode.
     bc = gen_tmpfile(base, 'bc')


It passed, but I got another error.

$ ./miniruby -I. -I./lib bin/rubyc --internal -C "lib/date.rb" -o "lib/date.rbo"
Error when executing `./miniruby --emit-llvm
"/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/date.bc"
MREP_146681552 "lib/date.rb"'
rake aborted!

The exact error of the executed subcommand is:

$ ./miniruby --emit-llvm
"/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/date.bc"
MREP_146681552 "lib/date.rb"
unrecognized literal `86400000000000' (class `Bignum' type 10)
zsh: abort      ./miniruby --emit-llvm  MREP_146681552 "lib/date.rb"

I doubt that numeric or integer part of my llvm or macruby went wrong,
it possibly caused by something bad in my environment.
If it is true, farther investigation will be waste of time to you and
me, I'm sorry, but I'll give up for now.


> I never got these warnings before on several machines, we build with -Werror
> since months and nobody reported this problem too.
>
> I suspect it has something to do with your LLVM installation, but I'm not
> sure. These warnings are probably because of -Winline that we only pass when
> building dispatcher.cpp (to make sure gcc won't lie to us).

I agreed that.

Thanks anyway.

From vincent.isambart at gmail.com  Sun Oct 11 19:42:51 2009
From: vincent.isambart at gmail.com (Vincent Isambart)
Date: Mon, 12 Oct 2009 11:42:51 +0900
Subject: [MacRuby-devel] Building MacRuby r2765 with llvm r82747 failed
	on core duo macbook, Leopard
In-Reply-To: <6e90f1240910111911he1037c1x6bd5657fa0c40d5a@mail.gmail.com>
References: <6e90f1240910090422g6c7a54cdxc7c521007fd1be60@mail.gmail.com>
	<75213076-B6F9-4945-9B72-87396B4392BB@apple.com>
	<6e90f1240910100717y4a734ab9yea5617936841cdf2@mail.gmail.com>
	<6879A248-1C08-4100-83C4-689596158A1B@apple.com>
	<6e90f1240910111911he1037c1x6bd5657fa0c40d5a@mail.gmail.com>
Message-ID: <145EF737-C6E6-45D6-AC61-459F2A76C4AC@gmail.com>


> At the line around 100 of bin/rubyc:
>
>    init_func = "MREP_#{File.read(path).hash}"
>
> I extracted this line and execute it with -e option
>
> $ ./miniruby -I. -I./lib -e "p File.read('rbconfig.rb').hash"
> -107041289
>
> I suppose that String#hash method will return an integer, that could
> be nagative value. I don't know why on other environments
> the method return positive value everytime...

Laurent, wouldn't it be better to use something like a SHA1:
require 'digest/sha1'
init_func = "MREP_#{Digest::SHA1.hexdigest(File.read(path))}"


From lsansonetti at apple.com  Sun Oct 11 22:01:06 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Sun, 11 Oct 2009 22:01:06 -0700
Subject: [MacRuby-devel] Building MacRuby r2765 with llvm r82747
 failed	on core duo macbook, Leopard
In-Reply-To: <145EF737-C6E6-45D6-AC61-459F2A76C4AC@gmail.com>
References: <6e90f1240910090422g6c7a54cdxc7c521007fd1be60@mail.gmail.com>
	<75213076-B6F9-4945-9B72-87396B4392BB@apple.com>
	<6e90f1240910100717y4a734ab9yea5617936841cdf2@mail.gmail.com>
	<6879A248-1C08-4100-83C4-689596158A1B@apple.com>
	<6e90f1240910111911he1037c1x6bd5657fa0c40d5a@mail.gmail.com>
	<145EF737-C6E6-45D6-AC61-459F2A76C4AC@gmail.com>
Message-ID: <858E4B0F-B088-4B16-8F51-C3FAB46E4FAA@apple.com>

On Oct 11, 2009, at 7:42 PM, Vincent Isambart wrote:
>> At the line around 100 of bin/rubyc:
>>
>>   init_func = "MREP_#{File.read(path).hash}"
>>
>> I extracted this line and execute it with -e option
>>
>> $ ./miniruby -I. -I./lib -e "p File.read('rbconfig.rb').hash"
>> -107041289
>>
>> I suppose that String#hash method will return an integer, that could
>> be nagative value. I don't know why on other environments
>> the method return positive value everytime...
>
> Laurent, wouldn't it be better to use something like a SHA1:
> require 'digest/sha1'
> init_func = "MREP_#{Digest::SHA1.hexdigest(File.read(path))}"

miniruby cannot load C extensions, so this isn't an option.

Laurent

From lsansonetti at apple.com  Sun Oct 11 22:10:40 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Sun, 11 Oct 2009 22:10:40 -0700
Subject: [MacRuby-devel] Building MacRuby r2765 with llvm r82747
 failed	on core duo macbook, Leopard
In-Reply-To: <6e90f1240910111911he1037c1x6bd5657fa0c40d5a@mail.gmail.com>
References: <6e90f1240910090422g6c7a54cdxc7c521007fd1be60@mail.gmail.com>
	<75213076-B6F9-4945-9B72-87396B4392BB@apple.com>
	<6e90f1240910100717y4a734ab9yea5617936841cdf2@mail.gmail.com>
	<6879A248-1C08-4100-83C4-689596158A1B@apple.com>
	<6e90f1240910111911he1037c1x6bd5657fa0c40d5a@mail.gmail.com>
Message-ID: <D651694C-BEB3-4D0A-ABB2-60382860BB68@apple.com>

Hi Hiroshi-san,

On Oct 11, 2009, at 7:11 PM, hiroshi saito wrote:

> Hi Laurent,
>
>> Strange. Could you try the following in the same directory and  
>> paste us the
>> output?
>>
>> $ ./miniruby -I. -I./lib bin/rubyc --internal -C "rbconfig.rb" -o
>> "./rbconfig.rbo" -V
>
> MacRuby - Laurent ????????????
>
> Hi Laurent,
>
>
>
> $ ./miniruby -I. -I./lib bin/rubyc --internal -C "rbconfig.rb" -o
> "./rbconfig.rbo" -V
>
> $ PATH=$PATH:~/Desktop/wc/MacRuby/llvm-trunk/Release/bin ./miniruby
> -I. -I./lib bin/rubyc --internal -C "rbconfig.rb" -o "./rbconfig.rbo"
> -V
> ./miniruby --emit-llvm
> "/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.bc"
> MREP_-107041289 "rbconfig.rb"
> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/Release/bin/llc -f
> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.bc
> -o=/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.s
> -march=x86-64 -enable-eh
> /usr/bin/gcc -c -arch x86_64
> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.s -o
> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.o
> /usr/bin/g++ /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c
> -dynamic -bundle -undefined suppress -flat_namespace -arch x86_64 -L.
> -lmacruby /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.o
> -o ./rbconfig.rbo
> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c:2: error:
> expected initializer before ?-? token
> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c: In function
> ?void __init__()?:
> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c:5: error:
> ?MREP_? was not declared in this scope
> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c:5: error:
> ?107041289? cannot be used as a function
> Error when executing `/usr/bin/g++
> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c -dynamic
> -bundle -undefined suppress -flat_namespace -arch x86_64 -L. -lmacruby
> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.o -o
> ./rbconfig.rbo'
>
> At the line around 100 of bin/rubyc:
>
>    init_func = "MREP_#{File.read(path).hash}"
>
> I extracted this line and execute it with -e option
>
> $ ./miniruby -I. -I./lib -e "p File.read('rbconfig.rb').hash"
> -107041289
>
> I suppose that String#hash method will return an integer, that could
> be nagative value. I don't know why on other environments
> the method return positive value everytime...

Indeed, it's weird that nobody reported that problem, yet.

> Anyway, I hack the line of code to continue like that:
>
> Index: bin/rubyc
> ===================================================================
> --- bin/rubyc   (revision 2779)
> +++ bin/rubyc   (working copy)
> @@ -96,7 +96,7 @@
>     output ||= File.join(File.dirname(path), base + '.o')
>
>     # Generate init function (must be unique).
> -    init_func = "MREP_#{File.read(path).hash}"
> +    init_func = "MREP_#{File.read(path).hash.abs}"
>
>     # Compile the file into LLVM bitcode.
>     bc = gen_tmpfile(base, 'bc')

I committed this change in r2781.

> It passed, but I got another error.
>
> $ ./miniruby -I. -I./lib bin/rubyc --internal -C "lib/date.rb" -o  
> "lib/date.rbo"
> Error when executing `./miniruby --emit-llvm
> "/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/date.bc"
> MREP_146681552 "lib/date.rb"'
> rake aborted!
>
> The exact error of the executed subcommand is:
>
> $ ./miniruby --emit-llvm
> "/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/date.bc"
> MREP_146681552 "lib/date.rb"
> unrecognized literal `86400000000000' (class `Bignum' type 10)
> zsh: abort      ./miniruby --emit-llvm  MREP_146681552 "lib/date.rb"
>
> I doubt that numeric or integer part of my llvm or macruby went wrong,
> it possibly caused by something bad in my environment.
> If it is true, farther investigation will be waste of time to you and
> me, I'm sorry, but I'll give up for now.

In fact, this crash is because of a limitation in the AOT compiler, I  
forgot to handle literal bignums.

$ ./miniruby --emit-llvm foo omg -e "p 1267650600228229401496703205376"
unrecognized literal `1267650600228229401496703205376' (class `Bignum'  
type 10)
Abort trap

In any case I will fix it. But I don't know yet why this problem hits  
you when compiling lib/date.rb. The same file appears to compile fine  
for the rest of us.

It's not a waste of time at all because you found legitimate bugs :-)  
???????????

Laurent

From lsansonetti at apple.com  Sun Oct 11 22:16:38 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Sun, 11 Oct 2009 22:16:38 -0700
Subject: [MacRuby-devel] Building MacRuby r2765 with llvm r82747
 failed	on core duo macbook, Leopard
In-Reply-To: <D651694C-BEB3-4D0A-ABB2-60382860BB68@apple.com>
References: <6e90f1240910090422g6c7a54cdxc7c521007fd1be60@mail.gmail.com>
	<75213076-B6F9-4945-9B72-87396B4392BB@apple.com>
	<6e90f1240910100717y4a734ab9yea5617936841cdf2@mail.gmail.com>
	<6879A248-1C08-4100-83C4-689596158A1B@apple.com>
	<6e90f1240910111911he1037c1x6bd5657fa0c40d5a@mail.gmail.com>
	<D651694C-BEB3-4D0A-ABB2-60382860BB68@apple.com>
Message-ID: <4FC96601-8505-47AA-9E10-54CCA1B7ACF9@apple.com>

On Oct 11, 2009, at 10:10 PM, Laurent Sansonetti wrote:
> Hi Hiroshi-san,
>
> On Oct 11, 2009, at 7:11 PM, hiroshi saito wrote:
>
>> Hi Laurent,
>>
>>> Strange. Could you try the following in the same directory and  
>>> paste us the
>>> output?
>>>
>>> $ ./miniruby -I. -I./lib bin/rubyc --internal -C "rbconfig.rb" -o
>>> "./rbconfig.rbo" -V
>>
>> MacRuby - Laurent ????????????
>>
>> Hi Laurent,
>>
>>
>>
>> $ ./miniruby -I. -I./lib bin/rubyc --internal -C "rbconfig.rb" -o
>> "./rbconfig.rbo" -V
>>
>> $ PATH=$PATH:~/Desktop/wc/MacRuby/llvm-trunk/Release/bin ./miniruby
>> -I. -I./lib bin/rubyc --internal -C "rbconfig.rb" -o "./rbconfig.rbo"
>> -V
>> ./miniruby --emit-llvm
>> "/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.bc"
>> MREP_-107041289 "rbconfig.rb"
>> /Users/hiroshi/Desktop/wc/MacRuby/llvm-trunk/Release/bin/llc -f
>> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.bc
>> -o=/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.s
>> -march=x86-64 -enable-eh
>> /usr/bin/gcc -c -arch x86_64
>> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.s -o
>> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.o
>> /usr/bin/g++ /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c
>> -dynamic -bundle -undefined suppress -flat_namespace -arch x86_64 -L.
>> -lmacruby /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/ 
>> rbconfig.o
>> -o ./rbconfig.rbo
>> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c:2: error:
>> expected initializer before ?-? token
>> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c: In function
>> ?void __init__()?:
>> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c:5: error:
>> ?MREP_? was not declared in this scope
>> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c:5: error:
>> ?107041289? cannot be used as a function
>> Error when executing `/usr/bin/g++
>> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/main.c -dynamic
>> -bundle -undefined suppress -flat_namespace -arch x86_64 -L. - 
>> lmacruby
>> /var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/rbconfig.o -o
>> ./rbconfig.rbo'
>>
>> At the line around 100 of bin/rubyc:
>>
>>   init_func = "MREP_#{File.read(path).hash}"
>>
>> I extracted this line and execute it with -e option
>>
>> $ ./miniruby -I. -I./lib -e "p File.read('rbconfig.rb').hash"
>> -107041289
>>
>> I suppose that String#hash method will return an integer, that could
>> be nagative value. I don't know why on other environments
>> the method return positive value everytime...
>
> Indeed, it's weird that nobody reported that problem, yet.
>
>> Anyway, I hack the line of code to continue like that:
>>
>> Index: bin/rubyc
>> ===================================================================
>> --- bin/rubyc   (revision 2779)
>> +++ bin/rubyc   (working copy)
>> @@ -96,7 +96,7 @@
>>    output ||= File.join(File.dirname(path), base + '.o')
>>
>>    # Generate init function (must be unique).
>> -    init_func = "MREP_#{File.read(path).hash}"
>> +    init_func = "MREP_#{File.read(path).hash.abs}"
>>
>>    # Compile the file into LLVM bitcode.
>>    bc = gen_tmpfile(base, 'bc')
>
> I committed this change in r2781.
>
>> It passed, but I got another error.
>>
>> $ ./miniruby -I. -I./lib bin/rubyc --internal -C "lib/date.rb" -o  
>> "lib/date.rbo"
>> Error when executing `./miniruby --emit-llvm
>> "/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/date.bc"
>> MREP_146681552 "lib/date.rb"'
>> rake aborted!
>>
>> The exact error of the executed subcommand is:
>>
>> $ ./miniruby --emit-llvm
>> "/var/folders/HQ/HQYJapbxHKW7ieZsqEt5-++++TI/-Tmp-/date.bc"
>> MREP_146681552 "lib/date.rb"
>> unrecognized literal `86400000000000' (class `Bignum' type 10)
>> zsh: abort      ./miniruby --emit-llvm  MREP_146681552 "lib/date.rb"
>>
>> I doubt that numeric or integer part of my llvm or macruby went  
>> wrong,
>> it possibly caused by something bad in my environment.
>> If it is true, farther investigation will be waste of time to you and
>> me, I'm sorry, but I'll give up for now.
>
> In fact, this crash is because of a limitation in the AOT compiler,  
> I forgot to handle literal bignums.
>
> $ ./miniruby --emit-llvm foo omg -e "p  
> 1267650600228229401496703205376"
> unrecognized literal `1267650600228229401496703205376' (class  
> `Bignum' type 10)
> Abort trap
>
> In any case I will fix it. But I don't know yet why this problem  
> hits you when compiling lib/date.rb. The same file appears to  
> compile fine for the rest of us.

Quick investigation:

$ ./miniruby -e 'p 86400000000000.class'
Fixnum
$ arch -i386 ./miniruby -e 'p 86400000000000.class'
Bignum

I think that your miniruby runs in 32-bit mode, which should be the  
case if your computer is a Core Duo as mentioned in the subject of  
this e-mail.

32-bit has not been tested a lot, which could explain these bugs :)

Laurent

From lsansonetti at apple.com  Sun Oct 11 22:35:27 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Sun, 11 Oct 2009 22:35:27 -0700
Subject: [MacRuby-devel] Building MacRuby r2765 with llvm r82747
 failed	on core duo macbook, Leopard
In-Reply-To: <D651694C-BEB3-4D0A-ABB2-60382860BB68@apple.com>
References: <6e90f1240910090422g6c7a54cdxc7c521007fd1be60@mail.gmail.com>
	<75213076-B6F9-4945-9B72-87396B4392BB@apple.com>
	<6e90f1240910100717y4a734ab9yea5617936841cdf2@mail.gmail.com>
	<6879A248-1C08-4100-83C4-689596158A1B@apple.com>
	<6e90f1240910111911he1037c1x6bd5657fa0c40d5a@mail.gmail.com>
	<D651694C-BEB3-4D0A-ABB2-60382860BB68@apple.com>
Message-ID: <AABAD730-C0BE-4E93-9954-6465FDCF73D3@apple.com>

On Oct 11, 2009, at 10:10 PM, Laurent Sansonetti wrote:
> In fact, this crash is because of a limitation in the AOT compiler,  
> I forgot to handle literal bignums.
>
> $ ./miniruby --emit-llvm foo omg -e "p  
> 1267650600228229401496703205376"
> unrecognized literal `1267650600228229401496703205376' (class  
> `Bignum' type 10)
> Abort trap

I fixed the problem in r2782.

$ cat t.rb
p 1267650600228229401496703205376
$ macrubyc t.rb -o /tmp/t
$ /tmp/t
1267650600228229401496703205376

Laurent

From hiroshi3110 at gmail.com  Mon Oct 12 01:50:57 2009
From: hiroshi3110 at gmail.com (hiroshi saito)
Date: Mon, 12 Oct 2009 17:50:57 +0900
Subject: [MacRuby-devel] Building MacRuby r2765 with llvm r82747 failed
	on core duo macbook,
	Leopard AND about regexp with non-ASCII characters
Message-ID: <6e90f1240910120150v19270a66m8a7bf094a7d5d309@mail.gmail.com>

Laurent, thanks for fixing the bignum issue. OK I'll continue.
After updating to r2782, my rubyc successfully compiled all of stdlib,
and WOW!, all of build task completed! Thanks!

One of my intention of building MacRuby 0.5 trunk by hand is checking
status of regular expression against non-ASCII characters.

As I wrote in the comment I'v left;
http://www.macruby.org/trac/ticket/94#comment:4

a very simple regular expression including a Japanese character
against a string contains same character doesn't match.

It's very important issue for us, Japanese, and, I suppose, other
non-ASCII character languages.

How about the status of supporting non-ASCII character?

On Mon, Oct 12, 2009 at 2:35 PM, Laurent Sansonetti
<lsansonetti at apple.com> wrote:
> On Oct 11, 2009, at 10:10 PM, Laurent Sansonetti wrote:
>>
>> In fact, this crash is because of a limitation in the AOT compiler, I
>> forgot to handle literal bignums.
>>
>> $ ./miniruby --emit-llvm foo omg -e "p 1267650600228229401496703205376"
>> unrecognized literal `1267650600228229401496703205376' (class `Bignum'
>> type 10)
>> Abort trap
>
> I fixed the problem in r2782.
>
> $ cat t.rb
> p 1267650600228229401496703205376
> $ macrubyc t.rb -o /tmp/t
> $ /tmp/t
> 1267650600228229401496703205376

From rice.audio at pobox.com  Mon Oct 12 08:15:04 2009
From: rice.audio at pobox.com (Robert Rice)
Date: Mon, 12 Oct 2009 11:15:04 -0400
Subject: [MacRuby-devel] Obj C objects
Message-ID: <30A973D6-8219-4176-AAB6-F5AE791AB301@pobox.com>

Hi Team:

Converting a RubyCocoa project to MacRuby should I convert my  
Objective C objects to normal Ruby objects (excluding NS objects) and  
get rid of the call to alloc?

Bob Rice


From jazzbox at 7zz.de  Mon Oct 12 09:04:40 2009
From: jazzbox at 7zz.de (B. Ohr)
Date: Mon, 12 Oct 2009 18:04:40 +0200
Subject: [MacRuby-devel] XCode MacRuby templates are generating .nib files
In-Reply-To: <30A973D6-8219-4176-AAB6-F5AE791AB301@pobox.com>
References: <30A973D6-8219-4176-AAB6-F5AE791AB301@pobox.com>
Message-ID: <CEEDE163-91C9-403C-B331-938220A2861F@7zz.de>

Hi,

the XCode MacRuby templates are generating .nib files instead of xib  
files (like Obj-C projects).

(.xib is better for diffs in git or svn)

Bernd

From gdeciantis at gmail.com  Mon Oct 12 11:39:23 2009
From: gdeciantis at gmail.com (Giampiero De Ciantis)
Date: Mon, 12 Oct 2009 14:39:23 -0400
Subject: [MacRuby-devel] Interesting spec failures
Message-ID: <D4237270-181F-4FC3-B1BB-18373D372E27@gmail.com>

I have been trying to run the specs and have found some weird issues  
with some of the behaviour

spec/frozen/core/kernel/spawn_spec.rb - in the "Kernel uses the  
current working directory as its working directory" it fails the test,  
but if you change the command line to use MacRuby instead of Ruby, it  
passes.

spec/frozen/library/socket/ipsocket/getaddress_spec.rb - in the  
"Socket::IPSocket#getaddress raises an error on unknown hostnames."  
The spec fails, but if run the same test on macirb it raises the  
appropriate socket error on an unknown host name.

Anyone know of environmental issues that might be causing this? I do  
'rake clean' often and still get these errors.


I am also getting an error "cat: stdin: Bad file descriptor" on the / 
spec/frozen/core/io/close_read_spec.rb spec, but it still passes.

Cheers,

-Gp





From lsansonetti at apple.com  Mon Oct 12 12:14:52 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Mon, 12 Oct 2009 12:14:52 -0700
Subject: [MacRuby-devel] Building MacRuby r2765 with llvm r82747
 failed	on core duo macbook,
 Leopard AND about regexp with non-ASCII characters
In-Reply-To: <6e90f1240910120150v19270a66m8a7bf094a7d5d309@mail.gmail.com>
References: <6e90f1240910120150v19270a66m8a7bf094a7d5d309@mail.gmail.com>
Message-ID: <03FD6F9F-0A85-4C9A-90C9-32EA997C8C31@apple.com>

On Oct 12, 2009, at 1:50 AM, hiroshi saito wrote:
> Laurent, thanks for fixing the bignum issue. OK I'll continue.
> After updating to r2782, my rubyc successfully compiled all of stdlib,
> and WOW!, all of build task completed! Thanks!

Nice :)

> One of my intention of building MacRuby 0.5 trunk by hand is checking
> status of regular expression against non-ASCII characters.
>
> As I wrote in the comment I'v left;
> http://www.macruby.org/trac/ticket/94#comment:4
>
> a very simple regular expression including a Japanese character
> against a string contains same character doesn't match.
>
> It's very important issue for us, Japanese, and, I suppose, other
> non-ASCII character languages.
>
> How about the status of supporting non-ASCII character?

That's right, currently regular expressions containing non-ASCII  
characters are not supported. This is a work in progress and you can  
be sure this will be fixed, of course. To make sure I won't forget I  
annotated the TODO file.

However, applying regular expressions to non-ASCII strings should work.

Laurent

From lsansonetti at apple.com  Mon Oct 12 12:15:34 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Mon, 12 Oct 2009 12:15:34 -0700
Subject: [MacRuby-devel] Obj C objects
In-Reply-To: <30A973D6-8219-4176-AAB6-F5AE791AB301@pobox.com>
References: <30A973D6-8219-4176-AAB6-F5AE791AB301@pobox.com>
Message-ID: <5FCC6A7E-C065-42E9-B66D-BA3EFF00F52D@apple.com>

Hi Robert,

Could you be more explicit? I don't understand your question :)

Thanks,

Laurent

On Oct 12, 2009, at 8:15 AM, Robert Rice wrote:

> Hi Team:
>
> Converting a RubyCocoa project to MacRuby should I convert my  
> Objective C objects to normal Ruby objects (excluding NS objects)  
> and get rid of the call to alloc?
>
> Bob Rice
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From lsansonetti at apple.com  Mon Oct 12 12:16:25 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Mon, 12 Oct 2009 12:16:25 -0700
Subject: [MacRuby-devel] XCode MacRuby templates are generating .nib
	files
In-Reply-To: <CEEDE163-91C9-403C-B331-938220A2861F@7zz.de>
References: <30A973D6-8219-4176-AAB6-F5AE791AB301@pobox.com>
	<CEEDE163-91C9-403C-B331-938220A2861F@7zz.de>
Message-ID: <15182A85-F29E-4090-8298-DFC5800C99FF@apple.com>

Indeed, .xib is probably the way to go now. if one wants to submit a  
patch for this I will merge it :)

Laurent

On Oct 12, 2009, at 9:04 AM, B. Ohr wrote:

> Hi,
>
> the XCode MacRuby templates are generating .nib files instead of xib  
> files (like Obj-C projects).
>
> (.xib is better for diffs in git or svn)
>
> Bernd
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

From lsansonetti at apple.com  Mon Oct 12 12:22:51 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Mon, 12 Oct 2009 12:22:51 -0700
Subject: [MacRuby-devel] Interesting spec failures
In-Reply-To: <D4237270-181F-4FC3-B1BB-18373D372E27@gmail.com>
References: <D4237270-181F-4FC3-B1BB-18373D372E27@gmail.com>
Message-ID: <63F3F88D-7893-4F40-A8D6-F112969F16F2@apple.com>

Hi Gp,

Yes there are several environmental issues when running RubySpec. For  
example I noticed that it will fail if you have a /tmp/xxx directory  
or if your $HOME is actually a symlink.

On Claudio's server I noticed a few more problems (you can see the  
failures from the nightly build website, under Tests).

One of my biggest issues with RubySpec is that it executes everything  
within the same process, so one spec could potentially damage the  
environment (because of a bug) so that another one might not pass (but  
executing a spec separately would work).

Laurent

On Oct 12, 2009, at 11:39 AM, Giampiero De Ciantis wrote:

> I have been trying to run the specs and have found some weird issues  
> with some of the behaviour
>
> spec/frozen/core/kernel/spawn_spec.rb - in the "Kernel uses the  
> current working directory as its working directory" it fails the  
> test, but if you change the command line to use MacRuby instead of  
> Ruby, it passes.
>
> spec/frozen/library/socket/ipsocket/getaddress_spec.rb - in the  
> "Socket::IPSocket#getaddress raises an error on unknown hostnames."  
> The spec fails, but if run the same test on macirb it raises the  
> appropriate socket error on an unknown host name.
>
> Anyone know of environmental issues that might be causing this? I do  
> 'rake clean' often and still get these errors.
>
>
> I am also getting an error "cat: stdin: Bad file descriptor" on the / 
> spec/frozen/core/io/close_read_spec.rb spec, but it still passes.
>
> Cheers,
>
> -Gp
>
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Mon Oct 12 13:09:52 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Mon, 12 Oct 2009 20:09:52 -0000
Subject: [MacRuby-devel] [MacRuby] #382: undefined constants in Snow Leopard
Message-ID: <049.ff9f578b42afb76b146b9b4fdde012b2@macosforge.org>

#382: undefined constants in Snow Leopard
--------------------------------+-------------------------------------------
 Reporter:  rich@?              |       Owner:  lsansonetti@?        
     Type:  defect              |      Status:  new                  
 Priority:  blocker             |   Milestone:                       
Component:  MacRuby             |    Keywords:                       
--------------------------------+-------------------------------------------
 In trying to get samples-macruby/Scripts/jumpy.rb to work, I noticed
 certain constants were not in the Bridge Support files in Snow Leopard.
 I added this to the top of jumpy.rb to fix the problem but we need these
 in a more central location:

 # these are not properly mapped in BridgeSupport in Snow Leopard (from
 GCGeometry.h)
 CGRectInfinite = CGRect.new([-8.98847e+307, -8.98847e+307], [1.79769e+308,
 1.79769e+308]) unless defined?(CGRectInfinite)
 CGSizeZero = CGSizeMake(0, 0) unless defined?(CGSizeZero)
 CGRectZero = CGRectMake(0, 0, 0, 0) unless defined?(CGRectZero)
 CGPointZero = CGPointMake(0, 0) unless defined?(CGPointZero)
 # we need CGRectNull!

 # these are not properly mapped in BridgeSupport in Snow Leopard (from
 CATransaction.h)
 KCATransactionAnimationDuration = 'animationDuration' unless
 defined?(KCATransactionAnimationDuration)
 KCATransactionDisableActions = 'disableActions' unless
 defined?(KCATransactionDisableActions)
 KCATransactionAnimationTimingFunction = 'animationTimingFunction' unless
 defined?(KCATransactionAnimationTimingFunction)
 KCATransactionCompletionBlock = 'completionBlock' unless
 defined?(KCATransactionCompletionBlock)

 # these are not properly mapped in BridgeSupport in Snow Leopard (from
 CAMediaTimingFunction.h)
 KCAMediaTimingFunctionEaseIn = 'easeIn' unless
 defined?(KCAMediaTimingFunctionEaseIn)
 KCAMediaTimingFunctionEaseOut = 'easeOut' unless
 defined?(KCAMediaTimingFunctionEaseOut)
 KCAMediaTimingFunctionLinear = 'linear' unless
 defined?(KCAMediaTimingFunctionLinear)
 KCAMediaTimingFunctionEaseInOut = 'easeInOut' unless
 defined?(KCAMediaTimingFunctionEaseInOut)

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/382>
MacRuby <http://macruby.org/>


From rice.audio at pobox.com  Mon Oct 12 14:00:43 2009
From: rice.audio at pobox.com (Robert Rice)
Date: Mon, 12 Oct 2009 17:00:43 -0400
Subject: [MacRuby-devel] Obj C objects
In-Reply-To: <5FCC6A7E-C065-42E9-B66D-BA3EFF00F52D@apple.com>
References: <30A973D6-8219-4176-AAB6-F5AE791AB301@pobox.com>
	<5FCC6A7E-C065-42E9-B66D-BA3EFF00F52D@apple.com>
Message-ID: <CC1F8129-121A-499F-BB6B-42B230B1DDC7@pobox.com>

Hi Laurent:

In my RubyCocoa code I found that I had to create Obj C objects (using  
alloc and an init call to super) to pass to NS tables since the UI  
keeps copies of my objects. If all objects in MacRuby are Objective C  
objects are the calls to alloc and to super still required?

Bob Rice


On Oct 12, 2009, at 3:15 PM, Laurent Sansonetti wrote:

> Hi Robert,
>
> Could you be more explicit? I don't understand your question :)
>
> Thanks,
>
> Laurent
>
> On Oct 12, 2009, at 8:15 AM, Robert Rice wrote:
>
>> Hi Team:
>>
>> Converting a RubyCocoa project to MacRuby should I convert my  
>> Objective C objects to normal Ruby objects (excluding NS objects)  
>> and get rid of the call to alloc?
>>
>> Bob Rice
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>


From lsansonetti at apple.com  Mon Oct 12 14:27:26 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Mon, 12 Oct 2009 14:27:26 -0700
Subject: [MacRuby-devel] Obj C objects
In-Reply-To: <CC1F8129-121A-499F-BB6B-42B230B1DDC7@pobox.com>
References: <30A973D6-8219-4176-AAB6-F5AE791AB301@pobox.com>
	<5FCC6A7E-C065-42E9-B66D-BA3EFF00F52D@apple.com>
	<CC1F8129-121A-499F-BB6B-42B230B1DDC7@pobox.com>
Message-ID: <B6DE4EB2-38BB-40B7-93EE-3C57FE74B80B@apple.com>

You can now pass true Ruby objects to a table or outline view  
datasource (since MacRuby doesn't use proxies) but keep in mind that  
you must always pass the same unique references and not copies, as  
mentioned in the documentation.

http://developer.apple.com/mac/library/documentation/Cocoa/Reference/ApplicationKit/Classes/NSOutlineView_Class/Reference/Reference.html

Also, check out the OutlineView sample code that ships with MacRuby as  
an example.

HTH,

Laurent

On Oct 12, 2009, at 2:00 PM, Robert Rice wrote:

> Hi Laurent:
>
> In my RubyCocoa code I found that I had to create Obj C objects  
> (using alloc and an init call to super) to pass to NS tables since  
> the UI keeps copies of my objects. If all objects in MacRuby are  
> Objective C objects are the calls to alloc and to super still  
> required?
>
> Bob Rice
>
>
> On Oct 12, 2009, at 3:15 PM, Laurent Sansonetti wrote:
>
>> Hi Robert,
>>
>> Could you be more explicit? I don't understand your question :)
>>
>> Thanks,
>>
>> Laurent
>>
>> On Oct 12, 2009, at 8:15 AM, Robert Rice wrote:
>>
>>> Hi Team:
>>>
>>> Converting a RubyCocoa project to MacRuby should I convert my  
>>> Objective C objects to normal Ruby objects (excluding NS objects)  
>>> and get rid of the call to alloc?
>>>
>>> Bob Rice
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From hiroshi3110 at gmail.com  Mon Oct 12 17:44:57 2009
From: hiroshi3110 at gmail.com (hiroshi saito)
Date: Tue, 13 Oct 2009 09:44:57 +0900
Subject: [MacRuby-devel] Building MacRuby r2765 with llvm r82747 failed
	on core duo macbook,
	Leopard AND about regexp with non-ASCII characters
In-Reply-To: <03FD6F9F-0A85-4C9A-90C9-32EA997C8C31@apple.com>
References: <6e90f1240910120150v19270a66m8a7bf094a7d5d309@mail.gmail.com>
	<03FD6F9F-0A85-4C9A-90C9-32EA997C8C31@apple.com>
Message-ID: <6e90f1240910121744r70ae2868j9d0b112c3fad9f26@mail.gmail.com>

Hi Laurent,

>> a very simple regular expression including a Japanese character
>> against a string contains same character doesn't match.
>>
>> It's very important issue for us, Japanese, and, I suppose, other
>> non-ASCII character languages.
>>
>> How about the status of supporting non-ASCII character?
>
> That's right, currently regular expressions containing non-ASCII characters
> are not supported. This is a work in progress and you can be sure this will
> be fixed, of course. To make sure I won't forget I annotated the TODO file.

I'm glad to hear that. I thank you as a Japanese.

> However, applying regular expressions to non-ASCII strings should work.

Yes, I know they do, and didn't in 0.4 :)

==========
Hiroshi Saito
hiroshi3110 at gmail.com
http://blog.yakitara.com/
http://github.com/hiroshi

From ruby-noreply at macosforge.org  Mon Oct 12 20:52:15 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 13 Oct 2009 03:52:15 -0000
Subject: [MacRuby-devel] [MacRuby] #373: protected methods aren't
In-Reply-To: <050.8b7f488c73e4ed24e710e6f09b814147@macosforge.org>
References: <050.8b7f488c73e4ed24e710e6f09b814147@macosforge.org>
Message-ID: <059.73a6d530b0e3606c4bce9c308a8773ce@macosforge.org>

#373: protected methods aren't
---------------------------------+------------------------------------------
 Reporter:  chrisw@?             |        Owner:  lsansonetti@?        
     Type:  defect               |       Status:  closed               
 Priority:  blocker              |    Milestone:  MacRuby 0.5          
Component:  MacRuby              |   Resolution:  fixed                
 Keywords:  protected access     |  
---------------------------------+------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Should be fixed in r2785.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/373#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct 12 21:30:42 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 13 Oct 2009 04:30:42 -0000
Subject: [MacRuby-devel] [MacRuby] #381: Losing track of a defined
 constant - possibly related to Module.autoload
In-Reply-To: <052.ae2dc3fa4ad8e9ad59e8ff9e3fd9f5ff@macosforge.org>
References: <052.ae2dc3fa4ad8e9ad59e8ff9e3fd9f5ff@macosforge.org>
Message-ID: <061.5cf773a20c125ad53cd76a912154324d@macosforge.org>

#381: Losing track of a defined constant - possibly related to Module.autoload
-----------------------------------+----------------------------------------
 Reporter:  kamal.fariz@?          |       Owner:  lsansonetti@?             
     Type:  defect                 |      Status:  new                       
 Priority:  minor                  |   Milestone:  MacRuby 0.5               
Component:  MacRuby                |    Keywords:  autoload require constants
-----------------------------------+----------------------------------------

Comment(by lsansonetti@?):

 Actually, #autoload has not been implemented yet.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/381#comment:1>
MacRuby <http://macruby.org/>


From eloy.de.enige at gmail.com  Tue Oct 13 00:34:19 2009
From: eloy.de.enige at gmail.com (Eloy Duran)
Date: Tue, 13 Oct 2009 09:34:19 +0200
Subject: [MacRuby-devel] Interesting spec failures
In-Reply-To: <63F3F88D-7893-4F40-A8D6-F112969F16F2@apple.com>
References: <D4237270-181F-4FC3-B1BB-18373D372E27@gmail.com>
	<63F3F88D-7893-4F40-A8D6-F112969F16F2@apple.com>
Message-ID: <9206A437-D85D-4C3D-B12B-760769367181@gmail.com>

Het Laurent,

Ishare your sentiment with regards to mspec/rubyspec on ? new  
implementation. However, we are now getting in ? state where, unless  
? spec is weitten badly, it's actually ? feature. Because there's  
actually ? bug that's only discovered when running the spec together.

My 2 cents :)

Eloy

Sent from my iPhone

On 12 okt 2009, at 21:22, Laurent Sansonetti <lsansonetti at apple.com>  
wrote:

> Hi Gp,
>
> Yes there are several environmental issues when running RubySpec.  
> For example I noticed that it will fail if you have a /tmp/xxx  
> directory or if your $HOME is actually a symlink.
>
> On Claudio's server I noticed a few more problems (you can see the  
> failures from the nightly build website, under Tests).
>
> One of my biggest issues with RubySpec is that it executes  
> everything within the same process, so one spec could potentially  
> damage the environment (because of a bug) so that another one might  
> not pass (but executing a spec separately would work).
>
> Laurent
>
> On Oct 12, 2009, at 11:39 AM, Giampiero De Ciantis wrote:
>
>> I have been trying to run the specs and have found some weird  
>> issues with some of the behaviour
>>
>> spec/frozen/core/kernel/spawn_spec.rb - in the "Kernel uses the  
>> current working directory as its working directory" it fails the  
>> test, but if you change the command line to use MacRuby instead of  
>> Ruby, it passes.
>>
>> spec/frozen/library/socket/ipsocket/getaddress_spec.rb - in the  
>> "Socket::IPSocket#getaddress raises an error on unknown hostnames."  
>> The spec fails, but if run the same test on macirb it raises the  
>> appropriate socket error on an unknown host name.
>>
>> Anyone know of environmental issues that might be causing this? I  
>> do 'rake clean' often and still get these errors.
>>
>>
>> I am also getting an error "cat: stdin: Bad file descriptor" on  
>> the /spec/frozen/core/io/close_read_spec.rb spec, but it still  
>> passes.
>>
>> Cheers,
>>
>> -Gp
>>
>>
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

From ruby-noreply at macosforge.org  Tue Oct 13 19:50:26 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 02:50:26 -0000
Subject: [MacRuby-devel] [MacRuby] #356: autoload is not working
In-Reply-To: <041.2ed8362bbd9409d3cbf7e2d7d528015d@macosforge.org>
References: <041.2ed8362bbd9409d3cbf7e2d7d528015d@macosforge.org>
Message-ID: <050.844cbcd86ca7e56d81b0087e4b0d951b@macosforge.org>

#356: autoload is not working
------------------------+---------------------------------------------------
 Reporter:  dev@?       |        Owner:  lsansonetti@?        
     Type:  defect      |       Status:  closed               
 Priority:  major       |    Milestone:  MacRuby 0.5          
Component:  MacRuby     |   Resolution:  fixed                
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Old description:

> {{{
> $ macruby -e 'autoload :YAML, "yaml"; p YAML'
> core:in `const_missing:': uninitialized constant YAML (NameError)
>         from -e:1:in `<main>'
> }}}

New description:

 {{{
 $ macruby -e 'autoload :YAML, "yaml"; p YAML'
 core:in `const_missing:': uninitialized constant YAML (NameError)
         from -e:1:in `<main>'
 }}}

--

Comment:

 Should be working in r2790.

 {{{
 $ macruby -e 'autoload :YAML, "yaml"; p YAML'
 YAML
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/356#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 13 19:55:58 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 02:55:58 -0000
Subject: [MacRuby-devel] [MacRuby] #102: Installation fails.
In-Reply-To: <048.021fdcf1ef494ccaa158de05ec3524a1@macosforge.org>
References: <048.021fdcf1ef494ccaa158de05ec3524a1@macosforge.org>
Message-ID: <057.df98081ba0913116ae4c1cf6d4c22197@macosforge.org>

#102: Installation fails.
-------------------------------+--------------------------------------------
 Reporter:  macruby@?          |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:                     |  
-------------------------------+--------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Please retry with MacRuby 0.5 beta 1, these problems should be fixed. Make
 sure you installed the Xcode developer tools if you want to build from
 source.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/102#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 13 19:57:00 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 02:57:00 -0000
Subject: [MacRuby-devel] [MacRuby] #132: MacRuby 0.3 won't build: the
 rake task returns more errors than I can shake a stick at
In-Reply-To: <056.cf054c7fe5cda51b6b862b45d8481000@macosforge.org>
References: <056.cf054c7fe5cda51b6b862b45d8481000@macosforge.org>
Message-ID: <065.ce2b52e8295132b47a5bb00dc893aafc@macosforge.org>

#132: MacRuby 0.3 won't build: the rake task returns more errors than I can shake
a stick at
---------------------------------------+------------------------------------
 Reporter:  brandon.zylstra@?          |        Owner:  lsansonetti@?        
     Type:  defect                     |       Status:  closed               
 Priority:  blocker                    |    Milestone:  MacRuby 0.5          
Component:  MacRuby                    |   Resolution:  fixed                
 Keywords:  rake build install         |  
---------------------------------------+------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 This problem should be fixed. Please retry with MacRuby 0.5 beta 1.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/132#comment:7>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 13 19:57:34 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 02:57:34 -0000
Subject: [MacRuby-devel] [MacRuby] #136: NSProgressIndicator freezes
	application
In-Reply-To: <051.c5b8db1f9c62c60437c0cfc6842c9b5e@macosforge.org>
References: <051.c5b8db1f9c62c60437c0cfc6842c9b5e@macosforge.org>
Message-ID: <060.be0af789a3ff817b7f1d0296eae767c2@macosforge.org>

#136: NSProgressIndicator freezes application
----------------------------------+-----------------------------------------
 Reporter:  masterkain@?          |        Owner:  lsansonetti@?        
     Type:  defect                |       Status:  closed               
 Priority:  blocker               |    Milestone:  MacRuby 0.5          
Component:  MacRuby               |   Resolution:  fixed                
 Keywords:                        |  
----------------------------------+-----------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Should work with MacRuby 0.5 beta 1. Closing.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/136#comment:4>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 13 19:59:01 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 02:59:01 -0000
Subject: [MacRuby-devel] [MacRuby] #145: PagePacker example locks up on
 exit if file is un-saved
In-Reply-To: <046.761717cd7ab37c8fb5ad24f24af2562d@macosforge.org>
References: <046.761717cd7ab37c8fb5ad24f24af2562d@macosforge.org>
Message-ID: <055.bcbe18264167f3d1f0223a5d487cabc3@macosforge.org>

#145: PagePacker example locks up on exit if file is un-saved
-----------------------------+----------------------------------------------
 Reporter:  niall@?          |        Owner:  lsansonetti@?        
     Type:  defect           |       Status:  closed               
 Priority:  blocker          |    Milestone:  MacRuby 0.5          
Component:  MacRuby          |   Resolution:  fixed                
 Keywords:                   |  
-----------------------------+----------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Closing.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/145#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 13 19:59:39 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 02:59:39 -0000
Subject: [MacRuby-devel] [MacRuby] #187: YAML.load and non-native
	classes.
In-Reply-To: <054.7a0db5df2b355d86d5be078d19d9149a@macosforge.org>
References: <054.7a0db5df2b355d86d5be078d19d9149a@macosforge.org>
Message-ID: <063.a4adf8ebaa19c58fe60dde395f7f9260@macosforge.org>

#187: YAML.load and non-native classes.
-------------------------------------+--------------------------------------
 Reporter:  eloy.de.enige@?          |       Owner:  lsansonetti@?        
     Type:  defect                   |      Status:  new                  
 Priority:  blocker                  |   Milestone:                       
Component:  MacRuby                  |    Keywords:                       
-------------------------------------+--------------------------------------

Comment(by lsansonetti@?):

 Eloy, could you check if the problem exists again? If yes, could you file
 a spec/macruby spec?

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/187#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 13 20:00:48 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 03:00:48 -0000
Subject: [MacRuby-devel] [MacRuby] #240: no such file to load --
 stringio.rb.bundle when starting irb/gems
In-Reply-To: <042.3b242b694944ae4f01068062cede7a44@macosforge.org>
References: <042.3b242b694944ae4f01068062cede7a44@macosforge.org>
Message-ID: <051.cf87cadc0a64c0df2e51765de1316e01@macosforge.org>

#240: no such file to load -- stringio.rb.bundle when starting irb/gems
-------------------------+--------------------------------------------------
 Reporter:  i@?          |        Owner:  lsansonetti@?        
     Type:  defect       |       Status:  closed               
 Priority:  blocker      |    Milestone:  MacRuby 0.5          
Component:  MacRuby      |   Resolution:  fixed                
 Keywords:               |  
-------------------------+--------------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 This problem should be fixed in MacRuby 0.5 beta 1.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/240#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 13 20:01:53 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 03:01:53 -0000
Subject: [MacRuby-devel] [MacRuby] #293: Object.methods in macirb
	returns crazy results
In-Reply-To: <048.cde85f07edeaa5f4f4bd48d215426e78@macosforge.org>
References: <048.cde85f07edeaa5f4f4bd48d215426e78@macosforge.org>
Message-ID: <057.a24957c494d60321229c570c7d645f2d@macosforge.org>

#293: Object.methods in macirb returns crazy results
-------------------------------+--------------------------------------------
 Reporter:  tjw@?              |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:                     |  
-------------------------------+--------------------------------------------
Changes (by lsansonetti@?):

  * status:  reopened => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 The problem should be fixed in trunk since a long time and definitely in
 MacRuby 0.5 beta 1.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/293#comment:4>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 13 20:03:06 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 03:03:06 -0000
Subject: [MacRuby-devel] [MacRuby] #138: macgem not working for me
In-Reply-To: <046.056b1e2d9f6cd81183740a7f12ddbe98@macosforge.org>
References: <046.056b1e2d9f6cd81183740a7f12ddbe98@macosforge.org>
Message-ID: <055.b61b32f996b3da8fb575968d39d976f4@macosforge.org>

#138: macgem not working for me
-----------------------------+----------------------------------------------
 Reporter:  nick@?           |        Owner:  lsansonetti@?        
     Type:  defect           |       Status:  closed               
 Priority:  blocker          |    Milestone:  MacRuby 0.5          
Component:  MacRuby          |   Resolution:  fixed                
 Keywords:                   |  
-----------------------------+----------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Forgot to close the bug.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/138#comment:7>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 13 20:05:20 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 03:05:20 -0000
Subject: [MacRuby-devel] [MacRuby] #276: macgem ends in Abort Trap after
 garbage collection errors
In-Reply-To: <057.e858db5b2b0520f28b5b4c48cfe817e4@macosforge.org>
References: <057.e858db5b2b0520f28b5b4c48cfe817e4@macosforge.org>
Message-ID: <066.502d1855948c89919792d5121511f1ef@macosforge.org>

#276: macgem ends in Abort Trap after garbage collection errors
----------------------------------------+-----------------------------------
 Reporter:  dale.martenson@?            |        Owner:  lsansonetti@?        
     Type:  defect                      |       Status:  closed               
 Priority:  major                       |    Milestone:  MacRuby 0.5          
Component:  MacRuby                     |   Resolution:  fixed                
 Keywords:                              |  
----------------------------------------+-----------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  MacRuby 0.4 => MacRuby 0.5


Comment:

 RubyGems should definitely work better now. Please retry with MacRuby 0.5
 beta 1, thanks!

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/276#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 13 20:07:10 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 03:07:10 -0000
Subject: [MacRuby-devel] [MacRuby] #172: resurrection error
In-Reply-To: <047.9cca286a3baff460c7b628b5949c878f@macosforge.org>
References: <047.9cca286a3baff460c7b628b5949c878f@macosforge.org>
Message-ID: <056.a089516f42307243beb44cf215ad76ca@macosforge.org>

#172: resurrection error
------------------------------+---------------------------------------------
 Reporter:  kbenne@?          |        Owner:  lsansonetti@?        
     Type:  defect            |       Status:  closed               
 Priority:  minor             |    Milestone:  MacRuby 0.5          
Component:  MacRuby           |   Resolution:  fixed                
 Keywords:                    |  
------------------------------+---------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Please retry with MacRuby 0.5 beta 1 and let us know if the problem still
 persists.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/172#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 13 20:08:18 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 03:08:18 -0000
Subject: [MacRuby-devel] [MacRuby] #351: problem with macruby build
	(rake)
In-Reply-To: <056.a01c07af097f798e7ca5af18773c51f6@macosforge.org>
References: <056.a01c07af097f798e7ca5af18773c51f6@macosforge.org>
Message-ID: <065.1ddd36059efac76d8ffcd3cd0bc27422@macosforge.org>

#351: problem with macruby build (rake)
---------------------------------------+------------------------------------
 Reporter:  sergei.homjakov@?          |        Owner:  lsansonetti@?        
     Type:  defect                     |       Status:  closed               
 Priority:  trivial                    |    Milestone:  MacRuby 0.5          
Component:  MacRuby                    |   Resolution:  fixed                
 Keywords:  rake                       |  
---------------------------------------+------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Closing.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/351#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 13 22:14:12 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 05:14:12 -0000
Subject: [MacRuby-devel] [MacRuby] #381: Losing track of a defined
 constant - possibly related to Module.autoload
In-Reply-To: <052.ae2dc3fa4ad8e9ad59e8ff9e3fd9f5ff@macosforge.org>
References: <052.ae2dc3fa4ad8e9ad59e8ff9e3fd9f5ff@macosforge.org>
Message-ID: <061.14ab3ab3aaa361c04f5897d8aef2926e@macosforge.org>

#381: Losing track of a defined constant - possibly related to Module.autoload
----------------------------------------+-----------------------------------
 Reporter:  kamal.fariz@?               |        Owner:  lsansonetti@?        
     Type:  defect                      |       Status:  closed               
 Priority:  minor                       |    Milestone:  MacRuby 0.5          
Component:  MacRuby                     |   Resolution:  fixed                
 Keywords:  autoload require constants  |  
----------------------------------------+-----------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Should be fixed in r2792.

 {{{
 $ macruby -rubygems -rrack -r"rack/builder" -e "Rack::Builder; p 42"
 42
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/381#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 14 00:57:47 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 07:57:47 -0000
Subject: [MacRuby-devel] [MacRuby] #383: segmentation fault with:
 NSDictionary.dictionaryWithObjectsAndKeys
Message-ID: <045.91ab0daa0bdf1b92dc769d32ccd8b90c@macosforge.org>

#383: segmentation fault with: NSDictionary.dictionaryWithObjectsAndKeys
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |       Owner:  lsansonetti@?        
     Type:  defect          |      Status:  new                  
 Priority:  critical        |   Milestone:  MacRuby 0.5          
Component:  MacRuby         |    Keywords:                       
----------------------------+-----------------------------------------------
 {{{
 macruby -e 'p NSDictionary.dictionaryWithObjectsAndKeys("a","b",nil)'
 Segmentation fault
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/383>
MacRuby <http://macruby.org/>


From jazzbox at 7zz.de  Wed Oct 14 01:03:54 2009
From: jazzbox at 7zz.de (B. Ohr)
Date: Wed, 14 Oct 2009 10:03:54 +0200
Subject: [MacRuby-devel] Translating Obj-C to MacRuby
In-Reply-To: <061.14ab3ab3aaa361c04f5897d8aef2926e@macosforge.org>
References: <052.ae2dc3fa4ad8e9ad59e8ff9e3fd9f5ff@macosforge.org>
	<061.14ab3ab3aaa361c04f5897d8aef2926e@macosforge.org>
Message-ID: <3F99D28A-FD17-4F1F-96E8-2FB8145CFB50@7zz.de>

Hi all!

Using Cocoa in MacRuby is sometimes a hard job, because all  
documentation, examples and sample code is Obj-C. For example, I found  
this piece of code '[NSNumber numberWithBool:NO]' and asked myself how  
to write that in Macruby.

I opened macirb and typed:

 > NSNumber.numberWithBool 0
=> false

First I had to laugh and then I thought: Hey implementors of macruby,  
you really did a great job!

What do you think about a table on http://www.macruby.org/ which lists  
all such short (and astonishing) examples. Or even better, why not  
create a command in the services menu which translates a Obj-C  
sequence (by regexp).

BTW, the second example I tried is:

 > NSDictionary.dictionaryWithObjectsAndKeys "a", "b", nil

but instead of {"b"=>"a"} I got a seg fault! (ticket is filed)

Greets,
Bernd






From johnmacshea at gmail.com  Wed Oct 14 01:34:15 2009
From: johnmacshea at gmail.com (John Shea)
Date: Wed, 14 Oct 2009 10:34:15 +0200
Subject: [MacRuby-devel] Translating Obj-C to MacRuby
In-Reply-To: <3F99D28A-FD17-4F1F-96E8-2FB8145CFB50@7zz.de>
References: <052.ae2dc3fa4ad8e9ad59e8ff9e3fd9f5ff@macosforge.org>
	<061.14ab3ab3aaa361c04f5897d8aef2926e@macosforge.org>
	<3F99D28A-FD17-4F1F-96E8-2FB8145CFB50@7zz.de>
Message-ID: <662C4FE8-B6CA-41F0-8554-5511E8441D87@gmail.com>

Hi Bernd,

YES and NO in ObjC are translated to true and false in MacRuby.

so you were probably after:

  NSNumber.numberWithBool(false)

(I am curious as to how often that is useful actually)

I will leave the table idea for others to comment - I actually think  
in the end there are only a few rules to learn and then you will find  
yourself translating easily (not that those rules should not go in a  
cheat sheet somewhere - that's probably a good idea).

With:
NSDictionary.dictionaryWithObjectsAndKeys "a", "b", nil

I assume that in the original ObjC method is actually passing an array  
which (it seems) must be terminated by a nil (in objC).
I actually ran across this in another context - passing objects in  
this way - again I will leave others to comment on it, perhaps it is  
an issue.

However why can't you use :

dict = {"b"=>"a"}
=> {"b"=>"a"}

#check class of created dictionary
dict.class
=> NSMutableDictionary

Why use the long winded ObjC form?

If you need a immutable NSDictionary for some reason:
dict = NSDictionary.alloc.initWithDictionary({"a"=>"b", "c" => "d"})
#or if you like typing
dict = NSDictionary.dictionaryWithObjects(["b","d"], forKeys: 
["a","c"],count:1)

(and many other similar methods, I am sure) works fine.

Cheers,
John


On Oct 14, 2009, at 10:03 , B. Ohr wrote:

> Hi all!
>
> Using Cocoa in MacRuby is sometimes a hard job, because all  
> documentation, examples and sample code is Obj-C. For example, I  
> found this piece of code '[NSNumber numberWithBool:NO]' and asked  
> myself how to write that in Macruby.
>
> I opened macirb and typed:
>
> > NSNumber.numberWithBool 0
> => false
>
> First I had to laugh and then I thought: Hey implementors of  
> macruby, you really did a great job!
>
> What do you think about a table on http://www.macruby.org/ which  
> lists all such short (and astonishing) examples. Or even better, why  
> not create a command in the services menu which translates a Obj-C  
> sequence (by regexp).
>
> BTW, the second example I tried is:
>
> > NSDictionary.dictionaryWithObjectsAndKeys "a", "b", nil
>
> but instead of {"b"=>"a"} I got a seg fault! (ticket is filed)
>
> Greets,
> Bernd
>
>
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091014/4da3763e/attachment-0001.html>

From ruby-noreply at macosforge.org  Wed Oct 14 01:56:00 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 08:56:00 -0000
Subject: [MacRuby-devel] [MacRuby] #383: segmentation fault with:
 NSDictionary.dictionaryWithObjectsAndKeys
In-Reply-To: <045.91ab0daa0bdf1b92dc769d32ccd8b90c@macosforge.org>
References: <045.91ab0daa0bdf1b92dc769d32ccd8b90c@macosforge.org>
Message-ID: <054.c649f66f48c30fb81db5ab3d8fcf1146@macosforge.org>

#383: segmentation fault with: NSDictionary.dictionaryWithObjectsAndKeys
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |        Owner:  lsansonetti@?        
     Type:  defect          |       Status:  closed               
 Priority:  critical        |    Milestone:  MacRuby 0.5          
Component:  MacRuby         |   Resolution:  invalid              
 Keywords:                  |  
----------------------------+-----------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => invalid


Old description:

> {{{
> macruby -e 'p NSDictionary.dictionaryWithObjectsAndKeys("a","b",nil)'
> Segmentation fault
> }}}

New description:

 {{{
 macruby -e 'p NSDictionary.dictionaryWithObjectsAndKeys("a","b",nil)'
 Segmentation fault
 }}}

--

Comment:

 -[NSDictionary dictionaryWithObjectsAndKeys:] is a tricky variadic method
 (it accepts a variable number of arguments). There is no way MacRuby can
 know if a given method is variadic by asking the runtime.

 However, MacRuby can handle these methods if you load the appropriate
 framework metadata first.

 {{{
 $ macruby -e 'framework "Foundation"; p
 NSDictionary.dictionaryWithObjectsAndKeys("a","b",nil)'
 {"b"=>"a"}
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/383#comment:1>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Wed Oct 14 02:04:28 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Wed, 14 Oct 2009 02:04:28 -0700
Subject: [MacRuby-devel] Translating Obj-C to MacRuby
In-Reply-To: <3F99D28A-FD17-4F1F-96E8-2FB8145CFB50@7zz.de>
References: <052.ae2dc3fa4ad8e9ad59e8ff9e3fd9f5ff@macosforge.org>
	<061.14ab3ab3aaa361c04f5897d8aef2926e@macosforge.org>
	<3F99D28A-FD17-4F1F-96E8-2FB8145CFB50@7zz.de>
Message-ID: <88011E79-9E54-45DA-A4B8-107E71E0C836@apple.com>

Hi,

On Oct 14, 2009, at 1:03 AM, B. Ohr wrote:

> Hi all!
>
> Using Cocoa in MacRuby is sometimes a hard job, because all  
> documentation, examples and sample code is Obj-C. For example, I  
> found this piece of code '[NSNumber numberWithBool:NO]' and asked  
> myself how to write that in Macruby.

You can simply pass true or false and MacRuby will do the conversion  
for you.

> I opened macirb and typed:
>
> > NSNumber.numberWithBool 0
> => false
>
> First I had to laugh and then I thought: Hey implementors of  
> macruby, you really did a great job!

And NSNumbers are converted to Ruby types as you just experienced :)

> What do you think about a table on http://www.macruby.org/ which  
> lists all such short (and astonishing) examples. Or even better, why  
> not create a command in the services menu which translates a Obj-C  
> sequence (by regexp).

I think a short tutorial/page on the website would be great, indeed. I  
don't believe it is easily possible to write an Objective-C -> MacRuby  
convertor that works most/all the time (because of the C nature of  
ObjC).

> BTW, the second example I tried is:
>
> > NSDictionary.dictionaryWithObjectsAndKeys "a", "b", nil
>
> but instead of {"b"=>"a"} I got a seg fault! (ticket is filed)

I replied to the ticket, it seems you forgot to do `framework  
'Foundation'' first.

Laurent

From jazzbox at 7zz.de  Wed Oct 14 02:10:19 2009
From: jazzbox at 7zz.de (B. Ohr)
Date: Wed, 14 Oct 2009 11:10:19 +0200
Subject: [MacRuby-devel] Translating Obj-C to MacRuby
In-Reply-To: <662C4FE8-B6CA-41F0-8554-5511E8441D87@gmail.com>
References: <052.ae2dc3fa4ad8e9ad59e8ff9e3fd9f5ff@macosforge.org>
	<061.14ab3ab3aaa361c04f5897d8aef2926e@macosforge.org>
	<3F99D28A-FD17-4F1F-96E8-2FB8145CFB50@7zz.de>
	<662C4FE8-B6CA-41F0-8554-5511E8441D87@gmail.com>
Message-ID: <E148802A-669A-41B1-AB61-2D498433F7FA@7zz.de>

Hi John,

Am 14.10.2009 um 10:34 schrieb John Shea:

> Hi Bernd,
>
> YES and NO in ObjC are translated to true and false in MacRuby.
>
> so you were probably after:
>
>  NSNumber.numberWithBool(false)
>
> (I am curious as to how often that is useful actually)
>
> I will leave the table idea for others to comment - I actually think  
> in the end there are only a few rules to learn and then you will  
> find yourself translating easily (not that those rules should not go  
> in a cheat sheet somewhere - that's probably a good idea).

Shure, there are only few rules, but:

1. there are newbies outside (most of the Obj-C programmers)

2. why should I manually correct those Obj-C things like [aObj: foo] a  
thousand times when it can easily be done by a regexp? I don't want a  
real translator, I am wanting just a simple []-remover!

>
> With:
> NSDictionary.dictionaryWithObjectsAndKeys "a", "b", nil
>
> I assume that in the original ObjC method is actually passing an  
> array which (it seems) must be terminated by a nil (in objC).
> I actually ran across this in another context - passing objects in  
> this way - again I will leave others to comment on it, perhaps it is  
> an issue.
>
> However why can't you use :
>
> dict = {"b"=>"a"}
> => {"b"=>"a"}
>
> #check class of created dictionary
> dict.class
> => NSMutableDictionary
>
> Why use the long winded ObjC form?

Perhaps you misunderstood me. I know this already and I don't want to  
use the long form, I just typed that in macirb to use the RESULT (in  
this case {"b"=>"a"}). Perhaps this is the way a Obj-C programmer is  
trying out MacRuby because of lacking of documentation.

Bernd


From jazzbox at 7zz.de  Wed Oct 14 02:34:59 2009
From: jazzbox at 7zz.de (B. Ohr)
Date: Wed, 14 Oct 2009 11:34:59 +0200
Subject: [MacRuby-devel] Translating Obj-C to MacRuby
In-Reply-To: <88011E79-9E54-45DA-A4B8-107E71E0C836@apple.com>
References: <052.ae2dc3fa4ad8e9ad59e8ff9e3fd9f5ff@macosforge.org>
	<061.14ab3ab3aaa361c04f5897d8aef2926e@macosforge.org>
	<3F99D28A-FD17-4F1F-96E8-2FB8145CFB50@7zz.de>
	<88011E79-9E54-45DA-A4B8-107E71E0C836@apple.com>
Message-ID: <F02C0DCE-09C5-4AB5-B45F-8DCFC3E57FFF@7zz.de>

Hi,

Am 14.10.2009 um 11:04 schrieb Laurent Sansonetti:

> Hi,
>
> On Oct 14, 2009, at 1:03 AM, B. Ohr wrote:
>
>> Hi all!
>>
>> Using Cocoa in MacRuby is sometimes a hard job, because all  
>> documentation, examples and sample code is Obj-C. For example, I  
>> found this piece of code '[NSNumber numberWithBool:NO]' and asked  
>> myself how to write that in Macruby.
>
> You can simply pass true or false and MacRuby will do the conversion  
> for you.

Oh yes, in my example project , I automatically used true and it  
worked. But then I began asking myself, how can I be shure that this  
is the correct way and what would an absolute beginner do and then i  
opened macirb...  ;-)

>
>> I opened macirb and typed:
>>
>> > NSNumber.numberWithBool 0
>> => false
>>
>> First I had to laugh and then I thought: Hey implementors of  
>> macruby, you really did a great job!
>
> And NSNumbers are converted to Ruby types as you just experienced :)

In the docs

+ (NSNumber *)numberWithBool:(BOOL)value

gives a NSNumber and not a TrueClass or FalseClass as in Macruby. I  
only wanted to say how impressed I am!


>
>> What do you think about a table on http://www.macruby.org/ which  
>> lists all such short (and astonishing) examples. Or even better,  
>> why not create a command in the services menu which translates a  
>> Obj-C sequence (by regexp).
>
> I think a short tutorial/page on the website would be great, indeed.  
> I don't believe it is easily possible to write an Objective-C ->  
> MacRuby convertor that works most/all the time (because of the C  
> nature of ObjC).
>

Such a cheat sheet can easily show the beauty of MacRuby and the  
"noisiness" of Obj-C! ;-)

I agree that a real translator is impossible. What I want is a simple  
text processing which removes all the [foo: bar baz] and replaces it  
with foo.bar(baz).


>> BTW, the second example I tried is:
>>
>> > NSDictionary.dictionaryWithObjectsAndKeys "a", "b", nil
>>
>> but instead of {"b"=>"a"} I got a seg fault! (ticket is filed)
>
> I replied to the ticket, it seems you forgot to do `framework  
> 'Foundation'' first.
>

Oh, my fault! But wouldn't it be better NOT to respond with a segment  
fault (this irritated me) and instead throw an normal ruby exception?  
(But perhaps that is impossible.)

Bernd






From ruby-noreply at macosforge.org  Wed Oct 14 05:16:45 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 12:16:45 -0000
Subject: [MacRuby-devel] [MacRuby] #356: autoload is not working
In-Reply-To: <041.2ed8362bbd9409d3cbf7e2d7d528015d@macosforge.org>
References: <041.2ed8362bbd9409d3cbf7e2d7d528015d@macosforge.org>
Message-ID: <050.b1b38db42d6fc7386013c34d79a92e1d@macosforge.org>

#356: autoload is not working
------------------------+---------------------------------------------------
 Reporter:  dev@?       |        Owner:  lsansonetti@?        
     Type:  defect      |       Status:  closed               
 Priority:  major       |    Milestone:  MacRuby 0.5          
Component:  MacRuby     |   Resolution:  fixed                
 Keywords:              |  
------------------------+---------------------------------------------------

Comment(by jazzbox@?):

 Thanks for implementing autoload!

 There is still remaining a problem with modules and classes:

 {{{
 $ cat foo.rb
 module Bar
   class Foo
   end
 end

 $ macruby -e 'module Bar; autoload :Foo, "foo.rb"; class Baz; p Foo; end;
 end'
 core:in `const_missing:': uninitialized constant Bar::Baz::Foo (NameError)
         from -e:1:in `<main>'

 $ ruby -e 'module Bar; autoload :Foo, "foo.rb"; class Baz; p Foo; end;
 end'
 Bar::Foo

 $ ruby1.9 -e 'module Bar; autoload :Foo, "foo.rb"; class Baz; p Foo; end;
 end'
 Bar::Foo

 $ macruby -e 'module Bar; require "foo.rb"; class Baz; p Foo; end; end'
 Bar::Foo
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/356#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 14 05:30:47 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 12:30:47 -0000
Subject: [MacRuby-devel] [MacRuby] #356: autoload is not working
In-Reply-To: <041.2ed8362bbd9409d3cbf7e2d7d528015d@macosforge.org>
References: <041.2ed8362bbd9409d3cbf7e2d7d528015d@macosforge.org>
Message-ID: <050.5937a9e22ddb5ed116c150ce0688485a@macosforge.org>

#356: autoload is not working
------------------------+---------------------------------------------------
 Reporter:  dev@?       |        Owner:  lsansonetti@?        
     Type:  defect      |       Status:  closed               
 Priority:  major       |    Milestone:  MacRuby 0.5          
Component:  MacRuby     |   Resolution:  fixed                
 Keywords:              |  
------------------------+---------------------------------------------------

Comment(by conradwt@?):

 Please file  another ticket because this issue is within the module/class.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/356#comment:3>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 14 05:40:03 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 12:40:03 -0000
Subject: [MacRuby-devel] [MacRuby] #384: autoload is not working within
	module and class
Message-ID: <045.01d4bdcd42ccbde74e3d424c33da19ac@macosforge.org>

#384: autoload is not working within module and class
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |       Owner:  lsansonetti@?        
     Type:  defect          |      Status:  new                  
 Priority:  critical        |   Milestone:  MacRuby 0.5          
Component:  MacRuby         |    Keywords:                       
----------------------------+-----------------------------------------------
 {{{
 $ cat foo.rb
 module Bar
   class Foo
   end
 end

 $ macruby -e 'module Bar; autoload :Foo, "foo.rb"; class Baz; p Foo; end;
 end'
 core:in `const_missing:': uninitialized constant Bar::Baz::Foo (NameError)
         from -e:1:in `<main>'

 $ ruby -e 'module Bar; autoload :Foo, "foo.rb"; class Baz; p Foo; end;
 end'
 Bar::Foo

 $ ruby1.9 -e 'module Bar; autoload :Foo, "foo.rb"; class Baz; p Foo; end;
 end'
 Bar::Foo

 $ macruby -e 'module Bar; require "foo.rb"; class Baz; p Foo; end; end'
 Bar::Foo
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/384>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 14 06:37:38 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 13:37:38 -0000
Subject: [MacRuby-devel] [MacRuby] #385: Cannot distribute macruby apps
Message-ID: <056.2dfff30c57e596c435e982e9f263c6b9@macosforge.org>

#385: Cannot distribute macruby apps
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?                
     Type:  defect                     |      Status:  new                          
 Priority:  blocker                    |   Milestone:  MacRuby 0.5                  
Component:  MacRuby                    |    Keywords:  macruby, distribute, rubygems
---------------------------------------+------------------------------------
 Was trying to send a demo app to various people for testing and built
 using the Embed Macruby target as well as customizing my rb_main.rb file
 with.

 {{{
 $:.map! {|x| x.sub(/^\/Library\/Frameworks/,
 NSBundle.mainBundle.privateFrameworksPath)}
 $:.unshift NSBundle.mainBundle.resourcePath.fileSystemRepresentation
 }}}

 Users reported crashes with output logs:
 10/13/09 7:27:51 PM     [0x0-0x14da4d9].com.yourcompany.GemManage[79689]
 /Users/joshaber/Downloads/TheSafe-1.app/Contents/Resources/rb_main.rb:2:in
 `<main>':
 dlopen(/Users/joshaber/Downloads/TheSafe-1.app/Contents/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/1.9.0/rubygems.rbo,
 9): Library not loaded:
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/libmacruby.dylib
 10/13/09 7:27:51 PM     [0x0-0x14da4d9].com.yourcompany.GemManage[79689]
 Referenced from:
 /Users/joshaber/Downloads/TheSafe-1.app/Contents/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/1.9.0/rubygems.rbo
 10/13/09 7:27:51 PM     [0x0-0x14da4d9].com.yourcompany.GemManage[79689]
 Reason: image not found -
 /Users/joshaber/Downloads/TheSafe-1.app/Contents/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/1.9.0/rubygems.rbo
 (LoadError)
 10/13/09 7:27:51 PM     com.apple.launchd.peruser.501[85]
 ([0x0-0x14da4d9].com.yourcompany.GemManage[79689]) Exited with exit code:
 1

 Should I not be using that custom load line in the rb_main.rb file?

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/385>
MacRuby <http://macruby.org/>


From keenan at thebrocks.net  Wed Oct 14 09:15:44 2009
From: keenan at thebrocks.net (Keenan Brock)
Date: Wed, 14 Oct 2009 12:15:44 -0400
Subject: [MacRuby-devel] Translating Obj-C to MacRuby (B. Ohr)
Message-ID: <F0BD2C2B-69C1-41F8-98EB-C67B877AAB67@thebrocks.net>

I was always amused by ASTranslate.

I think they actually take the events sent and use those to generate  
code.


http://appscript.sourceforge.net/tools.html


--Keenan

From ruby-noreply at macosforge.org  Wed Oct 14 12:04:32 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 19:04:32 -0000
Subject: [MacRuby-devel] [MacRuby] #385: Cannot distribute macruby apps
In-Reply-To: <056.2dfff30c57e596c435e982e9f263c6b9@macosforge.org>
References: <056.2dfff30c57e596c435e982e9f263c6b9@macosforge.org>
Message-ID: <065.bc72eeb32d5c58e60e552f415616b306@macosforge.org>

#385: Cannot distribute macruby apps
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?                
     Type:  defect                     |      Status:  new                          
 Priority:  blocker                    |   Milestone:  MacRuby 0.5                  
Component:  MacRuby                    |    Keywords:  macruby, distribute, rubygems
---------------------------------------+------------------------------------

Comment(by lsansonetti@?):

 Looks like we forgot to change the install name of the .rbo files.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/385#comment:1>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Wed Oct 14 12:26:21 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Wed, 14 Oct 2009 12:26:21 -0700
Subject: [MacRuby-devel] Translating Obj-C to MacRuby
In-Reply-To: <F02C0DCE-09C5-4AB5-B45F-8DCFC3E57FFF@7zz.de>
References: <052.ae2dc3fa4ad8e9ad59e8ff9e3fd9f5ff@macosforge.org>
	<061.14ab3ab3aaa361c04f5897d8aef2926e@macosforge.org>
	<3F99D28A-FD17-4F1F-96E8-2FB8145CFB50@7zz.de>
	<88011E79-9E54-45DA-A4B8-107E71E0C836@apple.com>
	<F02C0DCE-09C5-4AB5-B45F-8DCFC3E57FFF@7zz.de>
Message-ID: <999EADC3-4503-4DA9-85C4-9DD71B76FAE8@apple.com>

Hi,

On Oct 14, 2009, at 2:34 AM, B. Ohr wrote:

> Hi,
>
> Am 14.10.2009 um 11:04 schrieb Laurent Sansonetti:
>
>> Hi,
>>
>> On Oct 14, 2009, at 1:03 AM, B. Ohr wrote:
>>
>>> Hi all!
>>>
>>> Using Cocoa in MacRuby is sometimes a hard job, because all  
>>> documentation, examples and sample code is Obj-C. For example, I  
>>> found this piece of code '[NSNumber numberWithBool:NO]' and asked  
>>> myself how to write that in Macruby.
>>
>> You can simply pass true or false and MacRuby will do the  
>> conversion for you.
>
> Oh yes, in my example project , I automatically used true and it  
> worked. But then I began asking myself, how can I be shure that this  
> is the correct way and what would an absolute beginner do and then i  
> opened macirb...  ;-)
>
>>
>>> I opened macirb and typed:
>>>
>>> > NSNumber.numberWithBool 0
>>> => false
>>>
>>> First I had to laugh and then I thought: Hey implementors of  
>>> macruby, you really did a great job!
>>
>> And NSNumbers are converted to Ruby types as you just experienced :)
>
> In the docs
>
> + (NSNumber *)numberWithBool:(BOOL)value
>
> gives a NSNumber and not a TrueClass or FalseClass as in Macruby. I  
> only wanted to say how impressed I am!

Hehe, thank you :)

>>> What do you think about a table on http://www.macruby.org/ which  
>>> lists all such short (and astonishing) examples. Or even better,  
>>> why not create a command in the services menu which translates a  
>>> Obj-C sequence (by regexp).
>>
>> I think a short tutorial/page on the website would be great,  
>> indeed. I don't believe it is easily possible to write an Objective- 
>> C -> MacRuby convertor that works most/all the time (because of the  
>> C nature of ObjC).
>>
>
> Such a cheat sheet can easily show the beauty of MacRuby and the  
> "noisiness" of Obj-C! ;-)

If you or anyone are willing to work on this, feel free and we can  
integrate it later on the website.

> I agree that a real translator is impossible. What I want is a  
> simple text processing which removes all the [foo: bar baz] and  
> replaces it with foo.bar(baz).

I see. That should be easy then :)

>>> BTW, the second example I tried is:
>>>
>>> > NSDictionary.dictionaryWithObjectsAndKeys "a", "b", nil
>>>
>>> but instead of {"b"=>"a"} I got a seg fault! (ticket is filed)
>>
>> I replied to the ticket, it seems you forgot to do `framework  
>> 'Foundation'' first.
>>
>
> Oh, my fault! But wouldn't it be better NOT to respond with a  
> segment fault (this irritated me) and instead throw an normal ruby  
> exception? (But perhaps that is impossible.)

It's unfortunately not possible, we crash when calling the method  
because we don't use the right ABI conventions (since the method is  
variadic) and there is no way we can determine that at runtime.

This is why we need to load the framework metadata (BridgeSupport  
file) in order to handle these methods.

Laurent

From ruby-noreply at macosforge.org  Wed Oct 14 13:14:12 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 14 Oct 2009 20:14:12 -0000
Subject: [MacRuby-devel] [MacRuby] #384: autoload is not working within
	module and class
In-Reply-To: <045.01d4bdcd42ccbde74e3d424c33da19ac@macosforge.org>
References: <045.01d4bdcd42ccbde74e3d424c33da19ac@macosforge.org>
Message-ID: <054.5115e3c76464dcdd2b0d0dc7d4880454@macosforge.org>

#384: autoload is not working within module and class
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |        Owner:  lsansonetti@?        
     Type:  defect          |       Status:  closed               
 Priority:  critical        |    Milestone:  MacRuby 0.5          
Component:  MacRuby         |   Resolution:  fixed                
 Keywords:                  |  
----------------------------+-----------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Thanks for the report, it should be fixed in r2795.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/384#comment:1>
MacRuby <http://macruby.org/>


From macruby at ianragsdale.com  Wed Oct 14 13:28:06 2009
From: macruby at ianragsdale.com (macruby at ianragsdale.com)
Date: Wed, 14 Oct 2009 13:28:06 -0700 (PDT)
Subject: [MacRuby-devel] Translating Obj-C to MacRuby
Message-ID: <20091014202806.93E2215242C0@lists.macosforge.org>

An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091014/7a66f712/attachment.html>

From cwilliams at allancraig.net  Wed Oct 14 19:07:43 2009
From: cwilliams at allancraig.net (Craig Williams)
Date: Wed, 14 Oct 2009 20:07:43 -0600
Subject: [MacRuby-devel] Using Gems in MacRuby
Message-ID: <0BD9119F-541B-40C7-9DFD-6177B45794AB@allancraig.net>

Hi Everyone,

I have searched the web but have not found a good explanation on how  
to use
gems in a MacRuby project. Is there a tutorial I am missing?

Thanks,

Craig

From conradwt at gmail.com  Wed Oct 14 19:44:40 2009
From: conradwt at gmail.com (Conrad Taylor)
Date: Wed, 14 Oct 2009 19:44:40 -0700
Subject: [MacRuby-devel] Using Gems in MacRuby
In-Reply-To: <0BD9119F-541B-40C7-9DFD-6177B45794AB@allancraig.net>
References: <0BD9119F-541B-40C7-9DFD-6177B45794AB@allancraig.net>
Message-ID: <7317d7610910141944w36c3427aiad00bb2d959ff70d@mail.gmail.com>

Hi, could someone tell me the state of the iconv coding?

Thanks,

-Conrad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091014/8668acac/attachment.html>

From conradwt at gmail.com  Wed Oct 14 19:45:56 2009
From: conradwt at gmail.com (Conrad Taylor)
Date: Wed, 14 Oct 2009 19:45:56 -0700
Subject: [MacRuby-devel]  iconv coding status
Message-ID: <7317d7610910141945r5a8a54f4jfdc3750e8456425a@mail.gmail.com>

Hi, could someone tell me the state of the iconv coding?

Thanks,

-Conrad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091014/f0214fe4/attachment.html>

From ruby-noreply at macosforge.org  Thu Oct 15 05:38:02 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 15 Oct 2009 12:38:02 -0000
Subject: [MacRuby-devel] [MacRuby] #386: binding with block does not work
Message-ID: <045.e43cce02bfae563359f5ff08330af9a1@macosforge.org>

#386: binding with block does not work
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |       Owner:  lsansonetti@?        
     Type:  defect          |      Status:  new                  
 Priority:  critical        |   Milestone:  MacRuby 0.5          
Component:  MacRuby         |    Keywords:                       
----------------------------+-----------------------------------------------
 {{{
 $ cat y.rb
 class Foo
   def get_binding
     binding
   end
 end

 b = Foo.new.get_binding { "got it"}

 p eval "block_given?", b
 p eval "yield", b
 }}}

 {{{
 $ macruby y.rb
 false
 (eval):in `<main>': no block given (LocalJumpError)
         from core:in `eval:'
         from y.rb:in `<main>'
 }}}

 {{{
 $ ruby y.rb
 true
 "got it"
 }}}

 I added a failing test for test_vm/eval.rb

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/386>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 15 08:23:30 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 15 Oct 2009 15:23:30 -0000
Subject: [MacRuby-devel] [MacRuby] #387: inspect with circular references
	crashes
Message-ID: <045.4692823c1a086c5206c6882468d82d99@macosforge.org>

#387: inspect with circular references crashes
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |       Owner:  lsansonetti@?        
     Type:  defect          |      Status:  new                  
 Priority:  major           |   Milestone:  MacRuby 0.5          
Component:  MacRuby         |    Keywords:                       
----------------------------+-----------------------------------------------
 {{{
 $ cat insp.rb

 class Foo
   def initialize bar
     @bar = bar
   end
 end

 class Bar
   def initialize
     @foo = Foo.new(self)
     #@bar = self  # this crashes too
   end
 end

 puts Bar.new.inspect
 }}}

 {{{
 $ macruby insp.rb
 Segmentation fault
 }}}


 {{{
 $ ruby insp.rb
 #<Bar:0x1001561d8 @foo=#<Foo:0x100156110 @bar=#<Bar:0x1001561d8 ...>>>
 }}}


 (BTW, this was a very hard one to find for me: Foreign code, multiple
 nested modules and many, many instance variables. First I thought it has
 to too witch complexity until I had the idea with the circular
 reference...)

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/387>
MacRuby <http://macruby.org/>


From jazzbox at 7zz.de  Thu Oct 15 09:33:33 2009
From: jazzbox at 7zz.de (B. Ohr)
Date: Thu, 15 Oct 2009 18:33:33 +0200
Subject: [MacRuby-devel] Running nanoc3 with MacRuby
In-Reply-To: <7317d7610910141945r5a8a54f4jfdc3750e8456425a@mail.gmail.com>
References: <7317d7610910141945r5a8a54f4jfdc3750e8456425a@mail.gmail.com>
Message-ID: <48996A19-FC5E-4455-A76B-C5ED6BAC761B@7zz.de>

Hi,

I got nanoc3 working with MacRuby (http://nanoc.stoneship.org/). It?s  
a static site generator like webby (I think it is more powerful).

I haven't done much yet, just the basic things like create a site  
skeleton, replace a 'yield' in a layout page (does not work yet,  
ticket #386), and do some filtering with ERB.

Finally i wrote a MacRuby function, where I am parsing calendar events  
of my iCal (framework 'CalendarStore') to bring them on the website.  
This is the reason why I am running nanoc with MacRuby, because of the  
direct access to the Cocoa frameworks. It is working fine!

Next I will try to run other filters like Redcloth and Ultraviolet,  
and things like image- and pdf-processing (with the Cocoa framework) I  
will give a chance too.

Ah, there is one question remaining:

nanoc3 uses PStore, which is calling File#flock, which gives an  
unimplemented error in MacRuby. Does anybody know the state of  
File#flock?

Bernd

From ruby-noreply at macosforge.org  Thu Oct 15 10:04:17 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 15 Oct 2009 17:04:17 -0000
Subject: [MacRuby-devel] [MacRuby] #388: Exception with next...
Message-ID: <049.fd88d54f64aece1c6ed5eccd680a86d0@macosforge.org>

#388: Exception with next...
--------------------------------+-------------------------------------------
 Reporter:  rich@?              |       Owner:  lsansonetti@?        
     Type:  defect              |      Status:  new                  
 Priority:  minor               |   Milestone:                       
Component:  MacRuby             |    Keywords:                       
--------------------------------+-------------------------------------------
 This may be a place where we just break with compatibility but if you do:

 macruby -e 'def foo; next; end; puts "hello"'
 unexpected next (LocalJumpError)

 ruby -e 'def foo; next; end; puts "hello"'
 hello

 Since in Ruby that method is never called, the LocalJumpError will never
 surface.  Again, this may be something that is offered as a 'feature'...I
 dunno

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/388>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 15 11:37:17 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 15 Oct 2009 18:37:17 -0000
Subject: [MacRuby-devel] [MacRuby] #388: Exception with next...
In-Reply-To: <049.fd88d54f64aece1c6ed5eccd680a86d0@macosforge.org>
References: <049.fd88d54f64aece1c6ed5eccd680a86d0@macosforge.org>
Message-ID: <058.acb5babc34bed3055458a5398d2dc6f1@macosforge.org>

#388: Exception with next...
--------------------------------+-------------------------------------------
 Reporter:  rich@?              |        Owner:  lsansonetti@?        
     Type:  defect              |       Status:  closed               
 Priority:  minor               |    Milestone:                       
Component:  MacRuby             |   Resolution:  invalid              
 Keywords:                      |  
--------------------------------+-------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => invalid


Comment:

 This is an expected 1.9 behavior.

 {{{
 $ ruby19 -e 'def foo; next; end; puts "hello"'
 -e:1: Invalid next
 -e: compile error (SyntaxError)
 }}}

 I note that we should probably use a SyntaxError as 1.9 does.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/388#comment:1>
MacRuby <http://macruby.org/>


From tmcdowell at gmail.com  Thu Oct 15 12:18:36 2009
From: tmcdowell at gmail.com (Timothy McDowell)
Date: Thu, 15 Oct 2009 13:18:36 -0600
Subject: [MacRuby-devel] MacRuby MUD server... anyone up for it?
Message-ID: <88e4f940910151218r635fadd6mb83d41896eccb3e2@mail.gmail.com>

Hey, I'm fairly new to Objective-C, and totally new to MacRuby. However, I
do know Ruby. :)
I was wondering if anyone would be interested in helping out with a project
to make a MUDlib or MUD server with MacRuby. All the networking, etc. would
be done one the objc side, while all the logic and item/weapon/room/player
programming would be done in Ruby. Who's up for it?

-- 
--Timothy.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091015/7dde3565/attachment.html>

From lsansonetti at apple.com  Thu Oct 15 13:38:51 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 15 Oct 2009 13:38:51 -0700
Subject: [MacRuby-devel] Running nanoc3 with MacRuby
In-Reply-To: <48996A19-FC5E-4455-A76B-C5ED6BAC761B@7zz.de>
References: <7317d7610910141945r5a8a54f4jfdc3750e8456425a@mail.gmail.com>
	<48996A19-FC5E-4455-A76B-C5ED6BAC761B@7zz.de>
Message-ID: <B7460341-4411-4C7A-B35A-DE0C60E3A765@apple.com>

Hi,

On Oct 15, 2009, at 9:33 AM, B. Ohr wrote:

> Hi,
>
> I got nanoc3 working with MacRuby (http://nanoc.stoneship.org/).  
> It?s a static site generator like webby (I think it is more powerful).
>
> I haven't done much yet, just the basic things like create a site  
> skeleton, replace a 'yield' in a layout page (does not work yet,  
> ticket #386), and do some filtering with ERB.
>
> Finally i wrote a MacRuby function, where I am parsing calendar  
> events of my iCal (framework 'CalendarStore') to bring them on the  
> website. This is the reason why I am running nanoc with MacRuby,  
> because of the direct access to the Cocoa frameworks. It is working  
> fine!
>
> Next I will try to run other filters like Redcloth and Ultraviolet,  
> and things like image- and pdf-processing (with the Cocoa framework)  
> I will give a chance too.

That sounds awesome! I think it would be very cool if you could  
describe your experience on the website (maybe as a blog article or  
short tutorial).

> Ah, there is one question remaining:
>
> nanoc3 uses PStore, which is calling File#flock, which gives an  
> unimplemented error in MacRuby. Does anybody know the state of  
> File#flock?

Please file a ticket on Trac, I will try to get it implemented for the  
next beta.

Laurent

From lsansonetti at apple.com  Thu Oct 15 13:41:35 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 15 Oct 2009 13:41:35 -0700
Subject: [MacRuby-devel] iconv coding status
In-Reply-To: <7317d7610910141945r5a8a54f4jfdc3750e8456425a@mail.gmail.com>
References: <7317d7610910141945r5a8a54f4jfdc3750e8456425a@mail.gmail.com>
Message-ID: <1108680B-9C6E-40C3-AAC9-3CC32A5EB0C7@apple.com>

Hi Conrad,

On Oct 14, 2009, at 7:45 PM, Conrad Taylor wrote:

> Hi, could someone tell me the state of the iconv coding?

It's not implemented yet and won't probably be there in 0.5. Note that  
you can do encoding, unicode and ICU transformations on MacRuby  
strings out of the box, using the CFStringRef and NSString APIs.

Laurent

From lsansonetti at apple.com  Thu Oct 15 13:43:29 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 15 Oct 2009 13:43:29 -0700
Subject: [MacRuby-devel] Using Gems in MacRuby
In-Reply-To: <0BD9119F-541B-40C7-9DFD-6177B45794AB@allancraig.net>
References: <0BD9119F-541B-40C7-9DFD-6177B45794AB@allancraig.net>
Message-ID: <688131F8-17D5-4012-B73B-601A41A31122@apple.com>

Hi Craig,

On Oct 14, 2009, at 7:07 PM, Craig Williams wrote:

> Hi Everyone,
>
> I have searched the web but have not found a good explanation on how  
> to use
> gems in a MacRuby project. Is there a tutorial I am missing?

We should definitely write a tutorial about that. The RubyGems support  
is pretty new so I don't think anybody tried yet to embed gems in a  
MacRuby app. At a glance I believe it would be a matter of installing  
the gem inside MacRuby.framework, embed it in the app then change the  
GEM_HOME environment variable.

Laurent

From ruby-noreply at macosforge.org  Thu Oct 15 13:48:18 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 15 Oct 2009 20:48:18 -0000
Subject: [MacRuby-devel] [MacRuby] #387: inspect with circular
	references crashes
In-Reply-To: <045.4692823c1a086c5206c6882468d82d99@macosforge.org>
References: <045.4692823c1a086c5206c6882468d82d99@macosforge.org>
Message-ID: <054.01227c9d2af71b523b20730d5ac2578a@macosforge.org>

#387: inspect with circular references crashes
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |       Owner:  lsansonetti@?        
     Type:  defect          |      Status:  new                  
 Priority:  major           |   Milestone:  MacRuby 0.5          
Component:  MacRuby         |    Keywords:                       
----------------------------+-----------------------------------------------

Comment(by lsansonetti@?):

 Shorter reduction:

 {{{
 $ ./miniruby -e "class C; def initialize; @foo=self; end; end; p C.new"
 Segmentation fault
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/387#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 15 14:14:40 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 15 Oct 2009 21:14:40 -0000
Subject: [MacRuby-devel] [MacRuby] #387: inspect with circular
	references crashes
In-Reply-To: <045.4692823c1a086c5206c6882468d82d99@macosforge.org>
References: <045.4692823c1a086c5206c6882468d82d99@macosforge.org>
Message-ID: <054.b4ad45360b4942633ff4ef7694794187@macosforge.org>

#387: inspect with circular references crashes
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |        Owner:  lsansonetti@?        
     Type:  defect          |       Status:  closed               
 Priority:  major           |    Milestone:  MacRuby 0.5          
Component:  MacRuby         |   Resolution:  fixed                
 Keywords:                  |  
----------------------------+-----------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Should be fixed in r2814.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/387#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 15 16:51:58 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 15 Oct 2009 23:51:58 -0000
Subject: [MacRuby-devel] [MacRuby] #386: binding with block does not work
In-Reply-To: <045.e43cce02bfae563359f5ff08330af9a1@macosforge.org>
References: <045.e43cce02bfae563359f5ff08330af9a1@macosforge.org>
Message-ID: <054.4f05ee78fc8286d2f63520c4bed70324@macosforge.org>

#386: binding with block does not work
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |        Owner:  lsansonetti@?        
     Type:  defect          |       Status:  closed               
 Priority:  critical        |    Milestone:  MacRuby 0.5          
Component:  MacRuby         |   Resolution:  fixed                
 Keywords:                  |  
----------------------------+-----------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Thanks for the test case, I merged it and fixed the problem in r2819.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/386#comment:1>
MacRuby <http://macruby.org/>


From cwdinfo at gmail.com  Thu Oct 15 17:03:45 2009
From: cwdinfo at gmail.com (s.ross)
Date: Thu, 15 Oct 2009 17:03:45 -0700
Subject: [MacRuby-devel] Using Gems in MacRuby
In-Reply-To: <688131F8-17D5-4012-B73B-601A41A31122@apple.com>
References: <0BD9119F-541B-40C7-9DFD-6177B45794AB@allancraig.net>
	<688131F8-17D5-4012-B73B-601A41A31122@apple.com>
Message-ID: <F6F58795-2E02-47A4-A9ED-8349FF71A656@gmail.com>


On Oct 15, 2009, at 1:43 PM, Laurent Sansonetti wrote:

> Hi Craig,
>
> On Oct 14, 2009, at 7:07 PM, Craig Williams wrote:
>
>> Hi Everyone,
>>
>> I have searched the web but have not found a good explanation on  
>> how to use
>> gems in a MacRuby project. Is there a tutorial I am missing?
>
> We should definitely write a tutorial about that. The RubyGems  
> support is pretty new so I don't think anybody tried yet to embed  
> gems in a MacRuby app. At a glance I believe it would be a matter of  
> installing the gem inside MacRuby.framework, embed it in the app  
> then change the GEM_HOME environment variable.
>
> Laurent

Oof. Changing the framework? Maybe I'm not understanding what you're  
suggesting. Why would it not be enough to install all gems in a  
vendor/ directory and change GEM_HOME to there? Or something that  
would not involve embedding (eventually) all gems in use in all apps  
you're developing inside the MacRuby.framework...

Steve

From ruby-noreply at macosforge.org  Thu Oct 15 18:02:19 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 16 Oct 2009 01:02:19 -0000
Subject: [MacRuby-devel] [MacRuby] #376: The second 'pointer' of a
 double pointer type is ignored
In-Reply-To: <050.e457ce96cd16850e431e499f112c297c@macosforge.org>
References: <050.e457ce96cd16850e431e499f112c297c@macosforge.org>
Message-ID: <059.9ea2f2b23f93bf757d82831745d5bcdf@macosforge.org>

#376: The second 'pointer' of a double pointer type is ignored
---------------------------------+------------------------------------------
 Reporter:  mred@?               |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------

Comment(by lsansonetti@?):

 Could you attach your MusicPlayer.bridgesupport file? I'm curous how
 ^{OpaqueMusicPlayer} is annotated.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/376#comment:2>
MacRuby <http://macruby.org/>


From conradwt at gmail.com  Thu Oct 15 18:10:43 2009
From: conradwt at gmail.com (Conrad Taylor)
Date: Thu, 15 Oct 2009 18:10:43 -0700
Subject: [MacRuby-devel] Using Gems in MacRuby
In-Reply-To: <F6F58795-2E02-47A4-A9ED-8349FF71A656@gmail.com>
References: <0BD9119F-541B-40C7-9DFD-6177B45794AB@allancraig.net>
	<688131F8-17D5-4012-B73B-601A41A31122@apple.com>
	<F6F58795-2E02-47A4-A9ED-8349FF71A656@gmail.com>
Message-ID: <7317d7610910151810s6eb6a9c9jcad5ab0ea3cfd892@mail.gmail.com>

On Thu, Oct 15, 2009 at 5:03 PM, s.ross <cwdinfo at gmail.com> wrote:

>
> On Oct 15, 2009, at 1:43 PM, Laurent Sansonetti wrote:
>
>  Hi Craig,
>>
>> On Oct 14, 2009, at 7:07 PM, Craig Williams wrote:
>>
>>  Hi Everyone,
>>>
>>> I have searched the web but have not found a good explanation on how to
>>> use
>>> gems in a MacRuby project. Is there a tutorial I am missing?
>>>
>>
>> We should definitely write a tutorial about that. The RubyGems support is
>> pretty new so I don't think anybody tried yet to embed gems in a MacRuby
>> app. At a glance I believe it would be a matter of installing the gem inside
>> MacRuby.framework, embed it in the app then change the GEM_HOME environment
>> variable.
>>
>> Laurent
>>
>
> Oof. Changing the framework? Maybe I'm not understanding what you're
> suggesting. Why would it not be enough to install all gems in a vendor/
> directory and change GEM_HOME to there? Or something that would not involve
> embedding (eventually) all gems in use in all apps you're developing inside
> the MacRuby.framework...
>
> Steve
>
>
Steve, you should be able to install the gem(s) and require them in the
relevant file(s).  You shouldn't have to unpack the gem(s) into a vendor
directory because they should be visible to the Ruby environment after you
require it.

-Conrad


> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091015/75dd6c83/attachment.html>

From cwdinfo at gmail.com  Thu Oct 15 19:55:48 2009
From: cwdinfo at gmail.com (s.ross)
Date: Thu, 15 Oct 2009 19:55:48 -0700
Subject: [MacRuby-devel] Using Gems in MacRuby
In-Reply-To: <7317d7610910151810s6eb6a9c9jcad5ab0ea3cfd892@mail.gmail.com>
References: <0BD9119F-541B-40C7-9DFD-6177B45794AB@allancraig.net>
	<688131F8-17D5-4012-B73B-601A41A31122@apple.com>
	<F6F58795-2E02-47A4-A9ED-8349FF71A656@gmail.com>
	<7317d7610910151810s6eb6a9c9jcad5ab0ea3cfd892@mail.gmail.com>
Message-ID: <99E63DFC-0F30-45BD-865A-44313B65A521@gmail.com>

On Oct 15, 2009, at 6:10 PM, Conrad Taylor wrote:

> On Thu, Oct 15, 2009 at 5:03 PM, s.ross <cwdinfo at gmail.com> wrote:
>
> On Oct 15, 2009, at 1:43 PM, Laurent Sansonetti wrote:
>
> Hi Craig,
>
> On Oct 14, 2009, at 7:07 PM, Craig Williams wrote:
>
> Hi Everyone,
>
> I have searched the web but have not found a good explanation on how  
> to use
> gems in a MacRuby project. Is there a tutorial I am missing?
>
> We should definitely write a tutorial about that. The RubyGems  
> support is pretty new so I don't think anybody tried yet to embed  
> gems in a MacRuby app. At a glance I believe it would be a matter of  
> installing the gem inside MacRuby.framework, embed it in the app  
> then change the GEM_HOME environment variable.
>
> Laurent
>
> Oof. Changing the framework? Maybe I'm not understanding what you're  
> suggesting. Why would it not be enough to install all gems in a  
> vendor/ directory and change GEM_HOME to there? Or something that  
> would not involve embedding (eventually) all gems in use in all apps  
> you're developing inside the MacRuby.framework...
>
> Steve
>
>
> Steve, you should be able to install the gem(s) and require them in  
> the relevant file(s).  You shouldn't have to unpack the gem(s) into  
> a vendor directory because they should be visible to the Ruby  
> environment after you require it.
>
> -Conrad

Conrad--

I guess I'm thinking of a case where you didn't want to rely on a  
particular gem being present on a target machine -- say for an app you  
were distributing. Naturally, the GEM_HOME built into MacRuby is just  
fine on *my* machine. But, if I give the app to someone else who may  
not have a particular gem installed, boom!

Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091015/3f0dae9b/attachment.html>

From cwilliams at allancraig.net  Thu Oct 15 20:15:07 2009
From: cwilliams at allancraig.net (Craig Williams)
Date: Thu, 15 Oct 2009 21:15:07 -0600
Subject: [MacRuby-devel] Using Gems in MacRuby
In-Reply-To: <99E63DFC-0F30-45BD-865A-44313B65A521@gmail.com>
References: <0BD9119F-541B-40C7-9DFD-6177B45794AB@allancraig.net>
	<688131F8-17D5-4012-B73B-601A41A31122@apple.com>
	<F6F58795-2E02-47A4-A9ED-8349FF71A656@gmail.com>
	<7317d7610910151810s6eb6a9c9jcad5ab0ea3cfd892@mail.gmail.com>
	<99E63DFC-0F30-45BD-865A-44313B65A521@gmail.com>
Message-ID: <1E174F8E-8624-4DE3-84B3-C2C65661861D@allancraig.net>


On Oct 15, 2009, at 8:55 PM, s.ross wrote:

> On Oct 15, 2009, at 6:10 PM, Conrad Taylor wrote:
>
>> On Thu, Oct 15, 2009 at 5:03 PM, s.ross <cwdinfo at gmail.com> wrote:
>>
>> On Oct 15, 2009, at 1:43 PM, Laurent Sansonetti wrote:
>>
>> Hi Craig,
>>
>> On Oct 14, 2009, at 7:07 PM, Craig Williams wrote:
>>
>> Hi Everyone,
>>
>> I have searched the web but have not found a good explanation on  
>> how to use
>> gems in a MacRuby project. Is there a tutorial I am missing?
>>
>> We should definitely write a tutorial about that. The RubyGems  
>> support is pretty new so I don't think anybody tried yet to embed  
>> gems in a MacRuby app. At a glance I believe it would be a matter  
>> of installing the gem inside MacRuby.framework, embed it in the app  
>> then change the GEM_HOME environment variable.
>>
>> Laurent
>>
>> Oof. Changing the framework? Maybe I'm not understanding what  
>> you're suggesting. Why would it not be enough to install all gems  
>> in a vendor/ directory and change GEM_HOME to there? Or something  
>> that would not involve embedding (eventually) all gems in use in  
>> all apps you're developing inside the MacRuby.framework...
>>
>> Steve
>>
>>
>> Steve, you should be able to install the gem(s) and require them in  
>> the relevant file(s).  You shouldn't have to unpack the gem(s) into  
>> a vendor directory because they should be visible to the Ruby  
>> environment after you require it.
>>
>> -Conrad
>
> Conrad--
>
> I guess I'm thinking of a case where you didn't want to rely on a  
> particular gem being present on a target machine -- say for an app  
> you were distributing. Naturally, the GEM_HOME built into MacRuby is  
> just fine on *my* machine. But, if I give the app to someone else  
> who may not have a particular gem installed, boom!
>
> Steve


Any examples on how to do this? I get an error that it failed to load  
~/.gemrc during build.

Craig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091015/c713a4ea/attachment-0001.html>

From ruby-noreply at macosforge.org  Thu Oct 15 21:19:23 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 16 Oct 2009 04:19:23 -0000
Subject: [MacRuby-devel] [MacRuby] #359: Project Templates Not Installed
 By Nightly Installer
In-Reply-To: <050.8eeb92e1b62af31dac3f1ad5e353006a@macosforge.org>
References: <050.8eeb92e1b62af31dac3f1ad5e353006a@macosforge.org>
Message-ID: <059.ae2911783bacac41e00314aa92745b2a@macosforge.org>

#359: Project Templates Not Installed By Nightly Installer
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |        Owner:  mattaimonetti@?        
     Type:  enhancement          |       Status:  closed                 
 Priority:  major                |    Milestone:  MacRuby 0.5            
Component:  MacRuby              |   Resolution:  fixed                  
 Keywords:                       |  
---------------------------------+------------------------------------------
Changes (by lsansonetti@?):

  * status:  assigned => closed
  * resolution:  => fixed


Comment:

 Looks like this bug can be closed.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/359#comment:7>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 15 21:24:49 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 16 Oct 2009 04:24:49 -0000
Subject: [MacRuby-devel] [MacRuby] #231: [0.4] Can't install hoe
In-Reply-To: <050.6b6a8ee8213a3cc3cfb03e64a9423998@macosforge.org>
References: <050.6b6a8ee8213a3cc3cfb03e64a9423998@macosforge.org>
Message-ID: <059.ef8524099db3639b7b2a0e023e123b30@macosforge.org>

#231: [0.4] Can't install hoe
---------------------------------+------------------------------------------
 Reporter:  roberto@?            |        Owner:  lsansonetti@?        
     Type:  defect               |       Status:  closed               
 Priority:  critical             |    Milestone:  MacRuby 0.5          
Component:  MacRuby              |   Resolution:  fixed                
 Keywords:  hoe, gem             |  
---------------------------------+------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Seems to work on trunk (0.5), closing.

 {{{
 $ macgem install rubyforge
 WARNING:  Installing to ~/.gem since
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0
 and
           /usr/bin aren't both writable.
 WARNING:  You don't have /Users/lrz/.gem/macruby/1.9.0/bin in your PATH,
           gem executables will not run.
 Successfully installed json_pure-1.1.9
 Successfully installed rubyforge-2.0.3
 2 gems installed
 $ macgem install hoe
 WARNING:  Installing to ~/.gem since
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0
 and
           /usr/bin aren't both writable.
 WARNING:  You don't have /Users/lrz/.gem/macruby/1.9.0/bin in your PATH,
           gem executables will not run.
 Successfully installed hoe-2.3.3
 1 gem installed
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/231#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 15 21:27:17 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 16 Oct 2009 04:27:17 -0000
Subject: [MacRuby-devel] [MacRuby] #200: NSCFBoolean instances compared
 to Ruby bools does not work as expected
In-Reply-To: <054.fdcf094334a9e06a989a5db457f54986@macosforge.org>
References: <054.fdcf094334a9e06a989a5db457f54986@macosforge.org>
Message-ID: <063.9d0ada6542c046239c63e084d010eb5e@macosforge.org>

#200: NSCFBoolean instances compared to Ruby bools does not work as expected
-------------------------------------+--------------------------------------
 Reporter:  eloy.de.enige@?          |        Owner:  lsansonetti@?        
     Type:  defect                   |       Status:  closed               
 Priority:  blocker                  |    Milestone:  MacRuby 0.5          
Component:  MacRuby                  |   Resolution:  fixed                
 Keywords:                           |  
-------------------------------------+--------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Old description:

> {{{
> >> NSNumber.numberWithBool(true) == true
> => false
> }}}
>
> Added to known_bugs in r781

New description:

 {{{
 >> NSNumber.numberWithBool(true) == true
 => false
 }}}

 Added to known_bugs in r781

--

Comment:

 This is working in trunk (0.5).

 {{{
 $ ./miniruby -e "p NSNumber.numberWithBool(true) == true"
 true
 $ ./miniruby -e "p NSNumber.numberWithBool(false) == false"
 true
 $ ./miniruby -e "p NSNumber.numberWithBool(true) == false"
 false
 $ ./miniruby -e "p NSNumber.numberWithBool(false) == true"
 false
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/200#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 15 21:34:00 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 16 Oct 2009 04:34:00 -0000
Subject: [MacRuby-devel] [MacRuby] #208: Making #binding public returns
	wrong binding.
In-Reply-To: <054.aa8c60fc00f3261de598f56290c437f7@macosforge.org>
References: <054.aa8c60fc00f3261de598f56290c437f7@macosforge.org>
Message-ID: <063.3de374b0bbed3cab97b7b612e5dee6a3@macosforge.org>

#208: Making #binding public returns wrong binding.
-------------------------------------+--------------------------------------
 Reporter:  eloy.de.enige@?          |        Owner:  lsansonetti@?        
     Type:  defect                   |       Status:  closed               
 Priority:  blocker                  |    Milestone:  MacRuby 0.5          
Component:  MacRuby                  |   Resolution:  fixed                
 Keywords:                           |  
-------------------------------------+--------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 It looks like this issue is solved in trunk.

 Note that:

 1) doing send(:binding) won't work as expected with 1.9 and will crash for
 us (assertion).
 2) calling #binding on the Foo instance will raise a "private method
 called" exception on both 1.8 and 1.9.
 3) calling #b will work as expected.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/208#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 15 21:54:21 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 16 Oct 2009 04:54:21 -0000
Subject: [MacRuby-devel] [MacRuby] #326: module_function implicit use
 breaks (ArgumentError) with 1-arg splat methods (w/test code)
In-Reply-To: <044.ebe79a4920cb9ce9785d9494cc5bc469@macosforge.org>
References: <044.ebe79a4920cb9ce9785d9494cc5bc469@macosforge.org>
Message-ID: <053.8fefca37cf16a78ae3d17152f443ea99@macosforge.org>

#326: module_function implicit use breaks (ArgumentError) with 1-arg splat
methods (w/test code)
-------------------------------------------------+--------------------------
 Reporter:  occam@?                              |        Owner:  lsansonetti@?        
     Type:  defect                               |       Status:  closed               
 Priority:  major                                |    Milestone:  MacRuby 0.5          
Component:  MacRuby                              |   Resolution:  fixed                
 Keywords:  module_function splat ArgumentError  |  
-------------------------------------------------+--------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Should be fixed in r2828.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/326#comment:4>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 15 21:54:46 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 16 Oct 2009 04:54:46 -0000
Subject: [MacRuby-devel] [MacRuby] #347: module in module_function mode
 can't have methods with default args
In-Reply-To: <054.4f10935e7152566398950e6443f14505@macosforge.org>
References: <054.4f10935e7152566398950e6443f14505@macosforge.org>
Message-ID: <063.835f3e8bbe2b0e20ff5e047719f15bb2@macosforge.org>

#347: module in module_function mode can't have methods with default args
-------------------------------------+--------------------------------------
 Reporter:  mattaimonetti@?          |        Owner:  lsansonetti@?        
     Type:  defect                   |       Status:  closed               
 Priority:  blocker                  |    Milestone:  MacRuby 0.5          
Component:  MacRuby                  |   Resolution:  fixed                
 Keywords:  module_function module   |  
-------------------------------------+--------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Old description:

> {{{
> $ macruby -e "module Foo; module_function; def bar(baz=42); baz; end;
> end; p Foo.bar(2)"
> => -e:1:in `<main>': wrong number of arguments (1 for 0) (ArgumentError)
> }}}
>

> {{{
> $ macruby -e "module Foo; def bar(baz=42); baz; end; end; include Foo; p
> bar(2)"
> => 2
> }}}
>
> {{{
> $ ruby19 -e "module Foo; module_function; def bar(baz=42); baz; end; end;
> p Foo.bar(2)"
> => 2
> }}}

New description:

 {{{
 $ macruby -e "module Foo; module_function; def bar(baz=42); baz; end; end;
 p Foo.bar(2)"
 => -e:1:in `<main>': wrong number of arguments (1 for 0) (ArgumentError)
 }}}


 {{{
 $ macruby -e "module Foo; def bar(baz=42); baz; end; end; include Foo; p
 bar(2)"
 => 2
 }}}

 {{{
 $ ruby19 -e "module Foo; module_function; def bar(baz=42); baz; end; end;
 p Foo.bar(2)"
 => 2
 }}}

--

Comment:

 Should be fixed in r2828.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/347#comment:2>
MacRuby <http://macruby.org/>


From jazzbox at 7zz.de  Fri Oct 16 00:16:33 2009
From: jazzbox at 7zz.de (B. Ohr)
Date: Fri, 16 Oct 2009 09:16:33 +0200
Subject: [MacRuby-devel] Using Gems in MacRuby
In-Reply-To: <99E63DFC-0F30-45BD-865A-44313B65A521@gmail.com>
References: <0BD9119F-541B-40C7-9DFD-6177B45794AB@allancraig.net>
	<688131F8-17D5-4012-B73B-601A41A31122@apple.com>
	<F6F58795-2E02-47A4-A9ED-8349FF71A656@gmail.com>
	<7317d7610910151810s6eb6a9c9jcad5ab0ea3cfd892@mail.gmail.com>
	<99E63DFC-0F30-45BD-865A-44313B65A521@gmail.com>
Message-ID: <4C88971A-A8C6-4AB9-A22F-736E9249E194@7zz.de>


Am 16.10.2009 um 04:55 schrieb s.ross:

> On Oct 15, 2009, at 6:10 PM, Conrad Taylor wrote:
>
>> On Thu, Oct 15, 2009 at 5:03 PM, s.ross <cwdinfo at gmail.com> wrote:
>>
>> On Oct 15, 2009, at 1:43 PM, Laurent Sansonetti wrote:
>>
>> Hi Craig,
>>
>> On Oct 14, 2009, at 7:07 PM, Craig Williams wrote:
>>
>> Hi Everyone,
>>
>> I have searched the web but have not found a good explanation on  
>> how to use
>> gems in a MacRuby project. Is there a tutorial I am missing?
>>
>> We should definitely write a tutorial about that. The RubyGems  
>> support is pretty new so I don't think anybody tried yet to embed  
>> gems in a MacRuby app. At a glance I believe it would be a matter  
>> of installing the gem inside MacRuby.framework, embed it in the app  
>> then change the GEM_HOME environment variable.
>>
>> Laurent
>>
>> Oof. Changing the framework? Maybe I'm not understanding what  
>> you're suggesting. Why would it not be enough to install all gems  
>> in a vendor/ directory and change GEM_HOME to there? Or something  
>> that would not involve embedding (eventually) all gems in use in  
>> all apps you're developing inside the MacRuby.framework...
>>
>> Steve
>>
>>
>> Steve, you should be able to install the gem(s) and require them in  
>> the relevant file(s).  You shouldn't have to unpack the gem(s) into  
>> a vendor directory because they should be visible to the Ruby  
>> environment after you require it.
>>
>> -Conrad
>
> Conrad--
>
> I guess I'm thinking of a case where you didn't want to rely on a  
> particular gem being present on a target machine -- say for an app  
> you were distributing. Naturally, the GEM_HOME built into MacRuby is  
> just fine on *my* machine. But, if I give the app to someone else  
> who may not have a particular gem installed, boom!
>
> Steve

Steve,

another solution would be, that somebody writes a gem-helper, which  
loads the required gems interactively into macgem when they are  
missing. This helper should have a Cocoa-UI for the unexperienced user  
outside and is called at program startup. Upgrading gems and testing a  
required version are possible features of such a helper.

Bernd



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091016/2d5a39a3/attachment-0001.html>

From ruby-noreply at macosforge.org  Fri Oct 16 02:03:07 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 16 Oct 2009 09:03:07 -0000
Subject: [MacRuby-devel] [MacRuby] #389: unable to set ivar in a class
 derived from String, Array, Hash
Message-ID: <045.860647f076a5d467750cd90ed4e60ed3@macosforge.org>

#389: unable to set ivar in a class derived from String, Array, Hash
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |       Owner:  lsansonetti@?        
     Type:  defect          |      Status:  new                  
 Priority:  critical        |   Milestone:  MacRuby 0.5          
Component:  MacRuby         |    Keywords:                       
----------------------------+-----------------------------------------------
 {{{
   class Foo < String
     def foo
       @foo = 42
       @foo
     end
   end
   p Foo.new.foo
 }}}

 gives a nil

 Same issue with Hash and Array.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/389>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 16 02:07:03 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 16 Oct 2009 09:07:03 -0000
Subject: [MacRuby-devel] [MacRuby] #390: File#flock is undefined
Message-ID: <045.232ce9fd4e7a11fcaca4143c2811c8a0@macosforge.org>

#390: File#flock is undefined
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |       Owner:  lsansonetti@?        
     Type:  defect          |      Status:  new                  
 Priority:  major           |   Milestone:  MacRuby 0.5          
Component:  MacRuby         |    Keywords:                       
----------------------------+-----------------------------------------------
 Calling File#flock results in:

 NoMethodError: undefined method ...

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/390>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 16 02:21:35 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 16 Oct 2009 09:21:35 -0000
Subject: [MacRuby-devel] [MacRuby] #389: unable to set ivar in a class
 derived from String, Array, Hash
In-Reply-To: <045.860647f076a5d467750cd90ed4e60ed3@macosforge.org>
References: <045.860647f076a5d467750cd90ed4e60ed3@macosforge.org>
Message-ID: <054.30645a803d8ee66d8d78ff2fad88fe92@macosforge.org>

#389: unable to set ivar in a class derived from String, Array, Hash
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |       Owner:  lsansonetti@?        
     Type:  defect          |      Status:  new                  
 Priority:  critical        |   Milestone:  MacRuby 0.5          
Component:  MacRuby         |    Keywords:                       
----------------------------+-----------------------------------------------

Comment(by jazzbox@?):

 Perhaps this is the same issue:

 {{{
 class Foo < Time

     def foo
       @foo
     end

 end

 p Foo.new.foo
 }}}

 gives wierd results or segmentation faults!

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/389#comment:1>
MacRuby <http://macruby.org/>


From conradwt at gmail.com  Fri Oct 16 02:29:50 2009
From: conradwt at gmail.com (Conrad Taylor)
Date: Fri, 16 Oct 2009 02:29:50 -0700
Subject: [MacRuby-devel] Using Gems in MacRuby
In-Reply-To: <4C88971A-A8C6-4AB9-A22F-736E9249E194@7zz.de>
References: <0BD9119F-541B-40C7-9DFD-6177B45794AB@allancraig.net>
	<688131F8-17D5-4012-B73B-601A41A31122@apple.com>
	<F6F58795-2E02-47A4-A9ED-8349FF71A656@gmail.com>
	<7317d7610910151810s6eb6a9c9jcad5ab0ea3cfd892@mail.gmail.com>
	<99E63DFC-0F30-45BD-865A-44313B65A521@gmail.com>
	<4C88971A-A8C6-4AB9-A22F-736E9249E194@7zz.de>
Message-ID: <7317d7610910160229y39ab71a1j64d984f4a20e7fbb@mail.gmail.com>

  On Fri, Oct 16, 2009 at 12:16 AM, B. Ohr <jazzbox at 7zz.de> wrote:

>
> Am 16.10.2009 um 04:55 schrieb s.ross:
>
> On Oct 15, 2009, at 6:10 PM, Conrad Taylor wrote:
>
> On Thu, Oct 15, 2009 at 5:03 PM, s.ross <cwdinfo at gmail.com> wrote:
>
>>
>> On Oct 15, 2009, at 1:43 PM, Laurent Sansonetti wrote:
>>
>>  Hi Craig,
>>>
>>> On Oct 14, 2009, at 7:07 PM, Craig Williams wrote:
>>>
>>>  Hi Everyone,
>>>>
>>>> I have searched the web but have not found a good explanation on how to
>>>> use
>>>> gems in a MacRuby project. Is there a tutorial I am missing?
>>>>
>>>
>>> We should definitely write a tutorial about that. The RubyGems support is
>>> pretty new so I don't think anybody tried yet to embed gems in a MacRuby
>>> app. At a glance I believe it would be a matter of installing the gem inside
>>> MacRuby.framework, embed it in the app then change the GEM_HOME environment
>>> variable.
>>>
>>> Laurent
>>>
>>
>> Oof. Changing the framework? Maybe I'm not understanding what you're
>> suggesting. Why would it not be enough to install all gems in a vendor/
>> directory and change GEM_HOME to there? Or something that would not involve
>> embedding (eventually) all gems in use in all apps you're developing inside
>> the MacRuby.framework...
>>
>> Steve
>>
>>
> Steve, you should be able to install the gem(s) and require them in the
> relevant file(s).  You shouldn't have to unpack the gem(s) into a vendor
> directory because they should be visible to the Ruby environment after you
> require it.
>
> -Conrad
>
>
> Conrad--
>
> I guess I'm thinking of a case where you didn't want to rely on a
> particular gem being present on a target machine -- say for an app you were
> distributing. Naturally, the GEM_HOME built into MacRuby is just fine on
> *my* machine. But, if I give the app to someone else who may not have a
> particular gem installed, boom!
>
> Steve
>
>
> Steve,
>
> another solution would be, that somebody writes a gem-helper, which loads
> the required gems interactively into macgem when they are missing. This
> helper should have a Cocoa-UI for the unexperienced user outside and is
> called at program startup. Upgrading gems and testing a required version are
> possible features of such a helper.
>
> Bernd
>
>
>
Hi, you can actually find something like this in Rails as a rake task, 'rake
gems:install'.  Thus, you can take a look at the boot.rb within the config
directory.  Now, one can simply adapt the environment.rb file from rails for
loading gems and other components:

# Be sure to restart your server when you modify this file

# Specifies gem version of Rails to use when vendor/rails is not present
RAILS_GEM_VERSION = '2.3.4' unless defined? RAILS_GEM_VERSION

# Bootstrap the Rails environment, frameworks, and default configuration
require File.join(File.dirname(__FILE__), 'boot')

Rails::Initializer.run do |config|
  # Settings in config/environments/* take precedence over those specified
here.
  # Application configuration should go into files in config/initializers
  # -- all .rb files in that directory are automatically loaded.

  # Add additional load paths for your own custom dirs
  # config.load_paths += %W( #{RAILS_ROOT}/extras )

  # Specify gems that this application depends on and have them installed
with rake gems:install
  config.gem "hpricot", :version => '0.6', :source => "
http://code.whytheluckystiff.net"
  config.gem "sqlite3-ruby", :lib => "sqlite3"
  config.gem "aws-s3", :lib => "aws/s3"

  # Only load the plugins named here, in the order given (default is
alphabetical).
  # :all can be used as a placeholder for all plugins not explicitly named
  # config.plugins = [ :exception_notification, :ssl_requirement, :all ]

  # Skip frameworks you're not going to use. To use Rails without a
database,
  # you must remove the Active Record framework.
  # config.frameworks -= [ :active_record, :active_resource, :action_mailer
]

  # Activate observers that should always be running
  # config.active_record.observers = :cacher, :garbage_collector,
:forum_observer

  # Set Time.zone default to the specified zone and make Active Record
auto-convert to this zone.
  # Run "rake -D time" for a list of tasks for finding time zone names.
  config.time_zone = 'UTC'

  # The default locale is :en and all translations from
config/locales/*.rb,yml are auto loaded.
  # config.i18n.load_path += Dir[Rails.root.join('my', 'locales',
'*.{rb,yml}')]
  # config.i18n.default_locale = :de

end

Now, you simply need to execute the following command to install the missing
components before starting the app:

rake gems:install

Otherwise, you can create an application subdirectory called lib which is
added to your load path when your application
is started.  For example,

library_paths = []
library_paths << "#{FILE.dirname(__FILE__)}/lib/some_library_one"
library_paths << "#{FILE.dirname(__FILE__)}/lib/some_library_two"
library_paths << "#{FILE.dirname(__FILE__)}/lib/some_library_three"
...

library_paths.each do | library_path |
  $:.unshift( library_path ) if File.directory?( library_path )
end

Now, you can throw all this into some type of dependencies.rb file that gets
loaded before application starts.  This may be a better approach to
follow for end users instead of expecting them to execute a command before
application starts.  Thus, you can adapt the above library_path
example to install gems as well if your application depends on them.
 Finally, you may want to also look at the Rubygems API because it does
all this stuff and more for managing gems.

Good luck,

-Conrad


>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091016/639072c8/attachment.html>

From prabhaka at apple.com  Fri Oct 16 14:01:45 2009
From: prabhaka at apple.com (Ernest N. Prabhakar, Ph.D.)
Date: Fri, 16 Oct 2009 14:01:45 -0700
Subject: [MacRuby-devel] Gem Bundler is the Future
Message-ID: <680AEB9E-F962-4853-BDEE-26A538F1CEDA@apple.com>

I wonder if this will help MacRuby applications:

http://litanyagainstfear.com/blog/2009/10/14/gem-bundler-is-the-future/


Sounds like it is tied to Rails, but might be possible to extend it slightly to serve our needs...

-enp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091016/2a58d78b/attachment.html>

From jeremy at bitsweat.net  Fri Oct 16 14:03:38 2009
From: jeremy at bitsweat.net (Jeremy Kemper)
Date: Fri, 16 Oct 2009 14:03:38 -0700
Subject: [MacRuby-devel] Gem Bundler is the Future
In-Reply-To: <680AEB9E-F962-4853-BDEE-26A538F1CEDA@apple.com>
References: <680AEB9E-F962-4853-BDEE-26A538F1CEDA@apple.com>
Message-ID: <69a2885c0910161403y2ed1a95cn73ca314a5ec8bcd5@mail.gmail.com>

On Fri, Oct 16, 2009 at 2:01 PM, Ernest N. Prabhakar, Ph.D.
<prabhaka at apple.com> wrote:
> I wonder if this will help MacRuby applications:
> http://litanyagainstfear.com/blog/2009/10/14/gem-bundler-is-the-future/
>
> Sounds like it is tied to Rails, but might be possible to extend it slightly
> to serve our needs...

It's completely independent of Rails, though Rails 3 is using it :)

jeremy

From rdm at cfcl.com  Fri Oct 16 14:14:05 2009
From: rdm at cfcl.com (Rich Morin)
Date: Fri, 16 Oct 2009 14:14:05 -0700
Subject: [MacRuby-devel] Gem Bundler is the Future
In-Reply-To: <680AEB9E-F962-4853-BDEE-26A538F1CEDA@apple.com>
References: <680AEB9E-F962-4853-BDEE-26A538F1CEDA@apple.com>
Message-ID: <p06230938c6fe923e8af1@[192.168.1.205]>

Yehuda is wicked smart and tends to reach for fundamental and
well-considered solutions, so I expect this to be quite solid.

-r
-- 
http://www.cfcl.com/rdm            Rich Morin
http://www.cfcl.com/rdm/resume     rdm at cfcl.com
http://www.cfcl.com/rdm/weblog     +1 650-873-7841

Technical editing and writing, programming, and web development

From ruby-noreply at macosforge.org  Fri Oct 16 14:18:56 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 16 Oct 2009 21:18:56 -0000
Subject: [MacRuby-devel] [MacRuby] #389: unable to set ivar in a class
 derived from String, Array, Hash
In-Reply-To: <045.860647f076a5d467750cd90ed4e60ed3@macosforge.org>
References: <045.860647f076a5d467750cd90ed4e60ed3@macosforge.org>
Message-ID: <054.6b01278efc78d9385c94f2cd6975a146@macosforge.org>

#389: unable to set ivar in a class derived from String, Array, Hash
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |        Owner:  lsansonetti@?        
     Type:  defect          |       Status:  closed               
 Priority:  critical        |    Milestone:  MacRuby 0.5          
Component:  MacRuby         |   Resolution:  fixed                
 Keywords:                  |  
----------------------------+-----------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 I fixed the problem reported in the description as r2833. The second one
 is not fixed and is actually a different bug, subclassing any T_DATA-based
 class (like our friend Time) is not supported yet. I'm closing this bug
 but feel free to file another one for the other problem.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/389#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 16 14:37:18 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 16 Oct 2009 21:37:18 -0000
Subject: [MacRuby-devel] [MacRuby] #390: File#flock is undefined
In-Reply-To: <045.232ce9fd4e7a11fcaca4143c2811c8a0@macosforge.org>
References: <045.232ce9fd4e7a11fcaca4143c2811c8a0@macosforge.org>
Message-ID: <054.d8077133da7060459f1d04d16fe97baf@macosforge.org>

#390: File#flock is undefined
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |        Owner:  lsansonetti@?        
     Type:  defect          |       Status:  closed               
 Priority:  major           |    Milestone:  MacRuby 0.5          
Component:  MacRuby         |   Resolution:  fixed                
 Keywords:                  |  
----------------------------+-----------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Should be available in r2834. I don't know if it's going to work as
 expected, but at least the one rubyspec covering this method passes now.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/390#comment:1>
MacRuby <http://macruby.org/>


From prabhaka at apple.com  Fri Oct 16 14:49:02 2009
From: prabhaka at apple.com (Ernest N. Prabhakar, Ph.D.)
Date: Fri, 16 Oct 2009 14:49:02 -0700
Subject: [MacRuby-devel] Gem Bundler is the Future
In-Reply-To: <p06230938c6fe923e8af1@[192.168.1.205]>
References: <680AEB9E-F962-4853-BDEE-26A538F1CEDA@apple.com>
	<p06230938c6fe923e8af1@[192.168.1.205]>
Message-ID: <5ED1C0B0-A38C-4C34-BF2F-07353767F850@apple.com>

Hi Rich,

On Oct 16, 2009, at 2:14 PM, Rich Morin wrote:
> Yehuda is wicked smart and tends to reach for fundamental and
> well-considered solutions, so I expect this to be quite solid.

I don't doubt that.  What I'm wondering is whether it is "generic" enough that we could use it as "the" solution for bundling arbitrary gems -- or even MacRuby itself -- inside Mac OS X applications.  Any insights on that?

-- Ernie P.



From rdm at cfcl.com  Fri Oct 16 15:01:50 2009
From: rdm at cfcl.com (Rich Morin)
Date: Fri, 16 Oct 2009 15:01:50 -0700
Subject: [MacRuby-devel] Gem Bundler is the Future
In-Reply-To: <5ED1C0B0-A38C-4C34-BF2F-07353767F850@apple.com>
References: <680AEB9E-F962-4853-BDEE-26A538F1CEDA@apple.com>
	<p06230938c6fe923e8af1@[192.168.1.205]>
	<5ED1C0B0-A38C-4C34-BF2F-07353767F850@apple.com>
Message-ID: <p06230939c6fe9c84f322@[192.168.1.205]>

At 2:49 PM -0700 10/16/09, Ernest N. Prabhakar, Ph.D. wrote:
> What I'm wondering is whether it is "generic" enough that
> we could use it as "the" solution for bundling arbitrary gems
> -- or even MacRuby itself -- inside Mac OS X applications.
> Any insights on that?

Sadly, no, but I suspect that Matt Aimonetti does (:-).  Also,
if the problems aren't too fundamental (and/or can be reported
fairly soon), there's a pretty good chance of YK fixing them.

So, I strongly suggest that the MacRuby community try out the
new tools as soon as possible and see what happens...

-r
-- 
http://www.cfcl.com/rdm            Rich Morin
http://www.cfcl.com/rdm/resume     rdm at cfcl.com
http://www.cfcl.com/rdm/weblog     +1 650-873-7841

Technical editing and writing, programming, and web development

From jbarnette at gmail.com  Fri Oct 16 15:04:34 2009
From: jbarnette at gmail.com (John Barnette)
Date: Fri, 16 Oct 2009 15:04:34 -0700
Subject: [MacRuby-devel] Gem Bundler is the Future
In-Reply-To: <p06230939c6fe9c84f322@192.168.1.205>
References: <680AEB9E-F962-4853-BDEE-26A538F1CEDA@apple.com>
	<p06230938c6fe923e8af1@192.168.1.205>
	<5ED1C0B0-A38C-4C34-BF2F-07353767F850@apple.com>
	<p06230939c6fe9c84f322@192.168.1.205>
Message-ID: <2bce3eb60910161504l1d647e6ej83ab52380243ed44@mail.gmail.com>

On Fri, Oct 16, 2009 at 3:01 PM, Rich Morin <rdm at cfcl.com> wrote:
> So, I strongly suggest that the MacRuby community try out the
> new tools as soon as possible and see what happens...

You might also want to take a look at the code in Isolate
(http://github.com/jbarnette/isolate). It's not nearly as ambitious or
far-reaching as Bundler, but it's only a couple hundred lines of code,
and it's extracted from production apps. Getting the code (if not the
gem) running on MacRuby shouldn't be burdensome.


~ j.

From eloy.de.enige at gmail.com  Fri Oct 16 15:36:28 2009
From: eloy.de.enige at gmail.com (Eloy Duran)
Date: Sat, 17 Oct 2009 00:36:28 +0200
Subject: [MacRuby-devel] Gem Bundler is the Future
In-Reply-To: <680AEB9E-F962-4853-BDEE-26A538F1CEDA@apple.com>
References: <680AEB9E-F962-4853-BDEE-26A538F1CEDA@apple.com>
Message-ID: <7B67D356-5C93-4060-9705-3462DC82E9E2@gmail.com>

I'm planning on using this in Rucola as well, this should all be ?  
rake task away. But still need to fix the plumbing fitst...

Eloy

Sent from my iPhone

On 16 okt 2009, at 23:01, "Ernest N. Prabhakar, Ph.D." <prabhaka at apple.com 
 > wrote:

> I wonder if this will help MacRuby applications:
>
> http://litanyagainstfear.com/blog/2009/10/14/gem-bundler-is-the- 
> future/
>
>
> Sounds like it is tied to Rails, but might be possible to extend it  
> slightly to serve our needs...
>
> -enp
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091017/418f39ee/attachment-0001.html>

From cwilliams at allancraig.net  Fri Oct 16 18:08:19 2009
From: cwilliams at allancraig.net (Craig Williams)
Date: Fri, 16 Oct 2009 19:08:19 -0600
Subject: [MacRuby-devel] Using Gems in MacRuby
In-Reply-To: <2521c527-2404-4a6f-a417-39072b8fce61@h40g2000prf.googlegroups.com>
References: <2521c527-2404-4a6f-a417-39072b8fce61@h40g2000prf.googlegroups.com>
Message-ID: <FB13FAE8-1C5E-4A83-9D84-23CC01FC3C2F@allancraig.net>

Hi Everyone,

I am still not understanding how to include gems in my MacRuby  
project. From what has been discussed, I "unpacked"
the gem and included it in the project in "Vendor/gems."

I am using this in the rb_main.rb file, but it is resulting in 2180  
errors.

Dir.glob(File.expand_path("#{NSBundle.mainBundle.resourcePath}/vendor/ 
gems/*", __FILE__)).each do |gem|
    $:.unshift File.join(gem, 'lib')
end

I know this must be very simple but I am not getting it. I write Ruby  
scripts nearly every day but I all of my development
experience is with Objective-C. I would really appreciate a small  
example of how to accomplish this.

Thanks,

Craig

From ruby-noreply at macosforge.org  Sat Oct 17 03:33:57 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 17 Oct 2009 10:33:57 -0000
Subject: [MacRuby-devel] [MacRuby] #391: HotCocoa on_notification method
 stopped functioning in MacRuby 0.5 under Snow Leopard
Message-ID: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>

#391: HotCocoa on_notification method stopped functioning in MacRuby 0.5 under
Snow Leopard
--------------------------------------+-------------------------------------
 Reporter:  trevor@?                  |       Owner:  lsansonetti@?           
     Type:  defect                    |      Status:  new                     
 Priority:  blocker                   |   Milestone:                          
Component:  MacRuby                   |    Keywords:  HotCocoa on_notification
--------------------------------------+-------------------------------------
 I have a small MacRuby/HotCocoa application that uses the on_notification
 method described by Richard Kilmer in his post of Sept 19 2008
 http://lists.macosforge.org/pipermail/macruby-
 devel/2008-September/000539.html

 This application worked well under MacRuby 0.4 and Mac OS 10.5. It
 intercepts Spotify Growl messages to obtain track title and artist
 information to pass into an AppleScript Studio via a small window that it
 creates. The MacRuby/HotCocoa app was provided by a friendly software
 developer, Peter MacRobert, for me since ASS did not have the appropriate
 inter-process message handling capability. The script for the app is
 attached.

 I upgraded to Snow Leopard and discovered that the app crashed out with
 MacRuby 0.4. I succeeded in downloading and installing MacRuby 0.5 and now
 the app loads successfully with no error messages as before under Leopard.

 Unfortunately the on_notification code does not get triggered any longer.
 No error messages, just stubbornly refuses to respond when the Distributed
 Notifications Center gets the Spotify message. I am able to see that the
 message is there by firing up Growl which shows the message each time
 Spotify plays a track.

 Under Mac OS 10.5, it was necessary to have Growl stopped for this app to
 be able to intercept the message coming out of Spotify destined for the
 Growl alert.

 I'm afraid I am not familiar with what is required to set up a test case.
 All I can do is describe the situation. I believe that Spotify is now
 available in the USA, it's a music streaming application (excellent btw,
 if you're not familiar). When running a Spotify session every time a track
 is launched it sends a message to the Distributed Notifications Center
 containing the Track Artist  & Title information, if the system has Growl
 installed and configured for Spotify, a Growl alert will appear to the
 configured spec in Growl. If my MacRuby script is running (and, under
 10.5, Growl is turned off) it will intercept the Spotify message and show
 the Artist and track name in the two text fields of the window that it
 opens.

 This may sound crazy to you and it would take a while to explain why I
 have this application.  Briefly, it's used by an Applescript Studio App
 that I wrote (hobby only, not commercial) which controls Spotify and hides
 the windows to play a "Beat the Intro" game for competing teams. The
 MacRuby window is hidden and is used to pass the track details from
 Spotify to the ASS application.

 I'm sure that there would be a much easier way to test the HotCocoa
 on_notification method than setting up a test with my script and using
 Spotify. But I'm afraid I do not know how to do that.

 Regards

 Trevor Hills

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/391>
MacRuby <http://macruby.org/>


From mattaimonetti at gmail.com  Sat Oct 17 09:09:33 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Sat, 17 Oct 2009 13:09:33 -0300
Subject: [MacRuby-devel] Gem Bundler is the Future
In-Reply-To: <7B67D356-5C93-4060-9705-3462DC82E9E2@gmail.com>
References: <680AEB9E-F962-4853-BDEE-26A538F1CEDA@apple.com>
	<7B67D356-5C93-4060-9705-3462DC82E9E2@gmail.com>
Message-ID: <20fefa50910170909v18e74ec1l1ac7987e592be146@mail.gmail.com>

The Gem bundler that Carl Lerche and Yehuda Katz worked on should in theory
work great with MacRuby. However, as far as I know, it doesn't offer a
fallback to system gems, so you need to package all your gems with your
application. (which, really, shouldn't be a problem)

That said, I never gave it a shot with MacRuby, but that sounds like a fun
project for when I come back from vacation.

- Matt


On Fri, Oct 16, 2009 at 7:36 PM, Eloy Duran <eloy.de.enige at gmail.com> wrote:

> I'm planning on using this in Rucola as well, this should all be ? rake
> task away. But still need to fix the plumbing fitst...
>
> Eloy
>
> Sent from my iPhone
>
> On 16 okt 2009, at 23:01, "Ernest N. Prabhakar, Ph.D." <prabhaka at apple.com>
> wrote:
>
> I wonder if this will help MacRuby applications:
>
> <http://litanyagainstfear.com/blog/2009/10/14/gem-bundler-is-the-future/>
> http://litanyagainstfear.com/blog/2009/10/14/gem-bundler-is-the-future/
>
> Sounds like it is tied to Rails, but might be possible to extend it
> slightly to serve our needs...
>
> -enp
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091017/9b4332c6/attachment.html>

From rice.audio at pobox.com  Sat Oct 17 13:53:47 2009
From: rice.audio at pobox.com (Robert Rice)
Date: Sat, 17 Oct 2009 16:53:47 -0400
Subject: [MacRuby-devel] Serial Port I/O
Message-ID: <F483C80A-E444-4754-B1DB-04E46D48AF01@pobox.com>

Hi Team:

Do you have a recommended way to do serial port I/O in a MacRuby  
environment? I was using ruby-serialport in the RubyCocoa environment  
but the gem gives me the following error:

Password:
ERROR:  While executing gem ... (RuntimeError)
     MacRuby does not support native extensions yet. Be patient :-)
new-host:~ robertrice$

Thanks,
Bob Rice

From lsansonetti at apple.com  Sat Oct 17 14:07:21 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Sat, 17 Oct 2009 14:07:21 -0700
Subject: [MacRuby-devel] Serial Port I/O
In-Reply-To: <F483C80A-E444-4754-B1DB-04E46D48AF01@pobox.com>
References: <F483C80A-E444-4754-B1DB-04E46D48AF01@pobox.com>
Message-ID: <F6D2AF00-1346-4BAE-8F27-665223A7D109@apple.com>

Hi Robert,

ruby-serialport is not going to work anytime soon, but I think there  
are alternatives in the Cocoa world that you could use.

I did some googling and found http://sourceforge.net/projects/ 
amserial/. You might be able to use this framework inside your app,  
assuming it works with garbage collection.

Laurent

On Oct 17, 2009, at 1:53 PM, Robert Rice wrote:

> Hi Team:
>
> Do you have a recommended way to do serial port I/O in a MacRuby  
> environment? I was using ruby-serialport in the RubyCocoa  
> environment but the gem gives me the following error:
>
> Password:
> ERROR:  While executing gem ... (RuntimeError)
>    MacRuby does not support native extensions yet. Be patient :-)
> new-host:~ robertrice$
>
> Thanks,
> Bob Rice
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From koudelka at ryoukai.org  Sat Oct 17 14:50:29 2009
From: koudelka at ryoukai.org (Michael Shapiro)
Date: Sat, 17 Oct 2009 17:50:29 -0400
Subject: [MacRuby-devel] Gem Bundler is the Future
In-Reply-To: <680AEB9E-F962-4853-BDEE-26A538F1CEDA@apple.com>
References: <680AEB9E-F962-4853-BDEE-26A538F1CEDA@apple.com>
Message-ID: <F915A640-2AB4-438F-919A-42CEC6910F56@ryoukai.org>

If the AOT compiler's being used, I wonder if there's the possibility  
of statically compiling gems into the executable itself?

--Mike

On Oct 16, 2009, at 5:01 PM, Ernest N. Prabhakar, Ph.D. wrote:

> I wonder if this will help MacRuby applications:
>
> http://litanyagainstfear.com/blog/2009/10/14/gem-bundler-is-the- 
> future/
>
>
> Sounds like it is tied to Rails, but might be possible to extend it  
> slightly to serve our needs...
>
> -enp
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From jonathan.r.hicks at gmail.com  Sat Oct 17 16:03:50 2009
From: jonathan.r.hicks at gmail.com (Jonathan Hicks)
Date: Sat, 17 Oct 2009 18:03:50 -0500
Subject: [MacRuby-devel] Gem Bundler is the Future
In-Reply-To: <F915A640-2AB4-438F-919A-42CEC6910F56@ryoukai.org>
References: <680AEB9E-F962-4853-BDEE-26A538F1CEDA@apple.com>
	<F915A640-2AB4-438F-919A-42CEC6910F56@ryoukai.org>
Message-ID: <abb3a10a0910171603u15a8da1frd569c66e848381ba@mail.gmail.com>

It looks like support for system gems was added today.
http://github.com/wycats/bundler/commit/8a7ee26c8a979b69a2b7b299a3d9bfe248fe71ad


                      --J



On Sat, Oct 17, 2009 at 4:50 PM, Michael Shapiro <koudelka at ryoukai.org> wrote:
> If the AOT compiler's being used, I wonder if there's the possibility of
> statically compiling gems into the executable itself?
>
> --Mike
>
> On Oct 16, 2009, at 5:01 PM, Ernest N. Prabhakar, Ph.D. wrote:
>
>> I wonder if this will help MacRuby applications:
>>
>> http://litanyagainstfear.com/blog/2009/10/14/gem-bundler-is-the-future/
>>
>>
>> Sounds like it is tied to Rails, but might be possible to extend it
>> slightly to serve our needs...
>>
>> -enp
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>

From conradwt at gmail.com  Sat Oct 17 16:09:26 2009
From: conradwt at gmail.com (Conrad Taylor)
Date: Sat, 17 Oct 2009 16:09:26 -0700
Subject: [MacRuby-devel] Gem Bundler is the Future
In-Reply-To: <F915A640-2AB4-438F-919A-42CEC6910F56@ryoukai.org>
References: <680AEB9E-F962-4853-BDEE-26A538F1CEDA@apple.com>
	<F915A640-2AB4-438F-919A-42CEC6910F56@ryoukai.org>
Message-ID: <7317d7610910171609y4c127280u11332dbef7010324@mail.gmail.com>

Mike, this sounds like a very interesting option for packaging gems with a
MacRuby application.  Also, one might be able to ship dynamically linked
libraries with the
application.

-Conrad

On Sat, Oct 17, 2009 at 2:50 PM, Michael Shapiro <koudelka at ryoukai.org>wrote:

> If the AOT compiler's being used, I wonder if there's the possibility of
> statically compiling gems into the executable itself?
>
> --Mike
>
>
> On Oct 16, 2009, at 5:01 PM, Ernest N. Prabhakar, Ph.D. wrote:
>
>   I wonder if this will help MacRuby applications:
>>
>> http://litanyagainstfear.com/blog/2009/10/14/gem-bundler-is-the-future/
>>
>>
>> Sounds like it is tied to Rails, but might be possible to extend it
>> slightly to serve our needs...
>>
>> -enp
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091017/30d11918/attachment.html>

From joshua.ballanco at apple.com  Sat Oct 17 16:38:27 2009
From: joshua.ballanco at apple.com (Joshua Ballanco)
Date: Sat, 17 Oct 2009 16:38:27 -0700
Subject: [MacRuby-devel] TDD in Objective-C with MacRuby
Message-ID: <11283C49-0C0E-4976-A2D1-FF92C4E6231A@apple.com>

Hey all!

So, I've finished up the TDD recipe. You can find a PDF of it at http://files.me.com/jballanc/1lxnwb 
. Please look it over and let me know what you think! I welcome all  
comments/criticisms/suggestions.

Cheers,

Josh

From ruby-noreply at macosforge.org  Sat Oct 17 17:51:16 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 18 Oct 2009 00:51:16 -0000
Subject: [MacRuby-devel] [MacRuby] #353: No such file to load bigdecimal
In-Reply-To: <051.aa041ea2c1a8eee57a43c8998a5c0965@macosforge.org>
References: <051.aa041ea2c1a8eee57a43c8998a5c0965@macosforge.org>
Message-ID: <060.70101bd62bf046cad8cf43025679fb78@macosforge.org>

#353: No such file to load bigdecimal
----------------------------------+-----------------------------------------
 Reporter:  noelrappin@?          |        Owner:  lsansonetti@?        
     Type:  defect                |       Status:  closed               
 Priority:  blocker               |    Milestone:  MacRuby 0.5          
Component:  MacRuby               |   Resolution:  fixed                
 Keywords:                        |  
----------------------------------+-----------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Should be available as of r2844.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/353#comment:2>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Sat Oct 17 17:57:29 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Sat, 17 Oct 2009 17:57:29 -0700
Subject: [MacRuby-devel] TDD in Objective-C with MacRuby
In-Reply-To: <11283C49-0C0E-4976-A2D1-FF92C4E6231A@apple.com>
References: <11283C49-0C0E-4976-A2D1-FF92C4E6231A@apple.com>
Message-ID: <D75F17F5-0DAC-43D2-955C-0E7624C15D75@apple.com>

Hi Josh,

It's awesome! Unless someone has any objection I will deploy it by  
tomorrow :-) For those interested, the changes are already committed  
to the MacRubyWebsite repository.

Thanks a lot for this work!

Laurent

On Oct 17, 2009, at 4:38 PM, Joshua Ballanco wrote:

> Hey all!
>
> So, I've finished up the TDD recipe. You can find a PDF of it at http://files.me.com/jballanc/1lxnwb 
> . Please look it over and let me know what you think! I welcome all  
> comments/criticisms/suggestions.
>
> Cheers,
>
> Josh
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From mattaimonetti at gmail.com  Sat Oct 17 18:46:45 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Sat, 17 Oct 2009 22:46:45 -0300
Subject: [MacRuby-devel] TDD in Objective-C with MacRuby
In-Reply-To: <D75F17F5-0DAC-43D2-955C-0E7624C15D75@apple.com>
References: <11283C49-0C0E-4976-A2D1-FF92C4E6231A@apple.com>
	<D75F17F5-0DAC-43D2-955C-0E7624C15D75@apple.com>
Message-ID: <20fefa50910171846p251e77d7scd18dffb321f8fdc@mail.gmail.com>

Wow, this is awesome, this post is going to be very helpful!

- Matt

On Sat, Oct 17, 2009 at 9:57 PM, Laurent Sansonetti
<lsansonetti at apple.com>wrote:

> Hi Josh,
>
> It's awesome! Unless someone has any objection I will deploy it by tomorrow
> :-) For those interested, the changes are already committed to the
> MacRubyWebsite repository.
>
> Thanks a lot for this work!
>
> Laurent
>
>
> On Oct 17, 2009, at 4:38 PM, Joshua Ballanco wrote:
>
>  Hey all!
>>
>> So, I've finished up the TDD recipe. You can find a PDF of it at
>> http://files.me.com/jballanc/1lxnwb. Please look it over and let me know
>> what you think! I welcome all comments/criticisms/suggestions.
>>
>> Cheers,
>>
>> Josh
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091017/fb862416/attachment.html>

From joshua.ballanco at apple.com  Sat Oct 17 19:57:34 2009
From: joshua.ballanco at apple.com (Joshua Ballanco)
Date: Sat, 17 Oct 2009 19:57:34 -0700
Subject: [MacRuby-devel] TDD in Objective-C with MacRuby
In-Reply-To: <20fefa50910171846p251e77d7scd18dffb321f8fdc@mail.gmail.com>
References: <11283C49-0C0E-4976-A2D1-FF92C4E6231A@apple.com>
	<D75F17F5-0DAC-43D2-955C-0E7624C15D75@apple.com>
	<20fefa50910171846p251e77d7scd18dffb321f8fdc@mail.gmail.com>
Message-ID: <0E9E775C-BED7-4A36-8971-4A6A80DB8166@apple.com>

Thanks guys!

I fixed a few typos and committed the change. If you find any more  
please let me know (or feel free to fix as you see fit). One thing I'd  
like to work on when I get some time (yeah, right...) is a custom  
Xcode output formatter for Bacon. If we match the output format of the  
RunTestUnits script, then we should even get links from the build  
results window to the failing test in the text editor.

Cheers,

Josh


On Oct 17, 2009, at 6:46 PM, Matt Aimonetti wrote:

> Wow, this is awesome, this post is going to be very helpful!
>
> - Matt
>
> On Sat, Oct 17, 2009 at 9:57 PM, Laurent Sansonetti <lsansonetti at apple.com 
> > wrote:
> Hi Josh,
>
> It's awesome! Unless someone has any objection I will deploy it by  
> tomorrow :-) For those interested, the changes are already committed  
> to the MacRubyWebsite repository.
>
> Thanks a lot for this work!
>
> Laurent
>
>
> On Oct 17, 2009, at 4:38 PM, Joshua Ballanco wrote:
>
> Hey all!
>
> So, I've finished up the TDD recipe. You can find a PDF of it at http://files.me.com/jballanc/1lxnwb 
> . Please look it over and let me know what you think! I welcome all  
> comments/criticisms/suggestions.
>
> Cheers,
>
> Josh
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091017/9ad8c888/attachment.html>

From ruby-noreply at macosforge.org  Sun Oct 18 00:38:03 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 18 Oct 2009 07:38:03 -0000
Subject: [MacRuby-devel] [MacRuby] #391: HotCocoa on_notification method
 stopped functioning in MacRuby 0.5 under Snow Leopard
In-Reply-To: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
References: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
Message-ID: <064.c59ff3472747e190cace1fec78f9cd0f@macosforge.org>

#391: HotCocoa on_notification method stopped functioning in MacRuby 0.5 under
Snow Leopard
--------------------------------------+-------------------------------------
 Reporter:  trevor@?                  |       Owner:  lsansonetti@?           
     Type:  defect                    |      Status:  new                     
 Priority:  blocker                   |   Milestone:                          
Component:  MacRuby                   |    Keywords:  HotCocoa on_notification
--------------------------------------+-------------------------------------

Comment(by lsansonetti@?):

 Could you try to reduce the problem to a script that doesn't require a 3rd
 party app to be installed?

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/391#comment:1>
MacRuby <http://macruby.org/>


From eloy.de.enige at gmail.com  Sun Oct 18 02:44:18 2009
From: eloy.de.enige at gmail.com (Eloy Duran)
Date: Sun, 18 Oct 2009 11:44:18 +0200
Subject: [MacRuby-devel] TDD in Objective-C with MacRuby
In-Reply-To: <0E9E775C-BED7-4A36-8971-4A6A80DB8166@apple.com>
References: <11283C49-0C0E-4976-A2D1-FF92C4E6231A@apple.com>
	<D75F17F5-0DAC-43D2-955C-0E7624C15D75@apple.com>
	<20fefa50910171846p251e77d7scd18dffb321f8fdc@mail.gmail.com>
	<0E9E775C-BED7-4A36-8971-4A6A80DB8166@apple.com>
Message-ID: <27CE6BBE-0BEF-4969-8D64-7AE0D975E946@gmail.com>

Very nice work Joshua!

Eloy

Sent from my iPhone

On 18 okt 2009, at 04:57, Joshua Ballanco <joshua.ballanco at apple.com>  
wrote:

> Thanks guys!
>
> I fixed a few typos and committed the change. If you find any more  
> please let me know (or feel free to fix as you see fit). One thing  
> I'd like to work on when I get some time (yeah, right...) is a  
> custom Xcode output formatter for Bacon. If we match the output  
> format of the RunTestUnits script, then we should even get links  
> from the build results window to the failing test in the text editor.
>
> Cheers,
>
> Josh
>
>
> On Oct 17, 2009, at 6:46 PM, Matt Aimonetti wrote:
>
>> Wow, this is awesome, this post is going to be very helpful!
>>
>> - Matt
>>
>> On Sat, Oct 17, 2009 at 9:57 PM, Laurent Sansonetti <lsansonetti at apple.com 
>> > wrote:
>> Hi Josh,
>>
>> It's awesome! Unless someone has any objection I will deploy it by  
>> tomorrow :-) For those interested, the changes are already  
>> committed to the MacRubyWebsite repository.
>>
>> Thanks a lot for this work!
>>
>> Laurent
>>
>>
>> On Oct 17, 2009, at 4:38 PM, Joshua Ballanco wrote:
>>
>> Hey all!
>>
>> So, I've finished up the TDD recipe. You can find a PDF of it at http://files.me.com/jballanc/1lxnwb 
>> . Please look it over and let me know what you think! I welcome all  
>> comments/criticisms/suggestions.
>>
>> Cheers,
>>
>> Josh
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091018/82a85347/attachment-0001.html>

From julian at raschke.de  Sun Oct 18 03:16:19 2009
From: julian at raschke.de (Julian Raschke)
Date: Sun, 18 Oct 2009 18:16:19 +0800
Subject: [MacRuby-devel] How to properly wrap a C/C++ library for MacRuby
	(esp.: new/alloc/initialize)
Message-ID: <4C5350AF-71C5-463A-9685-3CC9464546BE@raschke.de>

Background: I want to let some existing Ruby projects run on MacRuby  
which depend on several C extensions. Since I have done some Objective  
C(++) before, I thought I would just follow the macruby.org guide on  
how to write an Objective C bundle for use with MacRuby. (Seemed  
conceptually easier to me than using FFI.)

My problem is that I don't know how to best conceal the fact that the  
wrapped objects are now NSObjects, not typical C extension objects. I  
can monkey-patch the method signature style, but I feel that it isn't  
so trivial for constructors. The reasons for that probably reach  
deeper into MR/Cocoa than I have looked so far.

The existing Ruby code expects to be able to do:

MyCObject.new(2, 4)

however my wrapped-through-Objective-C library only offers:

MyCObject.alloc.initWithA 2, b: 4

I have tried to just override MyCObject.new to call  
alloc.initWithA:b:, but that breaks as soon as the user wants to  
override "initialize". He may even want to call "super" at a defined  
point in there.

I have also tried writing a "initialize" method that calls  
"initWithA:b:", and calling "alloc.initialize(a, b)" from within  
MyCObject.new. I expected that this may allow for overriding  
#initialize. Instead, it leads to a segfault.

Is there a way to completely hide the fact that MyCObject is actually  
not a plain old Ruby class?

Julian


From conradwt at gmail.com  Sun Oct 18 04:29:26 2009
From: conradwt at gmail.com (Conrad Taylor)
Date: Sun, 18 Oct 2009 04:29:26 -0700
Subject: [MacRuby-devel]  rake spec:ci
Message-ID: <7317d7610910180429k35b2448xe4fb761e5dc9f579@mail.gmail.com>

Hi, the 'macrake spec:ci'  is failing using r2848.

BEGIN OUTPUT:

$ macrake spec:ci
(in /Users/conradwt/macruby.dir/projects/macruby-trunk)
unknown: warning: already initialized constant MACRUBY_VERSION
./mspec/bin/mspec ci -B ./spec/macruby.mspec  :full
MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
......2009-10-18 04:25:27.098 macruby[16464:1b07] *** Terminating app due to
uncaught exception 'TypeError', reason: '42 is not a symbol'
*** Call stack at first throw:
(
0   CoreFoundation                      0x00007fff82a995a4
__exceptionPreprocess + 180
1   libobjc.A.dylib                     0x00007fff86ae3313
objc_exception_throw + 45
2   libmacruby.dylib                    0x0000000100179285 rb_vm_raise + 437
3   libmacruby.dylib                    0x000000010003ff69 rb_exc_raise + 9
4   libmacruby.dylib                    0x000000010003e286 rb_raise + 310
5   libmacruby.dylib                    0x00000001000eddc0 rb_str_dump + 0
6   libmacruby.dylib                    0x000000010011c6fe
rb_queue_get_concurrent + 46
7   libmacruby.dylib                    0x00000001001667cd rb_vm_dispatch +
6269
8   ???                                 0x000000010117ff98 0x0 + 4313317272
9   libmacruby.dylib                    0x00000001001667cd rb_vm_dispatch +
6269
10  ???                                 0x0000000101171e55 0x0 + 4313259605
11  ???                                 0x000000010116d2b5 0x0 + 4313240245
)
terminate called after throwing an instance of 'NSException'
rake aborted!
Command failed with status (): [./mspec/bin/mspec ci -B
./spec/macruby.msp...]

END OUTPUT:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091018/a0f5d0f4/attachment.html>

From lsansonetti at apple.com  Sun Oct 18 12:34:18 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Sun, 18 Oct 2009 12:34:18 -0700
Subject: [MacRuby-devel] TDD in Objective-C with MacRuby
In-Reply-To: <27CE6BBE-0BEF-4969-8D64-7AE0D975E946@gmail.com>
References: <11283C49-0C0E-4976-A2D1-FF92C4E6231A@apple.com>
	<D75F17F5-0DAC-43D2-955C-0E7624C15D75@apple.com>
	<20fefa50910171846p251e77d7scd18dffb321f8fdc@mail.gmail.com>
	<0E9E775C-BED7-4A36-8971-4A6A80DB8166@apple.com>
	<27CE6BBE-0BEF-4969-8D64-7AE0D975E946@gmail.com>
Message-ID: <A66C4605-C3E4-4CEB-81AB-CB5526ED0F8F@apple.com>

It's now live :)

Laurent

On Oct 18, 2009, at 2:44 AM, Eloy Duran wrote:

> Very nice work Joshua!
>
> Eloy
>
> Sent from my iPhone
>
> On 18 okt 2009, at 04:57, Joshua Ballanco  
> <joshua.ballanco at apple.com> wrote:
>
>> Thanks guys!
>>
>> I fixed a few typos and committed the change. If you find any more  
>> please let me know (or feel free to fix as you see fit). One thing  
>> I'd like to work on when I get some time (yeah, right...) is a  
>> custom Xcode output formatter for Bacon. If we match the output  
>> format of the RunTestUnits script, then we should even get links  
>> from the build results window to the failing test in the text editor.
>>
>> Cheers,
>>
>> Josh
>>
>>
>> On Oct 17, 2009, at 6:46 PM, Matt Aimonetti wrote:
>>
>>> Wow, this is awesome, this post is going to be very helpful!
>>>
>>> - Matt
>>>
>>> On Sat, Oct 17, 2009 at 9:57 PM, Laurent Sansonetti <lsansonetti at apple.com 
>>> > wrote:
>>> Hi Josh,
>>>
>>> It's awesome! Unless someone has any objection I will deploy it by  
>>> tomorrow :-) For those interested, the changes are already  
>>> committed to the MacRubyWebsite repository.
>>>
>>> Thanks a lot for this work!
>>>
>>> Laurent
>>>
>>>
>>> On Oct 17, 2009, at 4:38 PM, Joshua Ballanco wrote:
>>>
>>> Hey all!
>>>
>>> So, I've finished up the TDD recipe. You can find a PDF of it at http://files.me.com/jballanc/1lxnwb 
>>> . Please look it over and let me know what you think! I welcome  
>>> all comments/criticisms/suggestions.
>>>
>>> Cheers,
>>>
>>> Josh
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Sun Oct 18 16:36:56 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 18 Oct 2009 23:36:56 -0000
Subject: [MacRuby-devel] [MacRuby] #392: String subclass obj.dup loses its
	class
Message-ID: <047.91a220ee842e506177cc588758ee0382@macosforge.org>

#392: String subclass obj.dup loses its class
------------------------------+---------------------------------------------
 Reporter:  timshadel@?       |       Owner:  lsansonetti@?        
     Type:  defect            |      Status:  new                  
 Priority:  major             |   Milestone:  MacRuby 0.5          
Component:  MacRuby           |    Keywords:  dup string           
------------------------------+---------------------------------------------
 From normal IRB

 >> class StringChild < String; end
 => nil
 >> c = StringChild.new
 => ""
 >> c.class
 => StringChild
 >> d = c.dup
 => ""
 >> d.class
 => StringChild


 from macirb (0.5b1)

 >> class StringChild < String; end
 => nil
 >> c = StringChild.new
 => ""
 >> c.class
 => StringChild
 >> d = c.dup
 => ""
 >> d.class
 => NSMutableString


 I found this through trying to use the BlueCloth gem (renders Markdown to
 HTML).

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/392>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct 19 12:37:47 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Mon, 19 Oct 2009 19:37:47 -0000
Subject: [MacRuby-devel] [MacRuby] #378: Macruby 0.5 allows
 instantiation of a Module instance
In-Reply-To: <056.b6b4d62f7733b375cf6d91488345844b@macosforge.org>
References: <056.b6b4d62f7733b375cf6d91488345844b@macosforge.org>
Message-ID: <065.d946c9f3cddd6543dd8cd6296358081a@macosforge.org>

#378: Macruby 0.5 allows instantiation of a Module instance
---------------------------------------+------------------------------------
 Reporter:  keith.gautreaux@?          |       Owner:  lsansonetti@?        
     Type:  defect                     |      Status:  new                  
 Priority:  minor                      |   Milestone:  MacRuby 0.5          
Component:  MacRuby                    |    Keywords:                       
---------------------------------------+------------------------------------

Comment(by eloy.de.enige@?):

 Hey,

 About writing specs, the rubyspec disallows the use of ?should?. And it
 should be enough to verify that calling #new results in a NoMethodError,
 all the others should then fail as well. Also, if you want specify that an
 exception is raised, you should do so inside a proc. For instance: lambda
 { Fred.new }.should raise_error(NoMethodError). (For more info see the
 rubyspec wiki.)

 However, the rubyspec is about specifying what actually _does_ work on
 MRI, not about what doesn't. For these cases we have the test_vm test
 suite. In fact there was already a failing test similar to this case.
 Nonetheless I've added an extra failing test, based on your example, in
 r2851.

 Thanks.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/378#comment:2>
MacRuby <http://macruby.org/>


From prabhaka at apple.com  Mon Oct 19 12:56:13 2009
From: prabhaka at apple.com (Ernest N. Prabhakar, Ph.D.)
Date: Mon, 19 Oct 2009 12:56:13 -0700
Subject: [MacRuby-devel] Using Bacon with MacRuby
Message-ID: <8B1E8C2F-D8C7-47F2-A885-C46022426689@apple.com>

Hi all,

I'm trying to use Bacon with MacRuby, and am running into an odd error:

A new array
- should be empty
- should have zero size
- should raise on trying fetch any index
- should have an object identity
- should be a palindrome
- should have super powers [FAILED]

core:in `write:': not opened for writing (IOError)


Running it with "bacon" on the command-line avoids the problem, and 'fails' correctly. :-)

Here's my config -- any suggestions?  Is this a real bug, or user error?

-- Ernie P.


> $ macruby --version
> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
> $ sudo macgem install bacon
> $ macgem list
> 
> *** LOCAL GEMS ***
> 
> bacon (1.1.0)


I am using the whirlwind tutorial for Bacon 1.1:

http://www.ruby-forum.com/topic/172139

> #!/usr/local/bin/macruby
> 
> require 'rubygems'
> require 'bacon'
...



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091019/9a1205d1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: whirlwind.rb
Type: text/x-ruby-script
Size: 937 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091019/9a1205d1/attachment.bin>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091019/9a1205d1/attachment-0001.html>

From eloy.de.enige at gmail.com  Mon Oct 19 13:38:52 2009
From: eloy.de.enige at gmail.com (Eloy Duran)
Date: Mon, 19 Oct 2009 22:38:52 +0200
Subject: [MacRuby-devel] Using Bacon with MacRuby
In-Reply-To: <8B1E8C2F-D8C7-47F2-A885-C46022426689@apple.com>
References: <8B1E8C2F-D8C7-47F2-A885-C46022426689@apple.com>
Message-ID: <0C052A90-4331-422F-92C9-01C39608368E@gmail.com>

If you mean that this happens when running it from XCode, then my  
guess is that stdout is unavailable to macruby. As flunk tries to use  
that iirc. No idea why that would be the case though?

Eloy

On 19 okt 2009, at 21:56, Ernest N. Prabhakar, Ph.D. wrote:

> Hi all,
>
> I'm trying to use Bacon with MacRuby, and am running into an odd  
> error:
>
> A new array
> - should be empty
> - should have zero size
> - should raise on trying fetch any index
> - should have an object identity
> - should be a palindrome
> - should have super powers [FAILED]
>
> core:in `write:': not opened for writing (IOError)
>
>
> Running it with "bacon" on the command-line avoids the problem, and  
> 'fails' correctly. :-)
>
> Here's my config -- any suggestions?  Is this a real bug, or user  
> error?
>
> -- Ernie P.
>
>
>> $ macruby --version
>> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
>> $ sudo macgem install bacon
>> $ macgem list
>>
>> *** LOCAL GEMS ***
>>
>> bacon (1.1.0)
>
>
> I am using the whirlwind tutorial for Bacon 1.1:
>
> http://www.ruby-forum.com/topic/172139
>
>> #!/usr/local/bin/macruby
>>
>> require 'rubygems'
>> require 'bacon'
> ...
>
>
>
> <whirlwind.rb>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091019/f646a1fb/attachment.html>

From prabhaka at apple.com  Mon Oct 19 13:46:28 2009
From: prabhaka at apple.com (Ernest N. Prabhakar, Ph.D.)
Date: Mon, 19 Oct 2009 13:46:28 -0700
Subject: [MacRuby-devel] Using Bacon with MacRuby
In-Reply-To: <0C052A90-4331-422F-92C9-01C39608368E@gmail.com>
References: <8B1E8C2F-D8C7-47F2-A885-C46022426689@apple.com>
	<0C052A90-4331-422F-92C9-01C39608368E@gmail.com>
Message-ID: <86BB04A6-3ECE-498A-934F-4639FEA618BF@apple.com>


On Oct 19, 2009, at 1:38 PM, Eloy Duran wrote:

> If you mean that this happens when running it from XCode, then my guess is that stdout is unavailable to macruby. As flunk tries to use that iirc. No idea why that would be the case though?

Ah, I was running it in TextMate.  Runs fine from the Terminal, thanks.  I've filed a bug against Bacon in case they have any ideas...

-enp



> 
> Eloy
> 
> On 19 okt 2009, at 21:56, Ernest N. Prabhakar, Ph.D. wrote:
> 
>> Hi all,
>> 
>> I'm trying to use Bacon with MacRuby, and am running into an odd error:
>> 
>> A new array
>> - should be empty
>> - should have zero size
>> - should raise on trying fetch any index
>> - should have an object identity
>> - should be a palindrome
>> - should have super powers [FAILED]
>> 
>> core:in `write:': not opened for writing (IOError)
>> 
>> 
>> Running it with "bacon" on the command-line avoids the problem, and 'fails' correctly. :-)
>> 
>> Here's my config -- any suggestions?  Is this a real bug, or user error?
>> 
>> -- Ernie P.
>> 
>> 
>>> $ macruby --version
>>> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
>>> $ sudo macgem install bacon
>>> $ macgem list
>>> 
>>> *** LOCAL GEMS ***
>>> 
>>> bacon (1.1.0)
>> 
>> 
>> I am using the whirlwind tutorial for Bacon 1.1:
>> 
>> http://www.ruby-forum.com/topic/172139
>> 
>>> #!/usr/local/bin/macruby
>>> 
>>> require 'rubygems'
>>> require 'bacon'
>> ...
>> 
>> 
>> 
>> <whirlwind.rb>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> 
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091019/c242b661/attachment.html>

From ruby-noreply at macosforge.org  Mon Oct 19 14:24:33 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Mon, 19 Oct 2009 21:24:33 -0000
Subject: [MacRuby-devel] [MacRuby] #393: Custom accessors for KVO
Message-ID: <051.89bd6963b0603dfaf29f0ac1537860e4@macosforge.org>

#393: Custom accessors for KVO
----------------------------------+-----------------------------------------
 Reporter:  paolo.bosetti@?       |       Owner:  lsansonetti@?        
     Type:  defect                |      Status:  new                  
 Priority:  minor                 |   Milestone:  MacRuby 0.5          
Component:  MacRuby               |    Keywords:  KVO                  
----------------------------------+-----------------------------------------
 if one creates custom accessors fro object keys to be used for KVO, the
 setter cannot be made KVO-compliant. The runtime error message is
 something like:

 KVO autonotifying only supports -set<Key>: methods that return void.
 Autonotifying will not be done for invocations of -[MyController
 setSlider:].

 Even making the setter returning nil doesn't work.
 See the attached example.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/393>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct 19 15:15:21 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Mon, 19 Oct 2009 22:15:21 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
Message-ID: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  blocker            |   Milestone:                       
Component:  MacRuby            |    Keywords:                       
-------------------------------+--------------------------------------------
 The following code worked under earlier builds of MacRuby and oddly, on
 32-bit Snowy.

 {{{
   def control(control, textView: view, completions: completions,
 forPartialWordRange: range, indexOfSelectedItem: index)
     puts "called completions #{range}"
     target = view.textStorage.string[range.location, range.length]
     completion_list_for(target, Strings::AutocompletionsFor[:keywords])
   end
 }}}

 Now, it is called as the delegate method, but generates the console error:

 {{{
 2009-10-19 15:09:43.595 IStockCocoa[8362:a0f] unrecognized runtime type
 `{_NSRange=II}'
 }}}

 Further info:

 {{{
 $ macruby -v
 MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
 }}}

 MacOS 10.6.1

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct 19 15:51:56 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Mon, 19 Oct 2009 22:51:56 -0000
Subject: [MacRuby-devel] [MacRuby] #378: Macruby 0.5 allows
 instantiation of a Module instance
In-Reply-To: <056.b6b4d62f7733b375cf6d91488345844b@macosforge.org>
References: <056.b6b4d62f7733b375cf6d91488345844b@macosforge.org>
Message-ID: <065.3cf114ff319be3130cd9f6af3700fc80@macosforge.org>

#378: Macruby 0.5 allows instantiation of a Module instance
---------------------------------------+------------------------------------
 Reporter:  keith.gautreaux@?          |       Owner:  lsansonetti@?        
     Type:  defect                     |      Status:  new                  
 Priority:  minor                      |   Milestone:  MacRuby 0.5          
Component:  MacRuby                    |    Keywords:                       
---------------------------------------+------------------------------------

Comment(by keith.gautreaux@?):

 Replying to [comment:2 eloy.de.enige@?]:
 > Hey,
 >
 > About writing specs, the rubyspec disallows the use of ?should?. And it
 should be enough to verify that calling #new results in a NoMethodError,
 all the others should then fail as well. Also, if you want specify that an
 exception is raised, you should do so inside a proc. For instance: lambda
 { Fred.new }.should raise_error(NoMethodError). (For more info see the
 rubyspec wiki.)
 >
 > However, the rubyspec is about specifying what actually _does_ work on
 MRI, not about what doesn't. For these cases we have the test_vm test
 suite. In fact there was already a failing test similar to this case.
 Nonetheless I've added an extra failing test, based on your example, in
 r2851.
 >
 > Thanks.

 Thanks very much for the info.  I was unaware of the existing test or the
 rubyspec recommendations.  Sorry, I haven't written any rubyspecs before.
 I appreciate your time.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/378#comment:3>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct 19 16:08:09 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Mon, 19 Oct 2009 23:08:09 -0000
Subject: [MacRuby-devel] [MacRuby] #392: String subclass obj.dup loses
	its class
In-Reply-To: <047.91a220ee842e506177cc588758ee0382@macosforge.org>
References: <047.91a220ee842e506177cc588758ee0382@macosforge.org>
Message-ID: <056.59ad2b0ece0c898e48e7b58723ff6e5e@macosforge.org>

#392: String subclass obj.dup loses its class
------------------------------+---------------------------------------------
 Reporter:  timshadel@?       |        Owner:  lsansonetti@?        
     Type:  defect            |       Status:  closed               
 Priority:  major             |    Milestone:  MacRuby 0.5          
Component:  MacRuby           |   Resolution:  fixed                
 Keywords:  dup string        |  
------------------------------+---------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Thanks for the report, it should be fixed in r2853.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/392#comment:1>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Mon Oct 19 16:36:50 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Mon, 19 Oct 2009 16:36:50 -0700
Subject: [MacRuby-devel] rake spec:ci
In-Reply-To: <7317d7610910180429k35b2448xe4fb761e5dc9f579@mail.gmail.com>
References: <7317d7610910180429k35b2448xe4fb761e5dc9f579@mail.gmail.com>
Message-ID: <3A22DFE8-91E6-41A8-BE11-8FF8CA4490E9@apple.com>

It should now pass, a strange regression was apparently introduced and  
I had to revert the commit. We will investigate the root cause later.

Laurent

On Oct 18, 2009, at 4:29 AM, Conrad Taylor wrote:

> Hi, the 'macrake spec:ci'  is failing using r2848.
>
> BEGIN OUTPUT:
>
> $ macrake spec:ci
> (in /Users/conradwt/macruby.dir/projects/macruby-trunk)
> unknown: warning: already initialized constant MACRUBY_VERSION
> ./mspec/bin/mspec ci -B ./spec/macruby.mspec  :full
> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
> ......2009-10-18 04:25:27.098 macruby[16464:1b07] *** Terminating  
> app due to uncaught exception 'TypeError', reason: '42 is not a  
> symbol'
> *** Call stack at first throw:
> (
> 	0   CoreFoundation                      0x00007fff82a995a4  
> __exceptionPreprocess + 180
> 	1   libobjc.A.dylib                     0x00007fff86ae3313  
> objc_exception_throw + 45
> 	2   libmacruby.dylib                    0x0000000100179285  
> rb_vm_raise + 437
> 	3   libmacruby.dylib                    0x000000010003ff69  
> rb_exc_raise + 9
> 	4   libmacruby.dylib                    0x000000010003e286 rb_raise  
> + 310
> 	5   libmacruby.dylib                    0x00000001000eddc0  
> rb_str_dump + 0
> 	6   libmacruby.dylib                    0x000000010011c6fe  
> rb_queue_get_concurrent + 46
> 	7   libmacruby.dylib                    0x00000001001667cd  
> rb_vm_dispatch + 6269
> 	8   ???                                 0x000000010117ff98 0x0 +  
> 4313317272
> 	9   libmacruby.dylib                    0x00000001001667cd  
> rb_vm_dispatch + 6269
> 	10  ???                                 0x0000000101171e55 0x0 +  
> 4313259605
> 	11  ???                                 0x000000010116d2b5 0x0 +  
> 4313240245
> )
> terminate called after throwing an instance of 'NSException'
> rake aborted!
> Command failed with status (): [./mspec/bin/mspec ci -B ./spec/ 
> macruby.msp...]
>
> END OUTPUT:
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Mon Oct 19 20:20:48 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 20 Oct 2009 03:20:48 -0000
Subject: [MacRuby-devel] [MacRuby] #393: Custom accessors for KVO
In-Reply-To: <051.89bd6963b0603dfaf29f0ac1537860e4@macosforge.org>
References: <051.89bd6963b0603dfaf29f0ac1537860e4@macosforge.org>
Message-ID: <060.ba60d800c780d6b8ad921ae77b9f25a0@macosforge.org>

#393: Custom accessors for KVO
----------------------------------+-----------------------------------------
 Reporter:  paolo.bosetti@?       |       Owner:  lsansonetti@?        
     Type:  defect                |      Status:  new                  
 Priority:  minor                 |   Milestone:  MacRuby 0.5          
Component:  MacRuby               |    Keywords:  KVO                  
----------------------------------+-----------------------------------------

Comment(by lsansonetti@?):

 Reduction:

 {{{
 $ cat t.rb
 framework 'Foundation'
 class Foo
   def setFoo(o)
     @foo = o
   end
 end
 o = Foo.new
 o.addObserver(self, forKeyPath: 'foo', options: 0, context: nil)
 $ ./miniruby t.rb
 2009-10-19 20:19:21.599 miniruby[87617:903] KVO autonotifying only
 supports -set<Key>: methods that return void. Autonotifying will not be
 done for invocations of -[Foo setFoo:].
 }}}

 I guess we should register setXXX methods with a special ObjC runtime
 signature automatically (like what attr_writer / attr_accessor do by
 default).

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/393#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct 19 20:29:38 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 20 Oct 2009 03:29:38 -0000
Subject: [MacRuby-devel] [MacRuby] #393: Custom accessors for KVO
In-Reply-To: <051.89bd6963b0603dfaf29f0ac1537860e4@macosforge.org>
References: <051.89bd6963b0603dfaf29f0ac1537860e4@macosforge.org>
Message-ID: <060.5d932226ec03dcee2d0a553413933ec4@macosforge.org>

#393: Custom accessors for KVO
----------------------------------+-----------------------------------------
 Reporter:  paolo.bosetti@?       |        Owner:  lsansonetti@?        
     Type:  defect                |       Status:  closed               
 Priority:  minor                 |    Milestone:  MacRuby 0.5          
Component:  MacRuby               |   Resolution:  fixed                
 Keywords:  KVO                   |  
----------------------------------+-----------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Should be fixed in r2863.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/393#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct 19 21:39:24 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 20 Oct 2009 04:39:24 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
Message-ID: <057.8127548916ae27a983e4ab9ea2d7aa36@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  blocker            |   Milestone:                       
Component:  MacRuby            |    Keywords:                       
-------------------------------+--------------------------------------------

Comment(by lsansonetti@?):

 Could you provide a test case or a small Xcode project that reproduces
 this problem? We have specs testing NSRange and they all pass.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct 19 22:55:00 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 20 Oct 2009 05:55:00 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
Message-ID: <057.ef449f11ce5771a89441a4d6e0cdce60@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  blocker            |   Milestone:                       
Component:  MacRuby            |    Keywords:                       
-------------------------------+--------------------------------------------

Comment(by cwdinfo@?):

 Replying to [comment:1 lsansonetti@?]:
 > Could you provide a test case or a small Xcode project that reproduces
 this problem? We have specs testing NSRange and they all pass.

 I added a small Xcode project that produces the exception on my machine.
 This is a fresh machine (just wiped and installed Snowy 2 days ago) so I
 don't think it's had a chance to get any bad habits ... yet :)

 To repro the bug, build, then type a few characters in the textfield.
 Press ESC to trigger the delegate method. That's when the unrecognized
 runtime type exception occurs.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct 19 23:41:51 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 20 Oct 2009 06:41:51 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
Message-ID: <057.db369e884f0297b367d1f44de54e243f@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  blocker            |   Milestone:                       
Component:  MacRuby            |    Keywords:                       
-------------------------------+--------------------------------------------

Comment(by lsansonetti@?):

 Thanks for the example. Looks like the exception is being raised inside
 the method resolver.

 {{{
 (gdb) bt
 #0  rb_exc_raise (mesg=8592694976) at eval.c:312
 #1  0x000000010003df86 in rb_raise (exc=8590153248, fmt=<value temporarily
 unavailable, due to optimizations>) at error.c:1120
 #2  0x00000001001321fd in RoxorCompiler::convert_type (this=0x103800800,
 type=0x7fff5fbfdd00 "{_NSRange=II}") at compiler.cpp:6575
 #3  0x000000010014ee5c in RoxorCompiler::compile_objc_stub
 (this=0x103800800, ruby_func=0x10140f060, ruby_imp=0x101100b00,
 arity=@0x104ab8fa8, types=<value temporarily unavailable, due to
 optimizations>) at compiler.cpp:6800
 #4  0x000000010017dbd8 in RoxorCore::resolve_method (this=0x102054200,
 klass=0x200225520, sel=0x7fff83f48988, func=0x10140f060,
 arity=@0x104ab8fa8, flags=0, imp=0x101100b00, m=0x0) at vm.cpp:1569
 #5  0x000000010017e62b in RoxorCore::resolve_methods (this=0x102054200,
 map=0x104ab9020, klass=0x200225520, sel=0x7fff83f48988) at vm.cpp:1610
 #6  0x000000010017ef67 in rb_vm_resolve_method (klass=0x200225520,
 sel=0x7fff83f48988) at vm.cpp:1658
 #7  0x000000010017ef8c in resolveInstanceMethod_imp (self=<value
 temporarily unavailable, due to optimizations>, sel=<value temporarily
 unavailable, due to optimizations>, name=<value temporarily unavailable,
 due to optimizations>) at vm.cpp:4102
 #8  0x00007fff88a18b57 in _class_resolveMethod ()
 #9  0x00007fff88a1e199 in lookUpMethod ()
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:3>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct 19 23:48:49 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 20 Oct 2009 06:48:49 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
Message-ID: <057.c20def0c60189889b82d2ea3bd1a02fd@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  blocker            |   Milestone:                       
Component:  MacRuby            |    Keywords:                       
-------------------------------+--------------------------------------------

Comment(by lsansonetti@?):

 It's a bug in BridgeSupport, this informal protocol method doesn't contain
 64-bit annotations.

 {{{
 <method type='@32 at 0:4 at 8@12 at 16{_NSRange=II}20^i28'
 selector='control:textView:completions:forPartialWordRange:indexOfSelectedItem:'/>
 }}}

 In 64-bit, NSRange fields are QQ, not II.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:4>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 20 00:00:56 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 20 Oct 2009 07:00:56 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
Message-ID: <057.798c7a574380fb5c1f0df1275c849e76@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:                     |  
-------------------------------+--------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Committed temporary workaround in r2865. Thanks for the report.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:5>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 20 07:33:53 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 20 Oct 2009 14:33:53 -0000
Subject: [MacRuby-devel] [MacRuby] #395: String#% does not work with %p
Message-ID: <045.3e8ec4fce5c76768e096f48d1069caae@macosforge.org>

#395: String#% does not work with %p
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |       Owner:  lsansonetti@?        
     Type:  defect          |      Status:  new                  
 Priority:  major           |   Milestone:  MacRuby 0.5          
Component:  MacRuby         |    Keywords:                       
----------------------------+-----------------------------------------------
 {{{
 macruby -e 'p "%p" % "foo"'
 }}}

 results in

 {{{
 core:in `%:': expected instance of Pointer, got `"foo"' (NSMutableString)
 (TypeError)
         from -e:1:in `<main>'
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/395>
MacRuby <http://macruby.org/>


From eloy.de.enige at gmail.com  Tue Oct 20 09:52:36 2009
From: eloy.de.enige at gmail.com (Eloy Duran)
Date: Tue, 20 Oct 2009 18:52:36 +0200
Subject: [MacRuby-devel] MacRuby 0.5 beta 1
In-Reply-To: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
References: <A7CBA0B3-DE04-4097-9997-CD6302EAA67C@apple.com>
Message-ID: <f52746ff0910200952id4cbbc6gaa7acb768c58ee38@mail.gmail.com>

Laurent,

as they say in french; congratulations on le grande effort! \m/

Eloy

On Thursday, October 8, 2009, Laurent Sansonetti <lsansonetti at apple.com> wrote:
> Hi,
>
> The first beta release of MacRuby 0.5 is out! I prepared some notes here:
>
> http://www.macruby.org/blog/2009/10/07/macruby05b1.html
>
> The goal is to go through a few beta releases before releasing the final 0.5.
>
> Please give it a try and report us bugs & feedback :)
>
> Laurent
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>

From johnmacshea at gmail.com  Tue Oct 20 10:11:39 2009
From: johnmacshea at gmail.com (John Shea)
Date: Tue, 20 Oct 2009 19:11:39 +0200
Subject: [MacRuby-devel] tentative first steps with GCD in macruby
Message-ID: <96AF515A-EE3E-41A2-8C6A-358E6BAAE67B@gmail.com>

Dear All,

(sorry for the long post)

I have been experimenting a bit with GCD in MacRuby 0.5 beta.

I have managed to get some code working as I would expect it to work,  
and I am wondering if a few of you could provide a sanity check that  
everything i am doing is above board and not the result of unspecified  
behaviour.

My main concern is that when running a set of tasks and collecting the  
results that the collecting itself is not thread safe (in this case  
the << operator). And if it is not thread safe - then what is the best  
way to collect results from dispatched tasks.

But so far it seems to work magically well.

Before I put the code down - here are some initial discoveries  (which  
may have been obvious to everyone else).

1. When running tests you need wait until the threads are finished -  
otherwise the main loop will finish before the output comes back from  
other threads.
I did that with a sleep, but also experimented with looping until an  
array is filled.

2. Scope: Given one of the global system queues : 		
gcdq = Dispatch::Queue.concurrent(:default)

and looping over a number of dispatches:
5.times do |index|
	gcdq.dispatch {puts index}
end
the task dispatched will hold the last value of index - it will not  
capture the changing value of index - I assume that the task has a  
pointer directly to the index variable.
(an article by Bill Bumgarner http://www.friday.com/bbum/2009/08/29/blocks-tips-tricks/ 
  pointed out something similar in objC - but had a different way of  
solving this)

So to capture that changing index,  I created a Proc then turned it  
back to a block, eg:
5.times do |index|
	task = Proc.new {puts index}
	gcdq.dispatch &task
end

3. You will notice that in the code below in check = a.run-disp2 that  
the array is returned - I assume empty - and is gradually filled by  
the tasks.

class A
   def run_disp(an_array)
     gcdq = Dispatch::Queue.concurrent(:default)
     ["f","g","h","i", "j"].each_with_index do |val, index|
        task = Proc.new {an_array  << do_something(val, index)}
        gcdq.dispatch &task
       puts "Loaded #{index}"
     end
   end

   def run_disp2
     an_array = []
     gcdq = Dispatch::Queue.concurrent(:default)
     ["f","g","h","i", "j"].each_with_index do |val, index|
        task = Proc.new {an_array  << do_something(val, index)}
        gcdq.dispatch &task
       puts "Loaded #{index}"
     end
     an_array
   end

   def do_something(val, index)
     #staggered sleeps so as to prove that various tasks finish first
     result = val * (index + 1)
     case index
     when 0, 1
       sleep 2
     when 2
       sleep 1
     else
       sleep 0
     end
     puts "yeah baby! #{index}"
     result
   end
end

a = A.new
#pass array to be filled
an_array = []
a.run_disp(an_array)
sleep 10
puts "passed array: #{an_array.join(", ")}"

check = a.run_disp2
sleep 10
puts "returned array: #{check.join(", ")}"

#results:
#     Loaded 0
#     Loaded 1
#     Loaded 2
#     Loaded 3
#     Loaded 4
#     yeah baby! 4yeah baby! 3
#
#     yeah baby! 2
#     yeah baby! 1
#     yeah baby! 0
#     passed array: iiii, jjjjj, hhh, gg, f
#     Loaded 0
#     Loaded 1
#     Loaded 2
#     Loaded 3
#     Loaded 4
#     yeah baby! 3
#     yeah baby! 4
#     yeah baby! 2
#     yeah baby! 0
#     yeah baby! 1
#     returned array: iiii, jjjjj, hhh, f, gg

#assume puts is not transactional.


thanks in advance for any comments / corrections,
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091020/73d586f2/attachment-0001.html>

From ruby-noreply at macosforge.org  Tue Oct 20 12:31:56 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 20 Oct 2009 19:31:56 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
Message-ID: <057.3f2cb2299e90b712d4d4f822a0781a22@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:                     |  
-------------------------------+--------------------------------------------

Comment(by cwdinfo@?):

 There is a new problem with this. I'm attaching a new file. The range
 passed in is bad. Build, run, type some characters, press esc. The numbers
 reported for length and location are wrong.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:6>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 20 12:44:36 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 20 Oct 2009 19:44:36 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
Message-ID: <057.f95703ab42c0be4050c3e9225c01f4b1@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  reopened             
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:                       
 Keywords:                     |  
-------------------------------+--------------------------------------------
Changes (by lsansonetti@?):

  * status:  closed => reopened
  * resolution:  fixed =>


Comment:

 You're right, reopening.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:7>
MacRuby <http://macruby.org/>


From jazzbox at 7zz.de  Wed Oct 21 08:16:22 2009
From: jazzbox at 7zz.de (B. Ohr)
Date: Wed, 21 Oct 2009 17:16:22 +0200
Subject: [MacRuby-devel] macgem with mixed-in ObjC
Message-ID: <F680B8D2-E98C-4528-8F26-DB73999786D8@7zz.de>

Hi,

what do you think about a macgem with mixed-in ObjC?

This could be useful for supporting native C libraries without using  
the MRI C interface, for calling parts of the OS X framework that is  
not Obj-C, for speed optimized code and so on.....

A macgem could also be delivered with a precompiled .rbo, so it can  
easily be installed on machines without the Developer tools installed.  
(I haven't yet tried to run macruby on such a machine ;-) )

BTW, I failed in building an .rbo bundle with a mixed-in ObjC part.

Pure Ruby like this

macrubyc --arch x86_64 -C "foo.rb" -o "output/foo.rbo"

is working, but I didn't find a way to include another .o file  
generated by gcc.

Bernd



From ruby-noreply at macosforge.org  Wed Oct 21 16:24:45 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 21 Oct 2009 23:24:45 -0000
Subject: [MacRuby-devel] [MacRuby] #396: open method from open-uri not
	working in macruby 0.5
Message-ID: <047.ac388a7d40b0cef40c9fcaff3a58ae82@macosforge.org>

#396: open method from open-uri not working in macruby 0.5
------------------------------+---------------------------------------------
 Reporter:  dmlary@?          |       Owner:  lsansonetti@?        
     Type:  defect            |      Status:  new                  
 Priority:  minor             |   Milestone:  MacRuby 0.5          
Component:  MacRuby           |    Keywords:  open-uri, openuri    
------------------------------+---------------------------------------------
 ~> macruby --version
 MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]

 ~> macruby -r 'open-uri' -e 'open "http://www.google.com"'
 core:in `open:': No such file or directory - open() failed (Errno::ENOENT)
         from -e:1:in `<main>'

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/396>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Wed Oct 21 18:02:00 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Wed, 21 Oct 2009 18:02:00 -0700
Subject: [MacRuby-devel] tentative first steps with GCD in macruby
In-Reply-To: <96AF515A-EE3E-41A2-8C6A-358E6BAAE67B@gmail.com>
References: <96AF515A-EE3E-41A2-8C6A-358E6BAAE67B@gmail.com>
Message-ID: <8A50FB05-616C-4390-B6B7-1F9CFE5B6074@apple.com>

Hi John,

On Oct 20, 2009, at 10:11 AM, John Shea wrote:

> Dear All,
>
> (sorry for the long post)
>
> I have been experimenting a bit with GCD in MacRuby 0.5 beta.

Cool!

> I have managed to get some code working as I would expect it to  
> work, and I am wondering if a few of you could provide a sanity  
> check that everything i am doing is above board and not the result  
> of unspecified behaviour.
>
> My main concern is that when running a set of tasks and collecting  
> the results that the collecting itself is not thread safe (in this  
> case the << operator). And if it is not thread safe - then what is  
> the best way to collect results from dispatched tasks.

Yes, appending objects to an array from multiple threads is definitely  
not going to work as you would expect.

Typically, you would use a Mutex object to synchronize access to the  
shared variable, but in the GCD world the most common way I believe is  
to use a sequential queue.

ary = []
ary_queue = Queue.new('com.apple.ary')

100.times do
   Queue.concurrent.dispatch do
       n = heavy_compute
       ary_queue.dispatch { ary << n }
   end
end

This way, the heavy_compute code is executed in parallel and appending  
the result to ary is done sequentially.

> But so far it seems to work magically well.
>
> Before I put the code down - here are some initial discoveries   
> (which may have been obvious to everyone else).
>
> 1. When running tests you need wait until the threads are finished -  
> otherwise the main loop will finish before the output comes back  
> from other threads.
> I did that with a sleep, but also experimented with looping until an  
> array is filled.

In case you do asynchronous dispatch calls to a sequential queue (that  
you created yourself), doing a synchronous call passing an empty block  
will block until asynchronous blocks are completed.

q = Queue.new('com.apple.ary')
100.times { q.dispatch { heavy_compute } }
q.dispatch(true) {} # wait

In case you use the concurrent queue, AFAIK the only way to wait is to  
use a Group.

g = Dispatch::Group.new
100.times { g.dispatch(Dispatch::Queue.concurrent) { heavy_compute } }
g.wait

> 2. Scope: Given one of the global system queues : 		
> gcdq = Dispatch::Queue.concurrent(:default)
>
> and looping over a number of dispatches:
> 5.times do |index|
> 	gcdq.dispatch {puts index}
> end
> the task dispatched will hold the last value of index - it will not  
> capture the changing value of index - I assume that the task has a  
> pointer directly to the index variable.
> (an article by Bill Bumgarner http://www.friday.com/bbum/2009/08/29/blocks-tips-tricks/ 
>  pointed out something similar in objC - but had a different way of  
> solving this)
>
> So to capture that changing index,  I created a Proc then turned it  
> back to a block, eg:
> 5.times do |index|
> 	task = Proc.new {puts index}
> 	gcdq.dispatch &task
> end

Good catch, it's actually a problem that needs to be solved. It also  
reproduces with normal Thread objects:

100.times { |i| Thread.new { p i } }

The current workaround for Thread is to pass the variables to #new.

100.times { |i| Thread.new(i) { |i| p i } }

For GCD, I think your idea is the best.

I have been considering a few ways to solve this problem, a naive one  
would be to copy the dynamic variables upon the block preparation if  
the compiler gives us enough hints.

> 3. You will notice that in the code below in check = a.run-disp2  
> that the array is returned - I assume empty - and is gradually  
> filled by the tasks.
>
> class A
>   def run_disp(an_array)
>     gcdq = Dispatch::Queue.concurrent(:default)
>     ["f","g","h","i", "j"].each_with_index do |val, index|
>        task = Proc.new {an_array  << do_something(val, index)}
>        gcdq.dispatch &task
>       puts "Loaded #{index}"
>     end
>   end
>
>   def run_disp2
>     an_array = []
>     gcdq = Dispatch::Queue.concurrent(:default)
>     ["f","g","h","i", "j"].each_with_index do |val, index|
>        task = Proc.new {an_array  << do_something(val, index)}
>        gcdq.dispatch &task
>       puts "Loaded #{index}"
>     end
>     an_array
>   end
>
>   def do_something(val, index)
>     #staggered sleeps so as to prove that various tasks finish first
>     result = val * (index + 1)
>     case index
>     when 0, 1
>       sleep 2
>     when 2
>       sleep 1
>     else
>       sleep 0
>     end
>     puts "yeah baby! #{index}"
>     result
>   end
> end
>
> a = A.new
> #pass array to be filled
> an_array = []
> a.run_disp(an_array)
> sleep 10
> puts "passed array: #{an_array.join(", ")}"
>
> check = a.run_disp2
> sleep 10
> puts "returned array: #{check.join(", ")}"
>
> #results:
> #     Loaded 0
> #     Loaded 1
> #     Loaded 2
> #     Loaded 3
> #     Loaded 4
> #     yeah baby! 4yeah baby! 3
> #
> #     yeah baby! 2
> #     yeah baby! 1
> #     yeah baby! 0
> #     passed array: iiii, jjjjj, hhh, gg, f
> #     Loaded 0
> #     Loaded 1
> #     Loaded 2
> #     Loaded 3
> #     Loaded 4
> #     yeah baby! 3
> #     yeah baby! 4
> #     yeah baby! 2
> #     yeah baby! 0
> #     yeah baby! 1
> #     returned array: iiii, jjjjj, hhh, f, gg
>
> #assume puts is not transactional.

I think you definitely want to synchronize the array access (using a  
sequential queue).

As for #puts & IO friends, definitely :)

Thanks for trying it out. Would you be interested to share your  
experiments later, in a website article?

Laurent

From ruby-noreply at macosforge.org  Wed Oct 21 20:06:39 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 22 Oct 2009 03:06:39 -0000
Subject: [MacRuby-devel] [MacRuby] #396: open method from open-uri not
 working in macruby 0.5
In-Reply-To: <047.ac388a7d40b0cef40c9fcaff3a58ae82@macosforge.org>
References: <047.ac388a7d40b0cef40c9fcaff3a58ae82@macosforge.org>
Message-ID: <056.037b017b1f69cfeff5f71f11947f2694@macosforge.org>

#396: open method from open-uri not working in macruby 0.5
------------------------------+---------------------------------------------
 Reporter:  dmlary@?          |       Owner:  lsansonetti@?        
     Type:  defect            |      Status:  new                  
 Priority:  minor             |   Milestone:  MacRuby 0.5          
Component:  MacRuby           |    Keywords:  open-uri, openuri    
------------------------------+---------------------------------------------

Comment(by lsansonetti@?):

 Looks like open-uri.rb is unable to replace Kernel#open, I suspect a bug
 of #module_function.

 In the interim, calling the open-uri stuff manually seems to work.

 {{{
 $ macruby -r open-uri -e "p URI.parse('http://google.com').open.read(42)"
 "<!doctype html><html><head><meta http-equi"
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/396#comment:1>
MacRuby <http://macruby.org/>


From johnmacshea at gmail.com  Wed Oct 21 22:08:37 2009
From: johnmacshea at gmail.com (John Shea)
Date: Thu, 22 Oct 2009 07:08:37 +0200
Subject: [MacRuby-devel] tentative first steps with GCD in macruby
In-Reply-To: <8A50FB05-616C-4390-B6B7-1F9CFE5B6074@apple.com>
References: <96AF515A-EE3E-41A2-8C6A-358E6BAAE67B@gmail.com>
	<8A50FB05-616C-4390-B6B7-1F9CFE5B6074@apple.com>
Message-ID: <C9F673F1-3328-497C-849C-4C366EC31B36@gmail.com>

Hi Lareunt,

thanks very much for the reply, and the corrections.

> Thanks for trying it out. Would you be interested to share your  
> experiments later, in a website article?
Yep, sure -   I have some real world number crunching to try it on,  
and a number of machines with different numbers of cores - so it  
should be interesting.

Cheers,
John

On Oct 22, 2009, at 3:02 AM, Laurent Sansonetti wrote:

> Hi John,
>
> On Oct 20, 2009, at 10:11 AM, John Shea wrote:
>
>> Dear All,
>>
>> (sorry for the long post)
>>
>> I have been experimenting a bit with GCD in MacRuby 0.5 beta.
>
> Cool!
>
>> I have managed to get some code working as I would expect it to  
>> work, and I am wondering if a few of you could provide a sanity  
>> check that everything i am doing is above board and not the result  
>> of unspecified behaviour.
>>
>> My main concern is that when running a set of tasks and collecting  
>> the results that the collecting itself is not thread safe (in this  
>> case the << operator). And if it is not thread safe - then what is  
>> the best way to collect results from dispatched tasks.
>
> Yes, appending objects to an array from multiple threads is  
> definitely not going to work as you would expect.
>
> Typically, you would use a Mutex object to synchronize access to the  
> shared variable, but in the GCD world the most common way I believe  
> is to use a sequential queue.
>
> ary = []
> ary_queue = Queue.new('com.apple.ary')
>
> 100.times do
>  Queue.concurrent.dispatch do
>      n = heavy_compute
>      ary_queue.dispatch { ary << n }
>  end
> end
>
> This way, the heavy_compute code is executed in parallel and  
> appending the result to ary is done sequentially.
>
>> But so far it seems to work magically well.
>>
>> Before I put the code down - here are some initial discoveries   
>> (which may have been obvious to everyone else).
>>
>> 1. When running tests you need wait until the threads are finished  
>> - otherwise the main loop will finish before the output comes back  
>> from other threads.
>> I did that with a sleep, but also experimented with looping until  
>> an array is filled.
>
> In case you do asynchronous dispatch calls to a sequential queue  
> (that you created yourself), doing a synchronous call passing an  
> empty block will block until asynchronous blocks are completed.
>
> q = Queue.new('com.apple.ary')
> 100.times { q.dispatch { heavy_compute } }
> q.dispatch(true) {} # wait
>
> In case you use the concurrent queue, AFAIK the only way to wait is  
> to use a Group.
>
> g = Dispatch::Group.new
> 100.times { g.dispatch(Dispatch::Queue.concurrent) { heavy_compute } }
> g.wait
>
>> 2. Scope: Given one of the global system queues : 		
>> gcdq = Dispatch::Queue.concurrent(:default)
>>
>> and looping over a number of dispatches:
>> 5.times do |index|
>> 	gcdq.dispatch {puts index}
>> end
>> the task dispatched will hold the last value of index - it will not  
>> capture the changing value of index - I assume that the task has a  
>> pointer directly to the index variable.
>> (an article by Bill Bumgarner http://www.friday.com/bbum/2009/08/29/blocks-tips-tricks/ 
>>  pointed out something similar in objC - but had a different way of  
>> solving this)
>>
>> So to capture that changing index,  I created a Proc then turned it  
>> back to a block, eg:
>> 5.times do |index|
>> 	task = Proc.new {puts index}
>> 	gcdq.dispatch &task
>> end
>
> Good catch, it's actually a problem that needs to be solved. It also  
> reproduces with normal Thread objects:
>
> 100.times { |i| Thread.new { p i } }
>
> The current workaround for Thread is to pass the variables to #new.
>
> 100.times { |i| Thread.new(i) { |i| p i } }
>
> For GCD, I think your idea is the best.
>
> I have been considering a few ways to solve this problem, a naive  
> one would be to copy the dynamic variables upon the block  
> preparation if the compiler gives us enough hints.
>
>> 3. You will notice that in the code below in check = a.run-disp2  
>> that the array is returned - I assume empty - and is gradually  
>> filled by the tasks.
>>
>> class A
>>  def run_disp(an_array)
>>    gcdq = Dispatch::Queue.concurrent(:default)
>>    ["f","g","h","i", "j"].each_with_index do |val, index|
>>       task = Proc.new {an_array  << do_something(val, index)}
>>       gcdq.dispatch &task
>>      puts "Loaded #{index}"
>>    end
>>  end
>>
>>  def run_disp2
>>    an_array = []
>>    gcdq = Dispatch::Queue.concurrent(:default)
>>    ["f","g","h","i", "j"].each_with_index do |val, index|
>>       task = Proc.new {an_array  << do_something(val, index)}
>>       gcdq.dispatch &task
>>      puts "Loaded #{index}"
>>    end
>>    an_array
>>  end
>>
>>  def do_something(val, index)
>>    #staggered sleeps so as to prove that various tasks finish first
>>    result = val * (index + 1)
>>    case index
>>    when 0, 1
>>      sleep 2
>>    when 2
>>      sleep 1
>>    else
>>      sleep 0
>>    end
>>    puts "yeah baby! #{index}"
>>    result
>>  end
>> end
>>
>> a = A.new
>> #pass array to be filled
>> an_array = []
>> a.run_disp(an_array)
>> sleep 10
>> puts "passed array: #{an_array.join(", ")}"
>>
>> check = a.run_disp2
>> sleep 10
>> puts "returned array: #{check.join(", ")}"
>>
>> #results:
>> #     Loaded 0
>> #     Loaded 1
>> #     Loaded 2
>> #     Loaded 3
>> #     Loaded 4
>> #     yeah baby! 4yeah baby! 3
>> #
>> #     yeah baby! 2
>> #     yeah baby! 1
>> #     yeah baby! 0
>> #     passed array: iiii, jjjjj, hhh, gg, f
>> #     Loaded 0
>> #     Loaded 1
>> #     Loaded 2
>> #     Loaded 3
>> #     Loaded 4
>> #     yeah baby! 3
>> #     yeah baby! 4
>> #     yeah baby! 2
>> #     yeah baby! 0
>> #     yeah baby! 1
>> #     returned array: iiii, jjjjj, hhh, f, gg
>>
>> #assume puts is not transactional.
>
> I think you definitely want to synchronize the array access (using a  
> sequential queue).
>
> As for #puts & IO friends, definitely :)
>
> Thanks for trying it out. Would you be interested to share your  
> experiments later, in a website article?
>
> Laurent
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Thu Oct 22 01:14:49 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 22 Oct 2009 08:14:49 -0000
Subject: [MacRuby-devel] [MacRuby] #397: erb string buffer corruption
Message-ID: <045.1e70cba81348117f4b7384267b898dee@macosforge.org>

#397: erb string buffer corruption
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |       Owner:  lsansonetti@?        
     Type:  defect          |      Status:  new                  
 Priority:  critical        |   Milestone:  MacRuby 0.5          
Component:  MacRuby         |    Keywords:                       
----------------------------+-----------------------------------------------
 {{{
 $ macruby -r 'erb' -e 'p ERB.new("1234567").result'
 }}}

 results in

 {{{
 core:in `eval:': (erb):1: syntax error, unexpected tIDENTIFIER, expecting
 $end
 ...''; _erbout.concat "1234567"?        ; _erbout.force_encoding(__EN...
 ...                              ^ (SyntaxError)
         from core:in `result'
 }}}

 As you can see the erb string is corrupted  with the '?'.

 This errror looks like Ticket #311 which is closed but still not working!

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/397>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 22 20:06:30 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 23 Oct 2009 03:06:30 -0000
Subject: [MacRuby-devel] [MacRuby] #398: Trouble loading gem
Message-ID: <056.b91449423d8f7303e3adc3be774b05b3@macosforge.org>

#398: Trouble loading gem
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?               
     Type:  defect                     |      Status:  new                         
 Priority:  blocker                    |   Milestone:  MacRuby 0.5                 
Component:  MacRuby                    |    Keywords:  gems, macruby, load, defined
---------------------------------------+------------------------------------
 Trying to load the Grit gem by using

 {{{
 require 'rubygems'
 require 'grit'
 include Grit
 }}}

 and I get

 '''unrecognized defined? arg: 21 (NODE_AND)'''

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/398>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 22 20:18:38 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 23 Oct 2009 03:18:38 -0000
Subject: [MacRuby-devel] [MacRuby] #398: Trouble loading gem
In-Reply-To: <056.b91449423d8f7303e3adc3be774b05b3@macosforge.org>
References: <056.b91449423d8f7303e3adc3be774b05b3@macosforge.org>
Message-ID: <065.4ceb5e4ea11e66b13387c73bc7e6e079@macosforge.org>

#398: Trouble loading gem
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?               
     Type:  defect                     |      Status:  new                         
 Priority:  blocker                    |   Milestone:  MacRuby 0.5                 
Component:  MacRuby                    |    Keywords:  gems, macruby, load, defined
---------------------------------------+------------------------------------

Comment(by conradwt@?):

 You shouldn't have to `require 'rubygems'` in Ruby 1.9.1 or greater.
 Thus, you might want to try the following:

 {{{

 require 'grit'
 include Grit'

 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/398#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 22 20:31:14 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 23 Oct 2009 03:31:14 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
Message-ID: <057.842ac53c1c40a9daeb9589d2b6606053@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  reopened             
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:                       
 Keywords:                     |  
-------------------------------+--------------------------------------------

Comment(by lsansonetti@?):

 Looks like yet another ABI issue. llvm-gcc compiles the code as:

 {{{
 define internal %struct.Foo* @"\01-[Foo
 control:textView:completions:forPartialWordRange:indexOfSelectedItem:]"(%struct.Foo*
 %self, %struct.objc_selector* %_cmd, %struct.NSControl* %control,
 %struct.NSTextView* %textView, %struct.Foo* %words, %struct.NSRange* byval
 %charRange, i64* %index) ssp {
 }}}

 In this case, the NSRange structure should be passed 'byval'. MacRuby
 doesn't (since sizeof(NSRange) is <= 128bit) but in this case the number
 of arguments seem to trigger something.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:8>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 22 20:38:17 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 23 Oct 2009 03:38:17 -0000
Subject: [MacRuby-devel] [MacRuby] #398: Trouble loading gem
In-Reply-To: <056.b91449423d8f7303e3adc3be774b05b3@macosforge.org>
References: <056.b91449423d8f7303e3adc3be774b05b3@macosforge.org>
Message-ID: <065.7b413e60ff42dbde5160c30ca930482b@macosforge.org>

#398: Trouble loading gem
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?               
     Type:  defect                     |      Status:  new                         
 Priority:  blocker                    |   Milestone:  MacRuby 0.5                 
Component:  MacRuby                    |    Keywords:  gems, macruby, load, defined
---------------------------------------+------------------------------------

Comment(by lsansonetti@?):

 Conrad, this looks like a bug in the compiler, it's unrelated to your
 comment.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/398#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 22 22:08:05 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 23 Oct 2009 05:08:05 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
Message-ID: <057.aae699f0ed45416d9e2ad46ebcaa188c@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  reopened             
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:                       
 Keywords:                     |  
-------------------------------+--------------------------------------------

Comment(by lsansonetti@?):

 Page 21 of the x86_64 ABI (http://www.x86-64.org/documentation/abi.pdf)
 says:

 {{{
 If there are no registers available for any eightbyte of an argument, the
 whole argument is passed on the stack. If registers have already been
 assigned for some eightbytes of such an argument, the assignments get
 reverted.
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:9>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 23 00:54:19 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 23 Oct 2009 07:54:19 -0000
Subject: [MacRuby-devel] [MacRuby] #398: Trouble loading gem
In-Reply-To: <056.b91449423d8f7303e3adc3be774b05b3@macosforge.org>
References: <056.b91449423d8f7303e3adc3be774b05b3@macosforge.org>
Message-ID: <065.c77cc1f3922098d49e4a18662ab08147@macosforge.org>

#398: Trouble loading gem
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?               
     Type:  defect                     |      Status:  new                         
 Priority:  blocker                    |   Milestone:  MacRuby 0.5                 
Component:  MacRuby                    |    Keywords:  gems, macruby, load, defined
---------------------------------------+------------------------------------

Comment(by eloy.de.enige@?):

 See this discussion from sept. 17th for more info:
 http://lists.macosforge.org/pipermail/macruby-
 devel/2009-September/002511.html

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/398#comment:3>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 23 08:11:02 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 23 Oct 2009 15:11:02 -0000
Subject: [MacRuby-devel] [MacRuby] #398: Trouble loading gem
In-Reply-To: <056.b91449423d8f7303e3adc3be774b05b3@macosforge.org>
References: <056.b91449423d8f7303e3adc3be774b05b3@macosforge.org>
Message-ID: <065.de582ad33df9fe19f4733b6654b0da5a@macosforge.org>

#398: Trouble loading gem
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?               
     Type:  defect                     |      Status:  new                         
 Priority:  blocker                    |   Milestone:  MacRuby 0.5                 
Component:  MacRuby                    |    Keywords:  gems, macruby, load, defined
---------------------------------------+------------------------------------

Comment(by hungerandthirst@?):

 Does the case formatting change in the discussion listed serve as a viable
 workaround for this issue until the compiler is fixed?

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/398#comment:4>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 23 11:10:57 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 23 Oct 2009 18:10:57 -0000
Subject: [MacRuby-devel] [MacRuby] #399: Building MacRuby HEAD with llvm
 trunk r82747 fails at dispatcher.cpp
Message-ID: <052.da365ab90dc5b5f7c6799bbe9d95110c@macosforge.org>

#399: Building MacRuby HEAD with llvm trunk r82747 fails at dispatcher.cpp
-----------------------------------+----------------------------------------
 Reporter:  nagachika00@?          |       Owner:  lsansonetti@?        
     Type:  defect                 |      Status:  new                  
 Priority:  major                  |   Milestone:                       
Component:  MacRuby                |    Keywords:                       
-----------------------------------+----------------------------------------
 Hi all. I was try to re-build MacRuby HEAD with llvm trunk r82747 on Mac
 OS X 10.6.1 and it fails at compiling dispatcher.cpp.
 With environment variable allow_build_warnings=1, the warnings are ignored
 and I could get macruby executable, but isn't there any problems?

 When I try to build macruby at Oct. 1, it success without
 allow_build_warnings=1.

 My command-lines are as follows.
 {{{
 (for llvm)
 $ svn up -r 82747 llvm-trunk
 $ cd llvm-trunk
 $ ./configure --prefix=~/opt/llvm
 $ UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64" ENABLE_OPTIMIZED=1 make -j2
 $ UNIVERSAL=1 UNIVERSAL_ARCH="i386 x86_64" ENABLE_OPTIMIZED=1 make install
 }}}
 {{{
 $ cd MacRuby-0.5
 $ git pull
 $ git log -1
 commit 323fd75841aa672659e87feb577c6cc93fd085eb
 Author: lsansonetti at apple.com <lsansonetti at apple.com@23306eb0-4c56-4727
 -a40e-e92c0eb68959>
 Date:   Fri Oct 23 00:59:10 2009 +0000

     unrelease parser nodes post execution

     git-svn-id:
 http://svn.macosforge.org/repository/ruby/MacRuby/trunk at 2886
 23306eb0-4c56-4727-a40e-e92c0eb68959
 $ rake clean
 $ rake
 :
 /usr/bin/g++ -I/Users/nagachika/opt/llvm/include  -D_DEBUG -D_GNU_SOURCE
 -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -O3  -fno-common
 -Woverloaded-virtual -I. -I./include -g -Wall -arch i386 -arch x86_64
 -Wno-parentheses -Wno-deprecated-declarations -Werror -Winline --param
 inline-unit-growth=10000 --param large-function-growth=10000 -x
 objective-c++ -c dispatcher.cpp -o dispatcher.o
 cc1objplus: warnings being treated as errors
 In file included from
 /Users/nagachika/opt/llvm/include/llvm/Metadata.h:20,
                  from /Users/nagachika/opt/llvm/include/llvm/Module.h:21,
                  from llvm.h:7,
                  from dispatcher.cpp:9:
 /Users/nagachika/opt/llvm/include/llvm/Type.h:417: warning: ?void
 llvm::PATypeHandle::addUser()? was used before it was declared inline
 /Users/nagachika/opt/llvm/include/llvm/AbstractTypeUser.h:95: warning:
 previous non-inline declaration here
 /Users/nagachika/opt/llvm/include/llvm/Type.h:422: warning: ?void
 llvm::PATypeHandle::removeUser()? was used before it was declared inline
 /Users/nagachika/opt/llvm/include/llvm/AbstractTypeUser.h:96: warning:
 previous non-inline declaration here
 /Users/nagachika/opt/llvm/include/llvm/Type.h:434: warning: ?llvm::Type*
 llvm::PATypeHolder::get() const? was used before it was declared inline
 /Users/nagachika/opt/llvm/include/llvm/AbstractTypeUser.h:159: warning:
 previous non-inline declaration here
 /Users/nagachika/opt/llvm/include/llvm/Type.h:440: warning: ?void
 llvm::PATypeHolder::addRef()? was used before it was declared inline
 /Users/nagachika/opt/llvm/include/llvm/AbstractTypeUser.h:182: warning:
 previous non-inline declaration here
 /Users/nagachika/opt/llvm/include/llvm/Type.h:446: warning: ?void
 llvm::PATypeHolder::dropRef()? was used before it was declared inline
 /Users/nagachika/opt/llvm/include/llvm/AbstractTypeUser.h:183: warning:
 previous non-inline declaration here
 cc1objplus: warnings being treated as errors
 In file included from
 /Users/nagachika/opt/llvm/include/llvm/Metadata.h:20,
                  from /Users/nagachika/opt/llvm/include/llvm/Module.h:21,
                  from llvm.h:7,
                  from dispatcher.cpp:9:
 /Users/nagachika/opt/llvm/include/llvm/Type.h:417: warning: ?void
 llvm::PATypeHandle::addUser()? was used before it was declared inline
 /Users/nagachika/opt/llvm/include/llvm/AbstractTypeUser.h:95: warning:
 previous non-inline declaration here
 /Users/nagachika/opt/llvm/include/llvm/Type.h:422: warning: ?void
 llvm::PATypeHandle::removeUser()? was used before it was declared inline
 /Users/nagachika/opt/llvm/include/llvm/AbstractTypeUser.h:96: warning:
 previous non-inline declaration here
 /Users/nagachika/opt/llvm/include/llvm/Type.h:434: warning: ?llvm::Type*
 llvm::PATypeHolder::get() const? was used before it was declared inline
 /Users/nagachika/opt/llvm/include/llvm/AbstractTypeUser.h:159: warning:
 previous non-inline declaration here
 /Users/nagachika/opt/llvm/include/llvm/Type.h:440: warning: ?void
 llvm::PATypeHolder::addRef()? was used before it was declared inline
 /Users/nagachika/opt/llvm/include/llvm/AbstractTypeUser.h:182: warning:
 previous non-inline declaration here
 /Users/nagachika/opt/llvm/include/llvm/Type.h:446: warning: ?void
 llvm::PATypeHolder::dropRef()? was used before it was declared inline
 /Users/nagachika/opt/llvm/include/llvm/AbstractTypeUser.h:183: warning:
 previous non-inline declaration here
 lipo: can't figure out the architecture type of:
 /var/folders/wg/wgLu2nI8HSa1xstYc+L5Jk+++TI/-Tmp-//ccf0vjOF.out
 rake aborted!
 Command failed with status (1): [/usr/bin/g++
 -I/Users/nagachika/opt/llvm/i...]

 (See full trace by running task with --trace)
 }}}

 Toolchain information is as below.
 {{{
 $ g++ --version
 i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5646)
 Copyright (C) 2007 Free Software Foundation, Inc.
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
 PURPOSE.
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/399>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 23 12:46:05 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 23 Oct 2009 19:46:05 -0000
Subject: [MacRuby-devel] [MacRuby] #398: Trouble loading gem
In-Reply-To: <056.b91449423d8f7303e3adc3be774b05b3@macosforge.org>
References: <056.b91449423d8f7303e3adc3be774b05b3@macosforge.org>
Message-ID: <065.644a6ea97cbe89faa106c687acd8d156@macosforge.org>

#398: Trouble loading gem
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?               
     Type:  defect                     |      Status:  new                         
 Priority:  blocker                    |   Milestone:  MacRuby 0.5                 
Component:  MacRuby                    |    Keywords:  gems, macruby, load, defined
---------------------------------------+------------------------------------

Comment(by lsansonetti@?):

 There is definitely a bug in the compiler, but I think there is a bug in
 the Ruby code too, this defined? expression is probably not doing what
 it's meant to.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/398#comment:5>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 23 13:12:52 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 23 Oct 2009 20:12:52 -0000
Subject: [MacRuby-devel] [MacRuby] #399: Building MacRuby HEAD with llvm
 trunk r82747 fails at dispatcher.cpp
In-Reply-To: <052.da365ab90dc5b5f7c6799bbe9d95110c@macosforge.org>
References: <052.da365ab90dc5b5f7c6799bbe9d95110c@macosforge.org>
Message-ID: <061.06f9e811b9e323d309373dfe166406e1@macosforge.org>

#399: Building MacRuby HEAD with llvm trunk r82747 fails at dispatcher.cpp
-----------------------------------+----------------------------------------
 Reporter:  nagachika00@?          |       Owner:  lsansonetti@?        
     Type:  defect                 |      Status:  new                  
 Priority:  major                  |   Milestone:                       
Component:  MacRuby                |    Keywords:                       
-----------------------------------+----------------------------------------

Comment(by lsansonetti@?):

 I remember someone reported that similar problem on the mailing-list, a
 few weeks ago. Apparently the root cause might be the --prefix option
 passed during LLVM build (we are not sure yet). I suspect that if you
 install LLVM in /usr/local (as the default) the compilation might not emit
 these -Winline warnings anymore.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/399#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 23 14:05:03 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 23 Oct 2009 21:05:03 -0000
Subject: [MacRuby-devel] [MacRuby] #400: Cannot uninstall gems under macgem
Message-ID: <056.03d17c730783ec2f89da5335006b024d@macosforge.org>

#400: Cannot uninstall gems under macgem
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?        
     Type:  defect                     |      Status:  new                  
 Priority:  blocker                    |   Milestone:  MacRuby 0.5          
Component:  MacRuby                    |    Keywords:                       
---------------------------------------+------------------------------------
 I run

 {{{
 macgem uninstall GEM
 }}}

 with any gem and I receive:

 {{{
 ERROR:  While executing gem ... (Gem::InstallError)
     Unknown gem GEM >= 0

 }}}


 using latest from macruby-trunk (2886).

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/400>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 23 14:22:37 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 23 Oct 2009 21:22:37 -0000
Subject: [MacRuby-devel] [MacRuby] #400: Cannot uninstall gems under
	macgem
In-Reply-To: <056.03d17c730783ec2f89da5335006b024d@macosforge.org>
References: <056.03d17c730783ec2f89da5335006b024d@macosforge.org>
Message-ID: <065.72754f8671c72e575bd533263f1f8c3f@macosforge.org>

#400: Cannot uninstall gems under macgem
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?        
     Type:  defect                     |      Status:  new                  
 Priority:  blocker                    |   Milestone:  MacRuby 0.5          
Component:  MacRuby                    |    Keywords:                       
---------------------------------------+------------------------------------

Comment(by lsansonetti@?):

 Where are the gems installed?

 If you didn't install them using `sudo', they might be in
 ~/.gems/macruby/1.9.0, and to uninstall them you must pass the --install-
 dir option to `macgem uninstall'.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/400#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 23 21:18:58 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 24 Oct 2009 04:18:58 -0000
Subject: [MacRuby-devel] [MacRuby] #399: Building MacRuby HEAD with llvm
 trunk r82747 fails at dispatcher.cpp
In-Reply-To: <052.da365ab90dc5b5f7c6799bbe9d95110c@macosforge.org>
References: <052.da365ab90dc5b5f7c6799bbe9d95110c@macosforge.org>
Message-ID: <061.373a727b3b8a393d7f57c782ae495277@macosforge.org>

#399: Building MacRuby HEAD with llvm trunk r82747 fails at dispatcher.cpp
-----------------------------------+----------------------------------------
 Reporter:  nagachika00@?          |       Owner:  lsansonetti@?        
     Type:  defect                 |      Status:  new                  
 Priority:  major                  |   Milestone:                       
Component:  MacRuby                |    Keywords:                       
-----------------------------------+----------------------------------------

Comment(by nagachika00@?):

 Replying to [comment:1 lsansonetti@?]:

 You're right. I retry without --prefix option for LLVM, and no warning
 during MacRuby building. Thank you for your suggestion.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/399#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 24 03:53:29 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 24 Oct 2009 10:53:29 -0000
Subject: [MacRuby-devel] [MacRuby] #401: Cannot call from ObjC to Ruby with
	an int argument
Message-ID: <054.5da750c5080a6b9816bc334b0c29029b@macosforge.org>

#401: Cannot call from ObjC to Ruby with an int argument
-------------------------------------+--------------------------------------
 Reporter:  antony.blakey@?          |       Owner:  lsansonetti@?        
     Type:  defect                   |      Status:  new                  
 Priority:  critical                 |   Milestone:  MacRuby 0.5          
Component:  MacRuby                  |    Keywords:                       
-------------------------------------+--------------------------------------
 0.5b1 / 10.6.1

 Given this Obj-C trampoline (with corresponding header):

 {{{
 @implementation CallInDriver
 +(id) test:(id)rubyObject {
   return [rubyObject callWithInt:1];
 }
 @end
 }}}


 and this Ruby that uses it:


 {{{
 class Test
   def callWithInt(i)
     nil
   end
 end
 CallInDriver.test(Test.new)
 }}}


 you get:

 {{{
 Program received signal:  ?EXC_BAD_ACCESS".
 }}}

 Changing the ObjC call to:

 {{{
 return [rubyObject callWithInt:[NSNumber numberWithInt: 1]];
 }}}

 doesn't have the problem (as you would expect). I presume this is meant to
 work?

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/401>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 24 11:10:29 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 24 Oct 2009 18:10:29 -0000
Subject: [MacRuby-devel] [MacRuby] #391: HotCocoa on_notification method
 stopped functioning in MacRuby 0.5 under Snow Leopard
In-Reply-To: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
References: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
Message-ID: <064.0127533d96624e0a857d89a1391524e5@macosforge.org>

#391: HotCocoa on_notification method stopped functioning in MacRuby 0.5 under
Snow Leopard
--------------------------------------+-------------------------------------
 Reporter:  trevor@?                  |       Owner:  lsansonetti@?           
     Type:  defect                    |      Status:  new                     
 Priority:  blocker                   |   Milestone:                          
Component:  MacRuby                   |    Keywords:  HotCocoa on_notification
--------------------------------------+-------------------------------------

Comment(by trevor@?):

 I'm struggling with this, I'm afraid. I've got simple scripts suggested by
 the original post on the on_notification method from Richard Kilmer to
 work under Snow Leopard. I now cannot go back to Leopard to see whether my
 Spotify track grabber code still works there, all I know is that it used
 to under Leopard and it doesn't now under SL. It must be something else
 that has changed in the Spotify use of the notification that is causing it
 not to trigger the on-notification in the MacRuby/HotCocoa script. Maybe
 the named=> 'GrowlNotification' has changed or something has tightened up
 in the syntax. I'm looking for a way to check that out but a bit short of
 knowledge on how to get a trace of the message and all I can see is what
 comes out of Growl if it is turned on, which is the normal track
 notification alert.

 Anyway, I'm willing to believe that it isn't a bug in MacRuby/HotCocoa.
 So, thanks for the attention. And happy for the ticket to be closed. Even
 happier if anybody has some suggestions for me!

 regards

 Trevor Hills

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/391#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 24 12:38:03 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 24 Oct 2009 19:38:03 -0000
Subject: [MacRuby-devel] [MacRuby] #401: Cannot call from ObjC to Ruby
 with an int argument
In-Reply-To: <054.5da750c5080a6b9816bc334b0c29029b@macosforge.org>
References: <054.5da750c5080a6b9816bc334b0c29029b@macosforge.org>
Message-ID: <063.f5a75c89d9cd7f5ab69b049f3857f419@macosforge.org>

#401: Cannot call from ObjC to Ruby with an int argument
-------------------------------------+--------------------------------------
 Reporter:  antony.blakey@?          |        Owner:  lsansonetti@?        
     Type:  defect                   |       Status:  closed               
 Priority:  critical                 |    Milestone:  MacRuby 0.5          
Component:  MacRuby                  |   Resolution:  invalid              
 Keywords:                           |  
-------------------------------------+--------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => invalid


Comment:

 Calling Ruby from Objective-C can be problematic because of the runtime
 signature. In your case, the callWithInt: Ruby method is registered by
 default as accepting an Objective-C object, but in the Objective-C side
 you pass a C int, which results in the segfault.

 We introduced an API called -performRubySelector:, we recommend to use it
 when calling Ruby from Objective-C. Check out the MacRuby.h header file
 for the complete list of these APIs.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/401#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 24 17:41:17 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 25 Oct 2009 00:41:17 -0000
Subject: [MacRuby-devel] [MacRuby] #401: Cannot call from ObjC to Ruby
 with an int argument
In-Reply-To: <054.5da750c5080a6b9816bc334b0c29029b@macosforge.org>
References: <054.5da750c5080a6b9816bc334b0c29029b@macosforge.org>
Message-ID: <063.0e24e1ff5d8f34ad6aac59a5d64be5b2@macosforge.org>

#401: Cannot call from ObjC to Ruby with an int argument
-------------------------------------+--------------------------------------
 Reporter:  antony.blakey@?          |        Owner:  lsansonetti@?        
     Type:  defect                   |       Status:  closed               
 Priority:  critical                 |    Milestone:  MacRuby 0.5          
Component:  MacRuby                  |   Resolution:  invalid              
 Keywords:                           |  
-------------------------------------+--------------------------------------

Comment(by antony.blakey@?):

 How is it possible then to implement Ruby objects that act as delegates or
 dataSources? I'm doing this now for table delegates, and it works with int
 arguments. The Ruby object '''doesn't''' descend from an Objective-C
 implementation of the protocol (which I've found fixes the problem). If
 this is true then how can you implement any Objective-C protocol with non-
 object arguments in a Ruby object?

 Is there something I need to do to register a protocol's method signatures
 so that the argument types become the default?

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/401#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 24 19:03:58 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 25 Oct 2009 02:03:58 -0000
Subject: [MacRuby-devel] [MacRuby] #401: Cannot call from ObjC to Ruby
 with an int argument
In-Reply-To: <054.5da750c5080a6b9816bc334b0c29029b@macosforge.org>
References: <054.5da750c5080a6b9816bc334b0c29029b@macosforge.org>
Message-ID: <063.2e20e8e02e74a35c13b5229fd7c39cbd@macosforge.org>

#401: Cannot call from ObjC to Ruby with an int argument
-------------------------------------+--------------------------------------
 Reporter:  antony.blakey@?          |        Owner:  lsansonetti@?        
     Type:  defect                   |       Status:  closed               
 Priority:  critical                 |    Milestone:  MacRuby 0.5          
Component:  MacRuby                  |   Resolution:  invalid              
 Keywords:                           |  
-------------------------------------+--------------------------------------

Comment(by lsansonetti@?):

 The current solution is to provide a BridgeSupport file that annotates all
 informal protocols (including datasource or delegate methods) of your
 Objective-C framework. MacRuby will read that file at runtime and
 appropriately register the methods using the right runtime signature.

 Most frameworks of Mac OS X ship with BridgeSupport files, so you should
 not need to do any of that if you deal with system APIs.

 In case you're trying to use MacRuby from your own Objective-C framework,
 you will have to generate a BridgeSupport file for it. Check out the
 gen_bridge_metadata(1) man-page for more info (you can also google a bit).

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/401#comment:3>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 24 20:06:36 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 25 Oct 2009 03:06:36 -0000
Subject: [MacRuby-devel] [MacRuby] #398: Trouble loading gem
In-Reply-To: <056.b91449423d8f7303e3adc3be774b05b3@macosforge.org>
References: <056.b91449423d8f7303e3adc3be774b05b3@macosforge.org>
Message-ID: <065.32239ead0ca69ff11f3112d9c1450deb@macosforge.org>

#398: Trouble loading gem
------------------------------------------+---------------------------------
 Reporter:  hungerandthirst@?             |        Owner:  lsansonetti@?        
     Type:  defect                        |       Status:  closed               
 Priority:  blocker                       |    Milestone:  MacRuby 0.5          
Component:  MacRuby                       |   Resolution:  fixed                
 Keywords:  gems, macruby, load, defined  |  
------------------------------------------+---------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Should be fixed in r2895.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/398#comment:6>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 24 21:18:11 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 25 Oct 2009 04:18:11 -0000
Subject: [MacRuby-devel] [MacRuby] #380: issues with Set
In-Reply-To: <054.8d7f82f758d7cc81f6817e299532c1a8@macosforge.org>
References: <054.8d7f82f758d7cc81f6817e299532c1a8@macosforge.org>
Message-ID: <063.2f7b4a817c649a8c501d9ee175ecf928@macosforge.org>

#380: issues with Set
-------------------------------------+--------------------------------------
 Reporter:  mattaimonetti@?          |        Owner:  lsansonetti@?        
     Type:  defect                   |       Status:  closed               
 Priority:  blocker                  |    Milestone:  MacRuby 0.5          
Component:  MacRuby                  |   Resolution:  fixed                
 Keywords:                           |  
-------------------------------------+--------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Matt worked on removing the previous set.c CFSet bridging code and as of
 r2896 we now use 1.9's set.rb, this seems to fix this problem.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/380#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 24 21:19:48 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 25 Oct 2009 04:19:48 -0000
Subject: [MacRuby-devel] [MacRuby] #245: Adding to a set causes a Cocoa
 exception to be thrown
In-Reply-To: <057.6585049b858b6fce33365387dde74602@macosforge.org>
References: <057.6585049b858b6fce33365387dde74602@macosforge.org>
Message-ID: <066.ceb8293c04e2c9a3bc5f4f8b44f3efbf@macosforge.org>

#245: Adding to a set causes a Cocoa exception to be thrown
----------------------------------------+-----------------------------------
 Reporter:  dave.baldwin@?              |        Owner:  lsansonetti@?        
     Type:  defect                      |       Status:  closed               
 Priority:  minor                       |    Milestone:  MacRuby 0.5          
Component:  MacRuby                     |   Resolution:  fixed                
 Keywords:  Set operation               |  
----------------------------------------+-----------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Seems to work as of r2896:

 {{{
 $ macruby -r set -e 's=Set.new([1,2,3]); s+=[4,5,6]; p s'
 #<Set: {3, 6, 2, 5, 1, 4}>
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/245#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 24 22:48:18 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 25 Oct 2009 05:48:18 -0000
Subject: [MacRuby-devel] [MacRuby] #402: "unrecognized selector" error if
 overriding Object#dup
Message-ID: <048.395859ae00c53ecf8b7f5df6dd5c5af3@macosforge.org>

#402: "unrecognized selector" error if overriding Object#dup
-------------------------------+--------------------------------------------
 Reporter:  pwilson@?          |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  blocker            |   Milestone:                       
Component:  MacRuby            |    Keywords:                       
-------------------------------+--------------------------------------------
 Given the following code:

 {{{
 #! /usr/bin/ruby -w

 class MyClass
   def dup
     super
   end
 end

 a = MyClass.new
 p a

 b = a.dup
 p b
 }}}

 I get this fatal exception using the Oct 24 nightly build of MacRuby:

 {{{
 2009-10-24 22:45:23.316 macruby[7029:903] -[MyClass copyWithZone:]:
 unrecognized selector sent to instance 0x2029be0
 2009-10-24 22:45:23.321 macruby[7029:903] *** Terminating app due to
 uncaught exception 'NSInvalidArgumentException', reason: '-[MyClass
 copyWithZone:]: unrecognized selector sent to instance 0x2029be0'
 *** Call stack at first throw:
 (
         0   CoreFoundation                      0x9151a40a __raiseError +
 410
         1   libobjc.A.dylib                     0x92dac509
 objc_exception_throw + 56
         2   CoreFoundation                      0x9156690b
 -[NSObject(NSObject) doesNotRecognizeSelector:] + 187
         3   CoreFoundation                      0x914c1db6
 ___forwarding___ + 950
         4   CoreFoundation                      0x914c1982
 _CF_forwarding_prep_0 + 50
         5   CoreFoundation                      0x914ad7ea
 -[NSObject(NSObject) copy] + 42
         6   libmacruby.dylib                    0x0017ae7e rb_vm_dispatch
 + 8622
         7   ???                                 0x00e3e24b 0x0 + 14934603
         8   ???                                 0x00e3e17a 0x0 + 14934394
         9   libmacruby.dylib                    0x0004192b ruby_run_node +
 91
         10  macruby                             0x00001c98 main + 184
         11  macruby                             0x00001bd5 start + 53
         12  ???                                 0x00000002 0x0 + 2
 )
 Killed
 }}}

 The code works as expected when run with Ruby 1.8.7.  It also works
 without the overridden 'dup' method.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/402>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sun Oct 25 03:24:16 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sun, 25 Oct 2009 10:24:16 -0000
Subject: [MacRuby-devel] [MacRuby] #403: rescue block executed if exception
 raised in previous iteration
Message-ID: <048.efa04832ec4225d0683e669e050b76e9@macosforge.org>

#403: rescue block executed if exception raised in previous iteration
-------------------------------+--------------------------------------------
 Reporter:  pwilson@?          |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  major              |   Milestone:  MacRuby 0.5          
Component:  MacRuby            |    Keywords:                       
-------------------------------+--------------------------------------------
 If a begin/rescue block is inside an iterator and the block raises an
 exception on the first iteration but calls return on the second iteration,
 the return is ignored and the rescue block ran a second time.  Here is an
 example:

 {{{
 def main
     [1,2].each do |iter|

       puts "Starting iteration #{iter}"

       begin

         if iter == 1
             raise StandardError
         end
         puts "  Successful iteration #{iter}"
         return true

       rescue StandardError
         puts "  Failed iteration #{iter}"
         next
       end

     end

     return false
 end

 puts main
 }}}

 In Ruby 1.8.7, the main method returns true, but in the Oct 24 nightly
 build of MacRuby, it returns false with this output:

 {{{
 Starting iteration 1
   Failed iteration 1
 Starting iteration 2
   Successful iteration 2
   Failed iteration 2
 false
 }}}

 Note that on the second iteration, both the Successful and Failed log
 messages get printed.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/403>
MacRuby <http://macruby.org/>


From cwdinfo at gmail.com  Sun Oct 25 11:17:44 2009
From: cwdinfo at gmail.com (s.ross)
Date: Sun, 25 Oct 2009 11:17:44 -0700
Subject: [MacRuby-devel] Implementing Undo In RaiseMan / MacRuby
Message-ID: <D96D3C0E-E4B7-40F8-8E3E-963AC8EE1D19@gmail.com>

I'm trying to implement the RaiseMan example from Aaron Hillegass's  
book in MacRuby. All has gone pretty well until I reached undo. The  
idea is to handle the insertObject message each time a Person is  
inserted and manipulate the undo stack.

   def insertObject(p, inEmployeesAtIndex:index)
     NSLog("adding #{p} to #{employees}") # <= Not called, huh?
     undo = @undoManager
     undo.prepareWithInvocationTarget(self,  
removeObjectFromEmployeesAtIndex:index)
     if !undo.isUndoing
       undo.setActionName("Insert Person")
     end
     employees.insertObject(p, atIndex:index)
   end

The Objective-C signature for this is:

- (void)insertObject:(Person *)p inEmployeesAtIndex:(int)index

Works in Objective-C but in my Ruby, the method is not recognized as a  
handler to be invoked when a Person object is to be inserted in the  
employees array. I should note that I created the employees array  
using Ruby syntax:

@employees ||= []

Changing this to:

@employees ||= NSMutableArray.alloc.init

makes no difference in this scenario.

Any hints with respect to what I'm missing here?

Thanks,

Steve

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091025/1e895d73/attachment.html>

From hukl at berlin.ccc.de  Sun Oct 25 12:36:09 2009
From: hukl at berlin.ccc.de (John-Paul Bader)
Date: Sun, 25 Oct 2009 20:36:09 +0100
Subject: [MacRuby-devel] Drawing in Custom Views
Message-ID: <A1303FE4-2641-4F5D-A2D6-5B1C4798403B@berlin.ccc.de>

Hey, just saw the previous question regarding an example from the  
Cocoa book.

I'm currently trying play with custom views and paths. Right now I'm  
trying the Example from page 240 ?Drawing with NSBezierPath? but I  
can't get the path to draw.

I uploaded the xcode project onto http://smyck.org/drawing.zip

The Controller is quite simple http://pastie.textmate.org/private/kafqjbqoml48otms0ddcqq

Something is not right but I don't know what - maybe one of you more  
experienced cocoa coders can help me out.

Kind regards, John

From hukl at berlin.ccc.de  Sun Oct 25 13:21:42 2009
From: hukl at berlin.ccc.de (John-Paul Bader)
Date: Sun, 25 Oct 2009 21:21:42 +0100
Subject: [MacRuby-devel] Drawing in Custom Views
In-Reply-To: <A1303FE4-2641-4F5D-A2D6-5B1C4798403B@berlin.ccc.de>
References: <A1303FE4-2641-4F5D-A2D6-5B1C4798403B@berlin.ccc.de>
Message-ID: <84EE2BF4-2470-4175-AC6A-F9AE4315549C@berlin.ccc.de>

Ah never mind. If I put the path drawing code directly into the  
drawRect method it all works fine.

The whole thing now looks like this: http://pastie.textmate.org/private/rczadjlgyv63txzv6raea

~ John

On 25.10.2009, at 20:36, John-Paul Bader wrote:

> Hey, just saw the previous question regarding an example from the  
> Cocoa book.
>
> I'm currently trying play with custom views and paths. Right now I'm  
> trying the Example from page 240 ?Drawing with NSBezierPath? but I  
> can't get the path to draw.
>
> I uploaded the xcode project onto http://smyck.org/drawing.zip
>
> The Controller is quite simple http://pastie.textmate.org/private/kafqjbqoml48otms0ddcqq
>
> Something is not right but I don't know what - maybe one of you more  
> experienced cocoa coders can help me out.
>
> Kind regards, John
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>


From mattaimonetti at gmail.com  Sun Oct 25 17:00:29 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Sun, 25 Oct 2009 17:00:29 -0700
Subject: [MacRuby-devel] new macruby tips: dialog window
Message-ID: <20fefa50910251700o45b165d5g7d411abd265c900b@mail.gmail.com>

I'm back from vacation and wrote a very simple tutorial:
MacRuby tips: create a Cocoa file/folder browser in a few lines of code:
http://bit.ly/1VuxBZ

It looks like it's time for me to move my tutorials
http://merbist.com/category/macruby/  to MacRuby's recipes.

Anyone feels like contributing more examples/tutorials?

- Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091025/349ecf08/attachment.html>

From cwdinfo at gmail.com  Sun Oct 25 19:10:37 2009
From: cwdinfo at gmail.com (s.ross)
Date: Sun, 25 Oct 2009 19:10:37 -0700
Subject: [MacRuby-devel] new macruby tips: dialog window
In-Reply-To: <20fefa50910251700o45b165d5g7d411abd265c900b@mail.gmail.com>
References: <20fefa50910251700o45b165d5g7d411abd265c900b@mail.gmail.com>
Message-ID: <BFE9BB40-DCD3-454E-B47A-F92883C8E9EE@gmail.com>

On Oct 25, 2009, at 5:00 PM, Matt Aimonetti wrote:

> I'm back from vacation and wrote a very simple tutorial:
> MacRuby tips: create a Cocoa file/folder browser in a few lines of  
> code: http://bit.ly/1VuxBZ
>
> It looks like it's time for me to move my tutorials http://merbist.com/category/macruby/ 
>   to MacRuby's recipes.
>
> Anyone feels like contributing more examples/tutorials?
>
> - Matt
> _______________________________________________

This might be a bit OT, but I poked around github looking for a  
MacRuby version of Aaron Hillegass's RaiseMan and found DrNic's  
effort. I've gotten a bit further, so I put it out there as:

http://github.com/sxross/raiseman-rb

I'm a Cocoa n00b, so I decided that instead of the meatier "real"  
projects that I wanted to do, I would work doggedly through Aaron's  
examples in Objective-C and then do MacRuby ports as I went along.  
I've hit a few snags, but my goal is to have a completely functional  
RaiseMan in MacRuby by the end of the exercise, and perhaps to inject  
some idiomatic Rubyisms into the end product.

-- Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091025/36a352ef/attachment.html>

From mattaimonetti at gmail.com  Sun Oct 25 19:20:42 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Sun, 25 Oct 2009 19:20:42 -0700
Subject: [MacRuby-devel] new macruby tips: dialog window
In-Reply-To: <BFE9BB40-DCD3-454E-B47A-F92883C8E9EE@gmail.com>
References: <20fefa50910251700o45b165d5g7d411abd265c900b@mail.gmail.com>
	<BFE9BB40-DCD3-454E-B47A-F92883C8E9EE@gmail.com>
Message-ID: <20fefa50910251920r89316afq2c6512fff4de74b1@mail.gmail.com>

Hey Steve,

 Check John's repo: http://idisk.mac.com/johnmshea-Public?view=web  he did a
great job porting examples from the book and other examples. That might help
you in your quest to Cocoa knowledge :)

- Matt

On Sun, Oct 25, 2009 at 7:10 PM, s.ross <cwdinfo at gmail.com> wrote:

> On Oct 25, 2009, at 5:00 PM, Matt Aimonetti wrote:
>
> I'm back from vacation and wrote a very simple tutorial:
> MacRuby tips: create a Cocoa file/folder browser in a few lines of code:
> http://bit.ly/1VuxBZ
>
> It looks like it's time for me to move my tutorials
> http://merbist.com/category/macruby/  to MacRuby's recipes.
>
> Anyone feels like contributing more examples/tutorials?
>
> - Matt
> _______________________________________________
>
>
> This might be a bit OT, but I poked around github looking for a MacRuby
> version of Aaron Hillegass's RaiseMan and found DrNic's effort. I've gotten
> a bit further, so I put it out there as:
>
> http://github.com/sxross/raiseman-rb
>
> I'm a Cocoa n00b, so I decided that instead of the meatier "real" projects
> that I wanted to do, I would work doggedly through Aaron's examples in
> Objective-C and then do MacRuby ports as I went along. I've hit a few snags,
> but my goal is to have a completely functional RaiseMan in MacRuby by the
> end of the exercise, and perhaps to inject some idiomatic Rubyisms into the
> end product.
>
> -- Steve
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091025/694069b4/attachment-0001.html>

From koudelka at ryoukai.org  Sun Oct 25 20:24:34 2009
From: koudelka at ryoukai.org (Michael Shapiro)
Date: Sun, 25 Oct 2009 23:24:34 -0400
Subject: [MacRuby-devel] Drawing in Custom Views
In-Reply-To: <84EE2BF4-2470-4175-AC6A-F9AE4315549C@berlin.ccc.de>
References: <A1303FE4-2641-4F5D-A2D6-5B1C4798403B@berlin.ccc.de>
	<84EE2BF4-2470-4175-AC6A-F9AE4315549C@berlin.ccc.de>
Message-ID: <ADC4003E-67EB-4F15-BD46-1462F76A0EBB@ryoukai.org>

Hey John,
You shouldn't need to put everything in drawRect:. In your original,  
you're stomping @path in your drawRect. :)

--Mike

On Oct 25, 2009, at 4:21 PM, John-Paul Bader wrote:

> Ah never mind. If I put the path drawing code directly into the  
> drawRect method it all works fine.
>
> The whole thing now looks like this: http://pastie.textmate.org/private/rczadjlgyv63txzv6raea
>
> ~ John
>
> On 25.10.2009, at 20:36, John-Paul Bader wrote:
>
>> Hey, just saw the previous question regarding an example from the  
>> Cocoa book.
>>
>> I'm currently trying play with custom views and paths. Right now  
>> I'm trying the Example from page 240 ?Drawing with NSBezierPath?  
>> but I can't get the path to draw.
>>
>> I uploaded the xcode project onto http://smyck.org/drawing.zip
>>
>> The Controller is quite simple http://pastie.textmate.org/private/kafqjbqoml48otms0ddcqq
>>
>> Something is not right but I don't know what - maybe one of you  
>> more experienced cocoa coders can help me out.
>>
>> Kind regards, John
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From jazzbox at 7zz.de  Mon Oct 26 00:26:53 2009
From: jazzbox at 7zz.de (B. Ohr)
Date: Mon, 26 Oct 2009 08:26:53 +0100
Subject: [MacRuby-devel] new macruby tips: dialog window
In-Reply-To: <20fefa50910251700o45b165d5g7d411abd265c900b@mail.gmail.com>
References: <20fefa50910251700o45b165d5g7d411abd265c900b@mail.gmail.com>
Message-ID: <B69031E7-BAB4-46E8-BD7A-E70758DE15D6@7zz.de>


Am 26.10.2009 um 01:00 schrieb Matt Aimonetti:

> I'm back from vacation and wrote a very simple tutorial:
> MacRuby tips: create a Cocoa file/folder browser in a few lines of  
> code: http://bit.ly/1VuxBZ

Could you please upload the current state to the github repository?

>
> It looks like it's time for me to move my tutorials http://merbist.com/category/macruby/ 
>   to MacRuby's recipes.
>
> Anyone feels like contributing more examples/tutorials?

I have written a tutorial about "building a static website with  
nanoc", but publishing has to wait until ticket #395 is resolved.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091026/1930fb84/attachment.html>

From mattaimonetti at gmail.com  Mon Oct 26 00:32:28 2009
From: mattaimonetti at gmail.com (Matt Aimonetti)
Date: Mon, 26 Oct 2009 00:32:28 -0700
Subject: [MacRuby-devel] new macruby tips: dialog window
In-Reply-To: <B69031E7-BAB4-46E8-BD7A-E70758DE15D6@7zz.de>
References: <20fefa50910251700o45b165d5g7d411abd265c900b@mail.gmail.com>
	<B69031E7-BAB4-46E8-BD7A-E70758DE15D6@7zz.de>
Message-ID: <20fefa50910260032p4c213bf5i15d8694a77911f88@mail.gmail.com>

On Mon, Oct 26, 2009 at 12:26 AM, B. Ohr <jazzbox at 7zz.de> wrote:

>
> Am 26.10.2009 um 01:00 schrieb Matt Aimonetti:
>
> I'm back from vacation and wrote a very simple tutorial:
> MacRuby tips: create a Cocoa file/folder browser in a few lines of code:
> http://bit.ly/1VuxBZ
>
>
> Could you please upload the current state to the github repository?
>

What do you mean?

- Matt



>
>
> It looks like it's time for me to move my tutorials
> http://merbist.com/category/macruby/  to MacRuby's recipes.
>
> Anyone feels like contributing more examples/tutorials?
>
>
> I have written a tutorial about "building a static website with nanoc", but
> publishing has to wait until ticket #395 is resolved.
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091026/78f7d908/attachment.html>

From jazzbox at 7zz.de  Mon Oct 26 00:45:43 2009
From: jazzbox at 7zz.de (B. Ohr)
Date: Mon, 26 Oct 2009 08:45:43 +0100
Subject: [MacRuby-devel] new macruby tips: dialog window
In-Reply-To: <20fefa50910260032p4c213bf5i15d8694a77911f88@mail.gmail.com>
References: <20fefa50910251700o45b165d5g7d411abd265c900b@mail.gmail.com>
	<B69031E7-BAB4-46E8-BD7A-E70758DE15D6@7zz.de>
	<20fefa50910260032p4c213bf5i15d8694a77911f88@mail.gmail.com>
Message-ID: <A41A76B0-1704-463F-9B58-20469BB91310@7zz.de>


Am 26.10.2009 um 08:32 schrieb Matt Aimonetti:

>
>
> On Mon, Oct 26, 2009 at 12:26 AM, B. Ohr <jazzbox at 7zz.de> wrote:
>
> Am 26.10.2009 um 01:00 schrieb Matt Aimonetti:
>
>> I'm back from vacation and wrote a very simple tutorial:
>> MacRuby tips: create a Cocoa file/folder browser in a few lines of  
>> code: http://bit.ly/1VuxBZ
>
> Could you please upload the current state to the github repository?
>
> What do you mean?
>
> - Matt
>
>

Oh, sorry, I thought you wrote your manual on http://www.macruby.org/ !

On http://github.com/mattetti/macruby_website at least the article  
"test driven development..." is missing.

BTW, wouldn't it be better to publish your articles on http://www.macruby.org/ 
  too?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091026/4b494eac/attachment.html>

From johnmacshea at gmail.com  Mon Oct 26 01:22:32 2009
From: johnmacshea at gmail.com (John Shea)
Date: Mon, 26 Oct 2009 09:22:32 +0100
Subject: [MacRuby-devel] Implementing Undo In RaiseMan / MacRuby
In-Reply-To: <D96D3C0E-E4B7-40F8-8E3E-963AC8EE1D19@gmail.com>
References: <D96D3C0E-E4B7-40F8-8E3E-963AC8EE1D19@gmail.com>
Message-ID: <c3ac07c60910260122w350dee08scb2182d0929c1def@mail.gmail.com>

Hi Steve,
did you solve this one?
if not perhaps you could post somewhere the MyDocument.rb code for us to
look at?
Cheers,
J

On Sun, Oct 25, 2009 at 7:17 PM, s.ross <cwdinfo at gmail.com> wrote:

> I'm trying to implement the RaiseMan example from Aaron Hillegass's book in
> MacRuby. All has gone pretty well until I reached undo. The idea is to
> handle the insertObject message each time a Person is inserted and
> manipulate the undo stack.
>
>   def insertObject(p, inEmployeesAtIndex:index)
>     NSLog("adding #{p} to #{employees}") # <= Not called, huh?
>     undo = @undoManager
>     undo.prepareWithInvocationTarget(self,
> removeObjectFromEmployeesAtIndex:index)
>     if !undo.isUndoing
>       undo.setActionName("Insert Person")
>     end
>     employees.insertObject(p, atIndex:index)
>   end
>
> The Objective-C signature for this is:
>
> - (void)insertObject:(Person *)p inEmployeesAtIndex:(int)index
>
> Works in Objective-C but in my Ruby, the method is not recognized as a
> handler to be invoked when a Person object is to be inserted in the
> employees array. I should note that I created the employees array using Ruby
> syntax:
>
> @employees ||= []
>
> Changing this to:
>
> @employees ||= NSMutableArray.alloc.init
>
> makes no difference in this scenario.
>
> Any hints with respect to what I'm missing here?
>
> Thanks,
>
> Steve
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091026/f7dbe1e5/attachment-0001.html>

From ruby-noreply at macosforge.org  Mon Oct 26 06:02:09 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Mon, 26 Oct 2009 13:02:09 -0000
Subject: [MacRuby-devel] [MacRuby] #400: Cannot uninstall gems under
	macgem
In-Reply-To: <056.03d17c730783ec2f89da5335006b024d@macosforge.org>
References: <056.03d17c730783ec2f89da5335006b024d@macosforge.org>
Message-ID: <065.cbce10e5bed541abf0ac42d1e8927681@macosforge.org>

#400: Cannot uninstall gems under macgem
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?        
     Type:  defect                     |      Status:  new                  
 Priority:  blocker                    |   Milestone:  MacRuby 0.5          
Component:  MacRuby                    |    Keywords:                       
---------------------------------------+------------------------------------

Comment(by hungerandthirst@?):

 Ah interesting. I had always been told installing gems using sudo was a
 bad idea. I'll check with this. It was giving me this error with all gems,
 but then I didn't use sudo for any of them so this makes sense. Thank you.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/400#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct 26 08:04:13 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Mon, 26 Oct 2009 15:04:13 -0000
Subject: [MacRuby-devel] [MacRuby] #404: Segfault with
	ObjectSpace#each_object
Message-ID: <056.9ee7caa8902fbca7a553db1f2ab8ad55@macosforge.org>

#404: Segfault with ObjectSpace#each_object
---------------------------------------+------------------------------------
 Reporter:  keith.gautreaux@?          |       Owner:  lsansonetti@?        
     Type:  defect                     |      Status:  new                  
 Priority:  blocker                    |   Milestone:  MacRuby 0.5          
Component:  MacRuby                    |    Keywords:  objectspace segfault 
---------------------------------------+------------------------------------
 The following code causes a segfault on my machine (MacBookPro3,1):

 {{{
  #!/usr/local/bin/macruby
 ObjectSpace.each_object { |o| puts o }
 }}}

 Unfortunately, I am running the nightly build of MacRuby from
 http://macruby.icoretech.org and it doesn't seem to allow backtrace
 generation with gdb when compiled with:

 {{{
 macrubyc -o macruby_test -a x86_64 macruby_test.rb
 }}}

 I also get a segfault when the code is run under macirb.

 If someone who can generate backtraces could try that method and reproduce
 the segfault that would be great.  If no one becomes available I can try
 compiling macruby from source and running a backtrace.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/404>
MacRuby <http://macruby.org/>


From cwdinfo at gmail.com  Mon Oct 26 08:06:40 2009
From: cwdinfo at gmail.com (s.ross)
Date: Mon, 26 Oct 2009 08:06:40 -0700
Subject: [MacRuby-devel] Implementing Undo In RaiseMan / MacRuby
In-Reply-To: <c3ac07c60910260122w350dee08scb2182d0929c1def@mail.gmail.com>
References: <D96D3C0E-E4B7-40F8-8E3E-963AC8EE1D19@gmail.com>
	<c3ac07c60910260122w350dee08scb2182d0929c1def@mail.gmail.com>
Message-ID: <DF79D29B-3864-4C52-A3B0-3D8E4E80809B@gmail.com>

John--

I've started a github repo at http://github.com/sxross/raiseman-rb,  
but it doesn't yet reflect that I can now do initial editing of an  
inserted row, but undo is not there yet.

Thanks,

Steve


On Oct 26, 2009, at 1:22 AM, John Shea wrote:

> Hi Steve,
> did you solve this one?
> if not perhaps you could post somewhere the MyDocument.rb code for  
> us to look at?
> Cheers,
> J
>
> On Sun, Oct 25, 2009 at 7:17 PM, s.ross <cwdinfo at gmail.com> wrote:
> I'm trying to implement the RaiseMan example from Aaron Hillegass's  
> book in MacRuby. All has gone pretty well until I reached undo. The  
> idea is to handle the insertObject message each time a Person is  
> inserted and manipulate the undo stack.
>
>   def insertObject(p, inEmployeesAtIndex:index)
>     NSLog("adding #{p} to #{employees}") # <= Not called, huh?
>     undo = @undoManager
>     undo.prepareWithInvocationTarget(self,  
> removeObjectFromEmployeesAtIndex:index)
>     if !undo.isUndoing
>       undo.setActionName("Insert Person")
>     end
>     employees.insertObject(p, atIndex:index)
>   end
>
> The Objective-C signature for this is:
>
> - (void)insertObject:(Person *)p inEmployeesAtIndex:(int)index
>
> Works in Objective-C but in my Ruby, the method is not recognized as  
> a handler to be invoked when a Person object is to be inserted in  
> the employees array. I should note that I created the employees  
> array using Ruby syntax:
>
> @employees ||= []
>
> Changing this to:
>
> @employees ||= NSMutableArray.alloc.init
>
> makes no difference in this scenario.
>
> Any hints with respect to what I'm missing here?
>
> Thanks,
>
> Steve
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091026/5ad8fad9/attachment.html>

From prabhaka at apple.com  Mon Oct 26 08:30:33 2009
From: prabhaka at apple.com (Ernest N. Prabhakar, Ph.D.)
Date: Mon, 26 Oct 2009 08:30:33 -0700
Subject: [MacRuby-devel] Implementing Undo In RaiseMan / MacRuby
In-Reply-To: <c3ac07c60910260122w350dee08scb2182d0929c1def@mail.gmail.com>
References: <D96D3C0E-E4B7-40F8-8E3E-963AC8EE1D19@gmail.com>
	<c3ac07c60910260122w350dee08scb2182d0929c1def@mail.gmail.com>
Message-ID: <62A428EB-8D10-46B3-B9AD-2D783F9CC0A4@apple.com>

Sounds like an unboxing issue, which requires a BridgeSupport file.  
Check the archives.

Sent from my iPhone

On Oct 26, 2009, at 1:22, John Shea <johnmacshea at gmail.com> wrote:

> Hi Steve,
> did you solve this one?
> if not perhaps you could post somewhere the MyDocument.rb code for  
> us to look at?
> Cheers,
> J
>
> On Sun, Oct 25, 2009 at 7:17 PM, s.ross <cwdinfo at gmail.com> wrote:
> I'm trying to implement the RaiseMan example from Aaron Hillegass's  
> book in MacRuby. All has gone pretty well until I reached undo. The  
> idea is to handle the insertObject message each time a Person is  
> inserted and manipulate the undo stack.
>
>   def insertObject(p, inEmployeesAtIndex:index)
>     NSLog("adding #{p} to #{employees}") # <= Not called, huh?
>     undo = @undoManager
>     undo.prepareWithInvocationTarget(self,  
> removeObjectFromEmployeesAtIndex:index)
>     if !undo.isUndoing
>       undo.setActionName("Insert Person")
>     end
>     employees.insertObject(p, atIndex:index)
>   end
>
> The Objective-C signature for this is:
>
> - (void)insertObject:(Person *)p inEmployeesAtIndex:(int)index
>
> Works in Objective-C but in my Ruby, the method is not recognized as  
> a handler to be invoked when a Person object is to be inserted in  
> the employees array. I should note that I created the employees  
> array using Ruby syntax:
>
> @employees ||= []
>
> Changing this to:
>
> @employees ||= NSMutableArray.alloc.init
>
> makes no difference in this scenario.
>
> Any hints with respect to what I'm missing here?
>
> Thanks,
>
> Steve
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091026/855c06a2/attachment.html>

From ruby-noreply at macosforge.org  Mon Oct 26 14:01:44 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Mon, 26 Oct 2009 21:01:44 -0000
Subject: [MacRuby-devel] [MacRuby] #395: String#% does not work with %p
In-Reply-To: <045.3e8ec4fce5c76768e096f48d1069caae@macosforge.org>
References: <045.3e8ec4fce5c76768e096f48d1069caae@macosforge.org>
Message-ID: <054.9eeb302a7bdabd8541273924b00c0f61@macosforge.org>

#395: String#% does not work with %p
----------------------------+-----------------------------------------------
 Reporter:  jazzbox@?       |        Owner:  lsansonetti@?        
     Type:  defect          |       Status:  closed               
 Priority:  major           |    Milestone:  MacRuby 0.5          
Component:  MacRuby         |   Resolution:  fixed                
 Keywords:                  |  
----------------------------+-----------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Should be fixed in r2899:

 {{{
 $ ./miniruby -e 'o=Object.new; p o.object_id.to_s(16); p "%p" % o'"
 200094800"
 "0x200094800"
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/395#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct 26 14:05:41 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Mon, 26 Oct 2009 21:05:41 -0000
Subject: [MacRuby-devel] [MacRuby] #400: Cannot uninstall gems under
	macgem
In-Reply-To: <056.03d17c730783ec2f89da5335006b024d@macosforge.org>
References: <056.03d17c730783ec2f89da5335006b024d@macosforge.org>
Message-ID: <065.2a4ca4b77ffcf11a8d874b24ba6b0455@macosforge.org>

#400: Cannot uninstall gems under macgem
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |        Owner:  lsansonetti@?        
     Type:  defect                     |       Status:  closed               
 Priority:  blocker                    |    Milestone:  MacRuby 0.5          
Component:  MacRuby                    |   Resolution:  invalid              
 Keywords:                             |  
---------------------------------------+------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => invalid


Comment:

 Closing.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/400#comment:3>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct 26 14:42:22 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Mon, 26 Oct 2009 21:42:22 -0000
Subject: [MacRuby-devel] [MacRuby] #403: rescue block executed if
 exception raised in previous iteration
In-Reply-To: <048.efa04832ec4225d0683e669e050b76e9@macosforge.org>
References: <048.efa04832ec4225d0683e669e050b76e9@macosforge.org>
Message-ID: <057.58c434eea29da2098d76ba4a7bf38462@macosforge.org>

#403: rescue block executed if exception raised in previous iteration
-------------------------------+--------------------------------------------
 Reporter:  pwilson@?          |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  major              |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:                     |  
-------------------------------+--------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Should be fixed in r2900:

 {{{
 $ ./miniruby t.rb
 Starting iteration 1
   Failed iteration 1
 Starting iteration 2
   Successful iteration 2
 true
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/403#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct 26 15:05:51 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Mon, 26 Oct 2009 22:05:51 -0000
Subject: [MacRuby-devel] [MacRuby] #402: "unrecognized selector" error
 if overriding Object#dup
In-Reply-To: <048.395859ae00c53ecf8b7f5df6dd5c5af3@macosforge.org>
References: <048.395859ae00c53ecf8b7f5df6dd5c5af3@macosforge.org>
Message-ID: <057.43dfd39c081b30ad2ea6c57ba3ca6732@macosforge.org>

#402: "unrecognized selector" error if overriding Object#dup
-------------------------------+--------------------------------------------
 Reporter:  pwilson@?          |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:                     |  
-------------------------------+--------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Should be fixed in r2901:

 {{{
 $ ./miniruby t.rb
 #<MyClass:0x20001f380>
 #<MyClass:0x2000108e0>
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/402#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Mon Oct 26 19:26:57 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 27 Oct 2009 02:26:57 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
Message-ID: <057.e040a5b6066705ca83b13ff671694180@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:                     |  
-------------------------------+--------------------------------------------
Changes (by lsansonetti@?):

  * status:  reopened => closed
  * resolution:  => fixed


Comment:

 Should be fixed by r2903.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:10>
MacRuby <http://macruby.org/>


From johnmacshea at gmail.com  Tue Oct 27 04:38:28 2009
From: johnmacshea at gmail.com (John Shea)
Date: Tue, 27 Oct 2009 12:38:28 +0100
Subject: [MacRuby-devel] Implementing Undo In RaiseMan / MacRuby
In-Reply-To: <DF79D29B-3864-4C52-A3B0-3D8E4E80809B@gmail.com>
References: <D96D3C0E-E4B7-40F8-8E3E-963AC8EE1D19@gmail.com>
	<c3ac07c60910260122w350dee08scb2182d0929c1def@mail.gmail.com>
	<DF79D29B-3864-4C52-A3B0-3D8E4E80809B@gmail.com>
Message-ID: <c3ac07c60910270438rdcea36cp534c2f1844b49743@mail.gmail.com>

Steve,

I am not sure what stage you are at with your example, I originally did this
without using an array controller, and the undoing worked fine.

I just threw together a version with an array controller - and the
insertObject(person,
inEmployeesAtIndex:index) and remove methods are being called by the array
controller - however they seem to be passing the index as a nil. Perhaps
this is what Ernest was talking about - an unboxing issue??
Undoing initially works.

Selecting the second row, and then pressing insert causes a crash into the
debugger - so perhaps again some issue with what method the array controller
is calling or trying to call  (and the vars it is trying to pass)  - as
Ernest implied (?).

Note that this experiment was still with 0.4.
Perhaps it works ok in later versions?

I personally have not come across this issue before because I never use the
arraycontroller method insert and remove - I always have my own controller
methods - usually I want to check other things before adding or removing (I
believe later in the book the array controller methods are replaced with own
methods).

Not a solution but perhaps you can work around it, by using your own
controller actions, and then exploring the undo aspects?

Cheers,
John

On Mon, Oct 26, 2009 at 4:06 PM, s.ross <cwdinfo at gmail.com> wrote:

> John--
>
> I've started a github repo at http://github.com/sxross/raiseman-rb, but it
> doesn't yet reflect that I can now do initial editing of an inserted row,
> but undo is not there yet.
>
> Thanks,
>
> Steve
>
>
> On Oct 26, 2009, at 1:22 AM, John Shea wrote:
>
> Hi Steve,
> did you solve this one?
> if not perhaps you could post somewhere the MyDocument.rb code for us to
> look at?
> Cheers,
> J
>
> On Sun, Oct 25, 2009 at 7:17 PM, s.ross <cwdinfo at gmail.com> wrote:
>
>> I'm trying to implement the RaiseMan example from Aaron Hillegass's book
>> in MacRuby. All has gone pretty well until I reached undo. The idea is to
>> handle the insertObject message each time a Person is inserted and
>> manipulate the undo stack.
>>
>>   def insertObject(p, inEmployeesAtIndex:index)
>>     NSLog("adding #{p} to #{employees}") # <= Not called, huh?
>>     undo = @undoManager
>>     undo.prepareWithInvocationTarget(self,
>> removeObjectFromEmployeesAtIndex:index)
>>     if !undo.isUndoing
>>       undo.setActionName("Insert Person")
>>     end
>>     employees.insertObject(p, atIndex:index)
>>   end
>>
>> The Objective-C signature for this is:
>>
>> - (void)insertObject:(Person *)p inEmployeesAtIndex:(int)index
>>
>> Works in Objective-C but in my Ruby, the method is not recognized as a
>> handler to be invoked when a Person object is to be inserted in the
>> employees array. I should note that I created the employees array using Ruby
>> syntax:
>>
>> @employees ||= []
>>
>> Changing this to:
>>
>> @employees ||= NSMutableArray.alloc.init
>>
>> makes no difference in this scenario.
>>
>> Any hints with respect to what I'm missing here?
>>
>> Thanks,
>>
>> Steve
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091027/3c899de2/attachment-0001.html>

From ben at tanjero.com  Tue Oct 27 09:23:10 2009
From: ben at tanjero.com (Benjamin Stiglitz)
Date: Tue, 27 Oct 2009 12:23:10 -0400
Subject: [MacRuby-devel] Implementing Undo In RaiseMan / MacRuby
In-Reply-To: <D96D3C0E-E4B7-40F8-8E3E-963AC8EE1D19@gmail.com>
References: <D96D3C0E-E4B7-40F8-8E3E-963AC8EE1D19@gmail.com>
Message-ID: <AAE7F116-38BD-4C8C-9F8D-E228DCEAB4BC@tanjero.com>

>   def insertObject(p, inEmployeesAtIndex:index)
>     NSLog("adding #{p} to #{employees}") # <= Not called, huh?
>     undo = @undoManager
>     undo.prepareWithInvocationTarget(self,  
> removeObjectFromEmployeesAtIndex:index)
>     if !undo.isUndoing
>       undo.setActionName("Insert Person")
>     end
>     employees.insertObject(p, atIndex:index)
>   end

FWIW, the third line of the body should read
undo.prepareWithInvocationTarget(self).removeObjectFromEmployeesAtIndex 
(index)

-Ben

From ruby-noreply at macosforge.org  Tue Oct 27 15:58:26 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 27 Oct 2009 22:58:26 -0000
Subject: [MacRuby-devel] [MacRuby] #216: fork subprocess exiting
	(normally) segfaults
In-Reply-To: <048.782fcdbab657c10a2ed80ff65b52a6c3@macosforge.org>
References: <048.782fcdbab657c10a2ed80ff65b52a6c3@macosforge.org>
Message-ID: <057.9b0a6916d0236ae572ac1273127d5774@macosforge.org>

#216: fork subprocess exiting (normally) segfaults
-------------------------------+--------------------------------------------
 Reporter:  celtic@?           |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  major              |   Milestone:                       
Component:  MacRuby            |    Keywords:  fork process         
-------------------------------+--------------------------------------------

Comment(by ernest.prabhakar@?):

 Any update on this? I notice that the MacRuby 0.5 beta (nightly) simply
 reports "fork" as unsupported, perhaps due to this.

 irb(main):001:0> fork
 RuntimeError: fork is not supported yet
         from core:in `fork'
         from (irb):1:in `<main>'
         from core:in `eval:'
         from core:in `evaluate:'

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/216#comment:4>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 27 16:16:21 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 27 Oct 2009 23:16:21 -0000
Subject: [MacRuby-devel] [MacRuby] #385: Cannot distribute macruby apps
In-Reply-To: <056.2dfff30c57e596c435e982e9f263c6b9@macosforge.org>
References: <056.2dfff30c57e596c435e982e9f263c6b9@macosforge.org>
Message-ID: <065.5d96e7c76344c60533d6be13177ae6d1@macosforge.org>

#385: Cannot distribute macruby apps
-------------------------------------------+--------------------------------
 Reporter:  hungerandthirst@?              |        Owner:  lsansonetti@?        
     Type:  defect                         |       Status:  closed               
 Priority:  blocker                        |    Milestone:  MacRuby 0.5          
Component:  MacRuby                        |   Resolution:  fixed                
 Keywords:  macruby, distribute, rubygems  |  
-------------------------------------------+--------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 This should be fixed in r2905, make sure to remove the old "Embed MacRuby"
 target of your project and add the new one.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/385#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 27 16:23:23 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 27 Oct 2009 23:23:23 -0000
Subject: [MacRuby-devel] [MacRuby] #361: Embed MacRuby Target Adds 60+
	MB to .app
In-Reply-To: <050.572b3571708c100e8e310b9c06e29519@macosforge.org>
References: <050.572b3571708c100e8e310b9c06e29519@macosforge.org>
Message-ID: <059.b95b67ba2d778ca78f7c6c4fdafedd3a@macosforge.org>

#361: Embed MacRuby Target Adds 60+ MB to .app
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |        Owner:  lsansonetti@?        
     Type:  defect               |       Status:  closed               
 Priority:  blocker              |    Milestone:  MacRuby 0.5          
Component:  MacRuby              |   Resolution:  fixed                
 Keywords:                       |  
---------------------------------+------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 As of r2905, the new Embed MacRuby target makes a fresh new MacRuby .app
 49MB, and when passing --no-stdlib to macruby_deploy inside the target
 script the .app becomes 28MB.

 We will make further improvements in the near future to reduce the size of
 embedded macruby apps, but I think this bug can be closed.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/361#comment:3>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 27 16:24:13 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 27 Oct 2009 23:24:13 -0000
Subject: [MacRuby-devel] [MacRuby] #360: Embed MacRuby Target Fails If
 $TARGET_BUILD_DIR contains spaces
In-Reply-To: <050.eedc780aca8b27bf94a63fda9a2989fe@macosforge.org>
References: <050.eedc780aca8b27bf94a63fda9a2989fe@macosforge.org>
Message-ID: <059.08c21b9b2a8f16d2288ee6853332a07f@macosforge.org>

#360: Embed MacRuby Target Fails If $TARGET_BUILD_DIR contains spaces
---------------------------------+------------------------------------------
 Reporter:  dylan@?              |        Owner:  lsansonetti@?        
     Type:  defect               |       Status:  closed               
 Priority:  blocker              |    Milestone:  MacRuby 0.5          
Component:  MacRuby              |   Resolution:  fixed                
 Keywords:                       |  
---------------------------------+------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Thank you, merged as r2906.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/360#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 27 16:27:40 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 27 Oct 2009 23:27:40 -0000
Subject: [MacRuby-devel] [MacRuby] #216: fork subprocess exiting
	(normally) segfaults
In-Reply-To: <048.782fcdbab657c10a2ed80ff65b52a6c3@macosforge.org>
References: <048.782fcdbab657c10a2ed80ff65b52a6c3@macosforge.org>
Message-ID: <057.1092df410227a967bdbf67bc0ebc0b1e@macosforge.org>

#216: fork subprocess exiting (normally) segfaults
-------------------------------+--------------------------------------------
 Reporter:  celtic@?           |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  major              |   Milestone:                       
Component:  MacRuby            |    Keywords:  fork process         
-------------------------------+--------------------------------------------

Comment(by lsansonetti@?):

 #fork will be hard to support in MacRuby because the underlying system
 (CoreFoundation, libauto) do not support it. I highly recommend using
 threads OR GCD instead.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/216#comment:5>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 27 16:30:09 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 27 Oct 2009 23:30:09 -0000
Subject: [MacRuby-devel] [MacRuby] #216: fork subprocess exiting
	(normally) segfaults
In-Reply-To: <048.782fcdbab657c10a2ed80ff65b52a6c3@macosforge.org>
References: <048.782fcdbab657c10a2ed80ff65b52a6c3@macosforge.org>
Message-ID: <057.691f3a6c86622a84a28a6aecaf78040e@macosforge.org>

#216: fork subprocess exiting (normally) segfaults
-------------------------------+--------------------------------------------
 Reporter:  celtic@?           |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  major              |   Milestone:                       
Component:  MacRuby            |    Keywords:  fork process         
-------------------------------+--------------------------------------------

Comment(by ernest.prabhakar@?):

 I can appreciate that, but I really want to run something in a separate
 *process* to take advantage of memory isolation.  Is there another way to
 asynchronously spawn another process from Ruby?

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/216#comment:6>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 27 16:35:21 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Tue, 27 Oct 2009 23:35:21 -0000
Subject: [MacRuby-devel] [MacRuby] #216: fork subprocess exiting
	(normally) segfaults
In-Reply-To: <048.782fcdbab657c10a2ed80ff65b52a6c3@macosforge.org>
References: <048.782fcdbab657c10a2ed80ff65b52a6c3@macosforge.org>
Message-ID: <057.03212a6ef4a0770b9623d400412ee91e@macosforge.org>

#216: fork subprocess exiting (normally) segfaults
-------------------------------+--------------------------------------------
 Reporter:  celtic@?           |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  major              |   Milestone:                       
Component:  MacRuby            |    Keywords:  fork process         
-------------------------------+--------------------------------------------

Comment(by lsansonetti@?):

 You can still spawn a new process (using #system, #`, #popen, etc.). If
 you want to run Ruby code in that process, you can spawn a new
 `/usr/bin/env macruby' process that way.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/216#comment:7>
MacRuby <http://macruby.org/>


From al_skipp at fastmail.fm  Tue Oct 27 17:13:17 2009
From: al_skipp at fastmail.fm (Alan Skipp)
Date: Wed, 28 Oct 2009 00:13:17 +0000
Subject: [MacRuby-devel] spotlight - MDItemRef
Message-ID: <1256688797.10538.1342295669@webmail.messagingengine.com>

Would anyone be able to give me a hint on how to get the following
objective-c code working with macruby. The code uses spotlight to
extract metadata from a file.

MDItemRef inspectedRef =
MDItemCreate(kCFAllocatorDefault,(CFStringRef)path);
CFArrayRef attributeNames = MDItemCopyAttributeNames(inspectedRef);
	
NSLog(@"%@", (NSArray*)attributeNames);


I was hoping that including the 'CoreServices' framework would work, but
no joy.

>> framework 'CoreServices'
=> true
>> item = MDItemCreate(KCFAllocatorDefault, '/Users/alan/Desktop/test.jpg')
NameError: uninitialized constant KCFAllocatorDefault
	from core:in `const_missing:'
	from (irb):2:in `<main>'
	from core:in `eval:'
	from core:in `evaluate:'
-- 
  Alan Skipp
  al_skipp at fastmail.fm

-- 
http://www.fastmail.fm - IMAP accessible web-mail


From lsansonetti at apple.com  Tue Oct 27 17:31:32 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Tue, 27 Oct 2009 17:31:32 -0700
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <1256688797.10538.1342295669@webmail.messagingengine.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com>
Message-ID: <983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>

Hi Alan,

I'm afraid the MD* APIs haven't been covered by BridgeSupport yet, so  
it may not be possible to call it directly from MacRuby at this point.  
I would recommend to file a bug at http://bugreporter.apple.com so  
that we can consider this for a future Mac OS X release, and to wrap  
this C API into an Objective-C class that you can call from MacRuby in  
the meantime.

Laurent

On Oct 27, 2009, at 5:13 PM, Alan Skipp wrote:

> Would anyone be able to give me a hint on how to get the following
> objective-c code working with macruby. The code uses spotlight to
> extract metadata from a file.
>
> MDItemRef inspectedRef =
> MDItemCreate(kCFAllocatorDefault,(CFStringRef)path);
> CFArrayRef attributeNames = MDItemCopyAttributeNames(inspectedRef);
> 	
> NSLog(@"%@", (NSArray*)attributeNames);
>
>
> I was hoping that including the 'CoreServices' framework would work,  
> but
> no joy.
>
>>> framework 'CoreServices'
> => true
>>> item = MDItemCreate(KCFAllocatorDefault, '/Users/alan/Desktop/ 
>>> test.jpg')
> NameError: uninitialized constant KCFAllocatorDefault
> 	from core:in `const_missing:'
> 	from (irb):2:in `<main>'
> 	from core:in `eval:'
> 	from core:in `evaluate:'
> -- 
>  Alan Skipp
>  al_skipp at fastmail.fm
>
> -- 
> http://www.fastmail.fm - IMAP accessible web-mail
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Tue Oct 27 17:39:24 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 28 Oct 2009 00:39:24 -0000
Subject: [MacRuby-devel] [MacRuby] #90: macruby fails to install
	(problem with File.join)
In-Reply-To: <052.49258afcf771a42237e6d1799d7c83c4@macosforge.org>
References: <052.49258afcf771a42237e6d1799d7c83c4@macosforge.org>
Message-ID: <061.677c53c2a4670d59129a7c27d981d207@macosforge.org>

#90: macruby fails to install (problem with File.join)
-----------------------------------+----------------------------------------
 Reporter:  jakub.suder@?          |        Owner:  lsansonetti@?        
     Type:  defect                 |       Status:  closed               
 Priority:  blocker                |    Milestone:  MacRuby 0.5          
Component:  MacRuby                |   Resolution:  fixed                
 Keywords:                         |  
-----------------------------------+----------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 This should probably be fixed now.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/90#comment:6>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 27 17:40:05 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 28 Oct 2009 00:40:05 -0000
Subject: [MacRuby-devel] [MacRuby] #334: MacIrb hangs after require on
	Snow Leopard
In-Reply-To: <054.8a20477737ff1ec9b3cec1563f4afbfa@macosforge.org>
References: <054.8a20477737ff1ec9b3cec1563f4afbfa@macosforge.org>
Message-ID: <063.d61a82072e849b196423e209a9642bcd@macosforge.org>

#334: MacIrb hangs after require on Snow Leopard
-------------------------------------+--------------------------------------
 Reporter:  rwalsh@?                 |        Owner:  lsansonetti@?        
     Type:  defect                   |       Status:  closed               
 Priority:  blocker                  |    Milestone:  MacRuby 0.5          
Component:  MacRuby                  |   Resolution:  fixed                
 Keywords:                           |  
-------------------------------------+--------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 This should be fixed since a long time and at least in 0.5 beta1.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/334#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 27 20:37:29 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 28 Oct 2009 03:37:29 -0000
Subject: [MacRuby-devel] [MacRuby] #405: Uncaught exception building RubyGems
Message-ID: <056.2e9b9ea3195d71bb2bb1941612ebd58b@macosforge.org>

#405: Uncaught exception building RubyGems
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?               
     Type:  defect                     |      Status:  new                         
 Priority:  blocker                    |   Milestone:  MacRuby 0.5                 
Component:  MacRuby                    |    Keywords:  macruby, rubygems, exception
---------------------------------------+------------------------------------
 Trying to build RubyGems with macruby throws:

 {{{
 uncaught Objective-C/C++ exception...
 terminate called after throwing an instance of
 'RoxorReturnFromBlockException*'
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/405>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 27 20:56:43 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 28 Oct 2009 03:56:43 -0000
Subject: [MacRuby-devel] [MacRuby] #405: Uncaught exception building
	RubyGems
In-Reply-To: <056.2e9b9ea3195d71bb2bb1941612ebd58b@macosforge.org>
References: <056.2e9b9ea3195d71bb2bb1941612ebd58b@macosforge.org>
Message-ID: <065.6ba5b6719d99bedcd1a3ca7862f56b2b@macosforge.org>

#405: Uncaught exception building RubyGems
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?               
     Type:  defect                     |      Status:  new                         
 Priority:  blocker                    |   Milestone:  MacRuby 0.5                 
Component:  MacRuby                    |    Keywords:  macruby, rubygems, exception
---------------------------------------+------------------------------------

Comment(by lsansonetti@?):

 Could you provide more information about what you are trying to do? It's
 impossible to determine from what you gave us.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/405#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Tue Oct 27 21:28:30 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 28 Oct 2009 04:28:30 -0000
Subject: [MacRuby-devel] [MacRuby] #406: Can't load gem grit.
Message-ID: <056.256b9e037413b63441189f2d9bdda620@macosforge.org>

#406: Can't load gem grit.
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?        
     Type:  defect                     |      Status:  new                  
 Priority:  blocker                    |   Milestone:  MacRuby 0.5          
Component:  MacRuby                    |    Keywords:  rubygems, grit, gems 
---------------------------------------+------------------------------------
 Sorry to be so specific about not being able to load a specific gem.
 I do this:

 {{{
 require 'rubygems'
 require 'grit'
 include Grit
 }}}

 and get

 {{{
 in `require:': undefined method `[]' for nil:NilClass (NoMethodError).
 }}}

 It seems to be coming from the

 {{{
 require 'rubygems'
 }}}

 inside of grit.rb. If I disable this line, it includes it with the
 following warnings:

 {{{
 unknown: warning: already initialized constant VERSION
 unknown: warning: already initialized constant MEDIA_TYPE_RE
 unknown: warning: already initialized constant UNREG_RE
 unknown: warning: already initialized constant ENCODING_RE
 unknown: warning: already initialized constant PLATFORM_RE
 unknown: warning: already initialized constant SIGNATURES
 unknown: warning: already initialized constant IANA_URL
 unknown: warning: already initialized constant RFC_URL
 unknown: warning: already initialized constant DRAFT_URL
 unknown: warning: already initialized constant LTSW_URL
 unknown: warning: already initialized constant CONTACT_URL
 unknown: warning: can't register `extensions' as an KVO setter on class
 `MIME::Type' (method `setExtensions:')
 unknown: warning: can't register `encoding' as an KVO setter on class
 `MIME::Type' (method `setEncoding:')
 unknown: warning: can't register `system' as an KVO setter on class
 `MIME::Type' (method `setSystem:')
 unknown: warning: can't register `obsolete' as an KVO setter on class
 `MIME::Type' (method `setObsolete:')
 unknown: warning: can't register `docs' as an KVO setter on class
 `MIME::Type' (method `setDocs:')
 unknown: warning: can't register `url' as an KVO setter on class
 `MIME::Type' (method `setUrl:')
 unknown: warning: can't register `registered' as an KVO setter on class
 `MIME::Type' (method `setRegistered:')
 unknown: warning: already initialized constant VERSION
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/406>
MacRuby <http://macruby.org/>


From demallien at me.com  Wed Oct 28 02:31:33 2009
From: demallien at me.com (Allison Newman)
Date: Wed, 28 Oct 2009 10:31:33 +0100
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com>
	<983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
Message-ID: <126587033973287886298186494201619914828-Webmail@me.com>

 I'm probably asking a really dumb question here - but I haven't used bridgesupport very much...
Is there a reason why the constant in the example that fails starts with an upper case K, rather than keeping the lower case k given in the framework?

Alli

On Wednesday, October 28, 2009, at 01:31AM, "Laurent Sansonetti" <lsansonetti at apple.com> wrote:
>Hi Alan,
>
>I'm afraid the MD* APIs haven't been covered by BridgeSupport yet, so  
>it may not be possible to call it directly from MacRuby at this point.  
>I would recommend to file a bug at http://bugreporter.apple.com so  
>that we can consider this for a future Mac OS X release, and to wrap  
>this C API into an Objective-C class that you can call from MacRuby in  
>the meantime.
>
>Laurent
>
>On Oct 27, 2009, at 5:13 PM, Alan Skipp wrote:
>
>> Would anyone be able to give me a hint on how to get the following
>> objective-c code working with macruby. The code uses spotlight to
>> extract metadata from a file.
>>
>> MDItemRef inspectedRef =
>> MDItemCreate(kCFAllocatorDefault,(CFStringRef)path);
>> CFArrayRef attributeNames = MDItemCopyAttributeNames(inspectedRef);
>> 	
>> NSLog(@"%@", (NSArray*)attributeNames);
>>
>>
>> I was hoping that including the 'CoreServices' framework would work,  
>> but
>> no joy.
>>
>>>> framework 'CoreServices'
>> => true
>>>> item = MDItemCreate(KCFAllocatorDefault, '/Users/alan/Desktop/ 
>>>> test.jpg')
>> NameError: uninitialized constant KCFAllocatorDefault
>> 	from core:in `const_missing:'
>> 	from (irb):2:in `<main>'
>> 	from core:in `eval:'
>> 	from core:in `evaluate:'
>> -- 
>>  Alan Skipp
>>  al_skipp at fastmail.fm
>>
>> -- 
>> http://www.fastmail.fm - IMAP accessible web-mail
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>_______________________________________________
>MacRuby-devel mailing list
>MacRuby-devel at lists.macosforge.org
>http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>

From joshua.ballanco at apple.com  Wed Oct 28 02:48:44 2009
From: joshua.ballanco at apple.com (Joshua Ballanco)
Date: Wed, 28 Oct 2009 02:48:44 -0700
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <126587033973287886298186494201619914828-Webmail@me.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com>
	<983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
	<126587033973287886298186494201619914828-Webmail@me.com>
Message-ID: <78305F40-2187-41C4-8E53-3FE4D8600234@apple.com>

Not a dumb question at all, just one of those "Ruby-isms" that will  
take some adjusting to if you're coming from a C/C++/Obj-C background.  
In Ruby, Constants always start with a Capital letter. Therefore, all  
of the kFooBarBaz constants from Cocoa get translated as KFooBarBaz.

Actually, that's got me thinking that we should maybe compile a list  
of the "cultural" differences between Obj-C and Ruby. I tried to sort  
of touch on it by pointing out Obj-C's tendency to CamelCase in place  
of Ruby's under_case, but I'm sure we can think of more of these  
transition-gotchas?

- Josh


On Oct 28, 2009, at 2:31 AM, Allison Newman wrote:

> I'm probably asking a really dumb question here - but I haven't used  
> bridgesupport very much...
> Is there a reason why the constant in the example that fails starts  
> with an upper case K, rather than keeping the lower case k given in  
> the framework?
>
> Alli
>
> On Wednesday, October 28, 2009, at 01:31AM, "Laurent Sansonetti" <lsansonetti at apple.com 
> > wrote:
>> Hi Alan,
>>
>> I'm afraid the MD* APIs haven't been covered by BridgeSupport yet, so
>> it may not be possible to call it directly from MacRuby at this  
>> point.
>> I would recommend to file a bug at http://bugreporter.apple.com so
>> that we can consider this for a future Mac OS X release, and to wrap
>> this C API into an Objective-C class that you can call from MacRuby  
>> in
>> the meantime.
>>
>> Laurent
>>
>> On Oct 27, 2009, at 5:13 PM, Alan Skipp wrote:
>>
>>> Would anyone be able to give me a hint on how to get the following
>>> objective-c code working with macruby. The code uses spotlight to
>>> extract metadata from a file.
>>>
>>> MDItemRef inspectedRef =
>>> MDItemCreate(kCFAllocatorDefault,(CFStringRef)path);
>>> CFArrayRef attributeNames = MDItemCopyAttributeNames(inspectedRef);
>>> 	
>>> NSLog(@"%@", (NSArray*)attributeNames);
>>>
>>>
>>> I was hoping that including the 'CoreServices' framework would work,
>>> but
>>> no joy.
>>>
>>>>> framework 'CoreServices'
>>> => true
>>>>> item = MDItemCreate(KCFAllocatorDefault, '/Users/alan/Desktop/
>>>>> test.jpg')
>>> NameError: uninitialized constant KCFAllocatorDefault
>>> 	from core:in `const_missing:'
>>> 	from (irb):2:in `<main>'
>>> 	from core:in `eval:'
>>> 	from core:in `evaluate:'
>>> -- 
>>> Alan Skipp
>>> al_skipp at fastmail.fm
>>>
>>> -- 
>>> http://www.fastmail.fm - IMAP accessible web-mail
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From johnmacshea at gmail.com  Wed Oct 28 02:49:21 2009
From: johnmacshea at gmail.com (John Shea)
Date: Wed, 28 Oct 2009 10:49:21 +0100
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <126587033973287886298186494201619914828-Webmail@me.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com>
	<983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
	<126587033973287886298186494201619914828-Webmail@me.com>
Message-ID: <E4213FFE-1B95-4D70-A3CE-EAE9E9BE72DE@gmail.com>

I always assumed (with no direct evidence) that it was because in  
Ruby, constants have to start with an uppercase letter, and so to  
match various method signatures/types sent through BridgeSupport,  
constant types must be passed as constant types.

Anyway for supported frameworks capitalising the constant always seems  
to work.

BridgeSupport is an amazing piece of work in my opinion - worksk (and  
work very well) almost transparent to the developer.

Actually am just assuming that the new Applescript methods use  
BridgeSupport? In which case BridgeSupport should just get better.

HTH
J


On Oct 28, 2009, at 10:31 , Allison Newman wrote:

> I'm probably asking a really dumb question here - but I haven't used  
> bridgesupport very much...
> Is there a reason why the constant in the example that fails starts  
> with an upper case K, rather than keeping the lower case k given in  
> the framework?
>
> Alli
>
> On Wednesday, October 28, 2009, at 01:31AM, "Laurent Sansonetti" <lsansonetti at apple.com 
> > wrote:
>> Hi Alan,
>>
>> I'm afraid the MD* APIs haven't been covered by BridgeSupport yet, so
>> it may not be possible to call it directly from MacRuby at this  
>> point.
>> I would recommend to file a bug at http://bugreporter.apple.com so
>> that we can consider this for a future Mac OS X release, and to wrap
>> this C API into an Objective-C class that you can call from MacRuby  
>> in
>> the meantime.
>>
>> Laurent
>>
>> On Oct 27, 2009, at 5:13 PM, Alan Skipp wrote:
>>
>>> Would anyone be able to give me a hint on how to get the following
>>> objective-c code working with macruby. The code uses spotlight to
>>> extract metadata from a file.
>>>
>>> MDItemRef inspectedRef =
>>> MDItemCreate(kCFAllocatorDefault,(CFStringRef)path);
>>> CFArrayRef attributeNames = MDItemCopyAttributeNames(inspectedRef);
>>> 	
>>> NSLog(@"%@", (NSArray*)attributeNames);
>>>
>>>
>>> I was hoping that including the 'CoreServices' framework would work,
>>> but
>>> no joy.
>>>
>>>>> framework 'CoreServices'
>>> => true
>>>>> item = MDItemCreate(KCFAllocatorDefault, '/Users/alan/Desktop/
>>>>> test.jpg')
>>> NameError: uninitialized constant KCFAllocatorDefault
>>> 	from core:in `const_missing:'
>>> 	from (irb):2:in `<main>'
>>> 	from core:in `eval:'
>>> 	from core:in `evaluate:'
>>> -- 
>>> Alan Skipp
>>> al_skipp at fastmail.fm
>>>
>>> -- 
>>> http://www.fastmail.fm - IMAP accessible web-mail
>>>
>>> _______________________________________________
>>> MacRuby-devel mailing list
>>> MacRuby-devel at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Wed Oct 28 07:09:54 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 28 Oct 2009 14:09:54 -0000
Subject: [MacRuby-devel] [MacRuby] #405: Uncaught exception building
	RubyGems
In-Reply-To: <056.2e9b9ea3195d71bb2bb1941612ebd58b@macosforge.org>
References: <056.2e9b9ea3195d71bb2bb1941612ebd58b@macosforge.org>
Message-ID: <065.861841595963a5d939bb810b10518e87@macosforge.org>

#405: Uncaught exception building RubyGems
---------------------------------------+------------------------------------
 Reporter:  hungerandthirst@?          |       Owner:  lsansonetti@?               
     Type:  defect                     |      Status:  new                         
 Priority:  blocker                    |   Milestone:  MacRuby 0.5                 
Component:  MacRuby                    |    Keywords:  macruby, rubygems, exception
---------------------------------------+------------------------------------

Comment(by hungerandthirst@?):

 I'm trying to build the RubyGems library with MacRuby by running the
 command:
 {{{
 macruby setup.rb
 }}}

 on the RubyGems codebase to build and install RubyGems using macruby. It
 fails with the above error.
 Using rubygems 1.3.5.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/405#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 10:16:02 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 28 Oct 2009 17:16:02 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
Message-ID: <057.77b635bfabfa0daa368e61db82866b86@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:                     |  
-------------------------------+--------------------------------------------

Comment(by cwdinfo@?):

 I am still getting a bad range passed into the complete method. The result
 of typing ABC<ESC> is:

 {{{
 text field is abc
 called completions #<NSRange:0x2002bbee0> = 0 140734799798096
 }}}

 This is on the 2009-10-28 nightly build.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:11>
MacRuby <http://macruby.org/>


From cwdinfo at gmail.com  Wed Oct 28 10:20:17 2009
From: cwdinfo at gmail.com (s.ross)
Date: Wed, 28 Oct 2009 10:20:17 -0700
Subject: [MacRuby-devel] Implementing Undo In RaiseMan / MacRuby
In-Reply-To: <c3ac07c60910270438rdcea36cp534c2f1844b49743@mail.gmail.com>
References: <D96D3C0E-E4B7-40F8-8E3E-963AC8EE1D19@gmail.com>
	<c3ac07c60910260122w350dee08scb2182d0929c1def@mail.gmail.com>
	<DF79D29B-3864-4C52-A3B0-3D8E4E80809B@gmail.com>
	<c3ac07c60910270438rdcea36cp534c2f1844b49743@mail.gmail.com>
Message-ID: <DD7146DA-4549-4527-B289-B725BC2D637C@gmail.com>

John--

Comments interleaved:

On Oct 27, 2009, at 4:38 AM, John Shea wrote:

> Steve,
>
> I am not sure what stage you are at with your example, I originally  
> did this without using an array controller, and the undoing worked  
> fine.
>
> I just threw together a version with an array controller - and the   
> insertObject(person, inEmployeesAtIndex:index) and remove methods  
> are being called by the array controller - however they seem to be  
> passing the index as a nil. Perhaps this is what Ernest was talking  
> about - an unboxing issue??
> Undoing initially works.

I'm not certain what to do about an unboxing issue. What I'm trying to  
do is work up some muscle memory with Cocoa and translating the  
prevailing Objective-C documentation to MacRuby in my head.

> Selecting the second row, and then pressing insert causes a crash  
> into the debugger - so perhaps again some issue with what method the  
> array controller is calling or trying to call  (and the vars it is  
> trying to pass)  - as Ernest implied (?).

That's what I see too on the current nightly build, but not having  
source limits what I can observe about this.

> Note that this experiment was still with 0.4.
> Perhaps it works ok in later versions?
>
> I personally have not come across this issue before because I never  
> use the arraycontroller method insert and remove - I always have my  
> own controller methods - usually I want to check other things before  
> adding or removing (I believe later in the book the array controller  
> methods are replaced with own methods).

And this is what I do under normal circumstances. There's a ton of  
magic in the wiring of this example ath the point where undo is  
supposed to first start working because a good deal of stuff is done  
in IB. That complicates debugging as opposed to wiring things up in  
code IMO.

> Not a solution but perhaps you can work around it, by using your own  
> controller actions, and then exploring the undo aspects?
>
> Cheers,
> John
>
> On Mon, Oct 26, 2009 at 4:06 PM, s.ross <cwdinfo at gmail.com> wrote:
> John--
>
> I've started a github repo at http://github.com/sxross/raiseman-rb,  
> but it doesn't yet reflect that I can now do initial editing of an  
> inserted row, but undo is not there yet.
>
> Thanks,
>
> Steve
>
>
> On Oct 26, 2009, at 1:22 AM, John Shea wrote:
>
>> Hi Steve,
>> did you solve this one?
>> if not perhaps you could post somewhere the MyDocument.rb code for  
>> us to look at?
>> Cheers,
>> J
>>
>> On Sun, Oct 25, 2009 at 7:17 PM, s.ross <cwdinfo at gmail.com> wrote:
>> I'm trying to implement the RaiseMan example from Aaron Hillegass's  
>> book in MacRuby. All has gone pretty well until I reached undo. The  
>> idea is to handle the insertObject message each time a Person is  
>> inserted and manipulate the undo stack.
>>
>>   def insertObject(p, inEmployeesAtIndex:index)
>>     NSLog("adding #{p} to #{employees}") # <= Not called, huh?
>>     undo = @undoManager
>>     undo.prepareWithInvocationTarget(self,  
>> removeObjectFromEmployeesAtIndex:index)
>>     if !undo.isUndoing
>>       undo.setActionName("Insert Person")
>>     end
>>     employees.insertObject(p, atIndex:index)
>>   end
>>
>> The Objective-C signature for this is:
>>
>> - (void)insertObject:(Person *)p inEmployeesAtIndex:(int)index
>>
>> Works in Objective-C but in my Ruby, the method is not recognized  
>> as a handler to be invoked when a Person object is to be inserted  
>> in the employees array. I should note that I created the employees  
>> array using Ruby syntax:
>>
>> @employees ||= []
>>
>> Changing this to:
>>
>> @employees ||= NSMutableArray.alloc.init
>>
>> makes no difference in this scenario.
>>
>> Any hints with respect to what I'm missing here?
>>
>> Thanks,
>>
>> Steve
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091028/c73ee0a2/attachment.html>

From ruby-noreply at macosforge.org  Wed Oct 28 11:46:26 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 28 Oct 2009 18:46:26 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
Message-ID: <057.053978dc2e505f3af9caf3292f08036f@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:                     |  
-------------------------------+--------------------------------------------

Comment(by lsansonetti@?):

 As of r2908 I get the following output:

 {{{
 text field is arf
 called completions #<NSRange:0x2003bcaa0> = 3 0
 "{0, 3}"
 }}}

 For the following code:

 {{{
   def control(control, textView: view, completions: completions,
 forPartialWordRange: range, indexOfSelectedItem: index)
     puts "text field is #{@textField.stringValue}"
     puts "called completions #{range} = #{range.length} #{range.location}"
     p NSStringFromRange(range)
     ['foo', 'bar', 'foobar']
   end
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:12>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 13:50:20 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 28 Oct 2009 20:50:20 -0000
Subject: [MacRuby-devel] [MacRuby] #407: NSData#bytes does not work
Message-ID: <050.559af3c3e56a737d39d62700d76b69ba@macosforge.org>

#407: NSData#bytes does not work
---------------------------------+------------------------------------------
 Reporter:  neeracher@?          |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  major                |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------
 MacRuby rev 2903.

 ---------------- Code ------------
 framework 'Cocoa'

 d = "xy".dataUsingEncoding(NSMacOSRomanStringEncoding)
 d.bytes
 ---------------------------------

 Expected to get some byteptr class, as I did in RubyCocoa. Got an error:

 Assertion failed: (ValueType->getTypeID() != VoidTyID && "Pointer to void
 is not valid, use i8* instead!"), function get, file Type.cpp, line 931.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/407>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 13:51:13 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 28 Oct 2009 20:51:13 -0000
Subject: [MacRuby-devel] [MacRuby] #407: NSData#bytes does not work
In-Reply-To: <050.559af3c3e56a737d39d62700d76b69ba@macosforge.org>
References: <050.559af3c3e56a737d39d62700d76b69ba@macosforge.org>
Message-ID: <059.9735d661bc1c4d0f2e29f7ab65484705@macosforge.org>

#407: NSData#bytes does not work
---------------------------------+------------------------------------------
 Reporter:  neeracher@?          |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  major                |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------
Description changed by neeracher@?:

Old description:

> MacRuby rev 2903.
>
> ---------------- Code ------------
> framework 'Cocoa'
>
> d = "xy".dataUsingEncoding(NSMacOSRomanStringEncoding)
> d.bytes
> ---------------------------------
>
> Expected to get some byteptr class, as I did in RubyCocoa. Got an error:
>
> Assertion failed: (ValueType->getTypeID() != VoidTyID && "Pointer to void
> is not valid, use i8* instead!"), function get, file Type.cpp, line 931.

New description:

 MacRuby rev 2903.

 ---------------- Code ------------
 framework 'Cocoa'

 d = "xy".dataUsingEncoding(NSMacOSRomanStringEncoding)[[BR]]
 d.bytes
 ---------------------------------

 Expected to get some byteptr class, as I did in RubyCocoa. Got an error:

 Assertion failed: (ValueType->getTypeID() != VoidTyID && "Pointer to void
 is not valid, use i8* instead!"), function get, file Type.cpp, line 931.

--

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/407#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 14:18:23 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 28 Oct 2009 21:18:23 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
Message-ID: <057.68b35a19efe0bfecc333d3d753f54441@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:                     |  
-------------------------------+--------------------------------------------

Comment(by cwdinfo@?):

 Same code and I get:

 {{{
 text field is qbc
 called completions #<NSRange:0x200368ae0> = 0 140734799798096
 "{140734799798096, 0}"
 }}}

 I can only get RUBY_VERSION, so I don't know exactly what version of
 MacRuby I'm running -- just the most recent nightly build on Snow Leopard
 10.6.1 x86_64.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:13>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 16:09:42 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 28 Oct 2009 23:09:42 -0000
Subject: [MacRuby-devel] [MacRuby] #408: leaked Tempfile don't get cleaned up
Message-ID: <050.add7e02be6f6ce5571f2c2cf5c12c200@macosforge.org>

#408: leaked Tempfile don't get cleaned up
---------------------------------+------------------------------------------
 Reporter:  neeracher@?          |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  minor                |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------
 macruby -e 'require "tempfile"; (0..1000).each {|i| p Tempfile.new("x")}'
 --------------
 fails after a few 100 files. Interestingly, this problem does not affect
 File:
 --------------
 macruby -e '(0..1000).each {|i| p File.new("x", "w")}'
 --------------
 ruby 1.8 runs both programs successfully. I have no 1.9 mainline install
 to test against.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/408>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 16:29:45 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 28 Oct 2009 23:29:45 -0000
Subject: [MacRuby-devel] [MacRuby] #408: leaked Tempfile don't get
	cleaned up
In-Reply-To: <050.add7e02be6f6ce5571f2c2cf5c12c200@macosforge.org>
References: <050.add7e02be6f6ce5571f2c2cf5c12c200@macosforge.org>
Message-ID: <059.45946c22d8bd17a62c47eb79f4db96f3@macosforge.org>

#408: leaked Tempfile don't get cleaned up
---------------------------------+------------------------------------------
 Reporter:  neeracher@?          |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  minor                |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------

Comment(by lsansonetti@?):

 Also run fine on 1.9.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/408#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 16:34:14 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Wed, 28 Oct 2009 23:34:14 -0000
Subject: [MacRuby-devel] [MacRuby] #409: Attribute setter should be accepted
	as KVO setter
Message-ID: <050.33a0371df802951a6ff2317cfe09a9fa@macosforge.org>

#409: Attribute setter should be accepted as KVO setter
---------------------------------+------------------------------------------
 Reporter:  neeracher@?          |       Owner:  lsansonetti@?        
     Type:  enhancement          |      Status:  new                  
 Priority:  minor                |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------
 MacRuby rev 2903:

 {{{
 class A
   attr_reader :a, :b
   def setA(value)
      @a = value
   end
   def b=(value)
      @b = value
   end
 end
 a = A.new
 a.setValue("hey", forKey:"a")
 p a
 a.setValue("yo", forKey:"b")
 p.a
 }}}

 It would be nice if the ruby style setter worked for KVO as well.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/409>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 19:57:57 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 29 Oct 2009 02:57:57 -0000
Subject: [MacRuby-devel] [MacRuby] #104: Problem with OpenSSL using
 MacRuby's internal conversion to and from NSData
In-Reply-To: <049.be69e860559b29dafc3ecfbbfc6470da@macosforge.org>
References: <049.be69e860559b29dafc3ecfbbfc6470da@macosforge.org>
Message-ID: <058.059d2093fa1dd13fd8b0727e064481e7@macosforge.org>

#104: Problem with OpenSSL using MacRuby's internal conversion to and from NSData
--------------------------------+-------------------------------------------
 Reporter:  rich@?              |        Owner:  lsansonetti@?        
     Type:  defect              |       Status:  closed               
 Priority:  blocker             |    Milestone:  MacRuby 0.5          
Component:  MacRuby             |   Resolution:  fixed                
 Keywords:                      |  
--------------------------------+-------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  MacRuby 0.4 => MacRuby 0.5


Comment:

 This seems to work as of r2915. The tmp.key file is properly generated. I
 don't know if the data is valid though. I'm closing the bug but please re-
 open it in case something is still not working.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/104#comment:3>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 20:06:33 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 29 Oct 2009 03:06:33 -0000
Subject: [MacRuby-devel] [MacRuby] #215: OpenSSL's SSLSocket appears not
 to be initialised correctly
In-Reply-To: <048.742693924250fbe57678a2130a56333a@macosforge.org>
References: <048.742693924250fbe57678a2130a56333a@macosforge.org>
Message-ID: <057.6c631584f458e7380b07ed5f58473f0a@macosforge.org>

#215: OpenSSL's SSLSocket appears not to be initialised correctly
-------------------------------+--------------------------------------------
 Reporter:  celtic@?           |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  major              |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:  openssl            |  
-------------------------------+--------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Looks like there was some iterations on this bug. However the IO layer
 changed a lot in 0.5, and as of r2915 it seems that the SSLSocket class is
 being "initialized" correctly (it does not crash).

 {{{
 $ macruby -r openssl -r net/http -r net/https -e "p
 OpenSSL::SSL::SSLSocket.new(nil) "
 core:in `initialize:': wrong argument type nil (expected File) (TypeError)
         from core:in `__new__:'
         from -e:1:in `<main>'
 }}}

 I was not able to find a different snippet by reading the attachments, so
 I'm closing the bug, if something doesn't work still please provide a
 proper bug reduction.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/215#comment:12>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 20:21:04 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 29 Oct 2009 03:21:04 -0000
Subject: [MacRuby-devel] [MacRuby] #139: Parsing bug
In-Reply-To: <049.f8d59de46eb2aedae931edb321ba81fc@macosforge.org>
References: <049.f8d59de46eb2aedae931edb321ba81fc@macosforge.org>
Message-ID: <058.98ad22328fb23fbbb4a44e79ce9be2ca@macosforge.org>

#139: Parsing bug
--------------------------------+-------------------------------------------
 Reporter:  mikael@?            |        Owner:  lsansonetti@?        
     Type:  defect              |       Status:  closed               
 Priority:  minor               |    Milestone:  MacRuby 0.5          
Component:  MacRuby             |   Resolution:  fixed                
 Keywords:  nil datasource      |  
--------------------------------+-------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  MacRuby 0.4 => MacRuby 0.5


Comment:

 This bug should be fixed since a long time, at least in 0.5 beta1.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/139#comment:3>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 21:02:44 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 29 Oct 2009 04:02:44 -0000
Subject: [MacRuby-devel] [MacRuby] #407: NSData#bytes does not work
In-Reply-To: <050.559af3c3e56a737d39d62700d76b69ba@macosforge.org>
References: <050.559af3c3e56a737d39d62700d76b69ba@macosforge.org>
Message-ID: <059.38effd92e08d116002ad2b1aa04f9785@macosforge.org>

#407: NSData#bytes does not work
---------------------------------+------------------------------------------
 Reporter:  neeracher@?          |        Owner:  lsansonetti@?        
     Type:  defect               |       Status:  closed               
 Priority:  major                |    Milestone:  MacRuby 0.5          
Component:  MacRuby              |   Resolution:  fixed                
 Keywords:                       |  
---------------------------------+------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Should be fixed by r2916:

 {{{
 $ ./miniruby -e "framework 'Foundation'; ptr =
 'hey'.dataUsingEncoding(NSMacOSRomanStringEncoding).bytes; p ptr[0].chr,
 ptr[1].chr, ptr[2].chr"
 "h"
 "e"
 "y"
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/407#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 21:15:02 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 29 Oct 2009 04:15:02 -0000
Subject: [MacRuby-devel] [MacRuby] #408: leaked Tempfile don't get
	cleaned up
In-Reply-To: <050.add7e02be6f6ce5571f2c2cf5c12c200@macosforge.org>
References: <050.add7e02be6f6ce5571f2c2cf5c12c200@macosforge.org>
Message-ID: <059.53c8ce71a0fd94125d1457544c36443e@macosforge.org>

#408: leaked Tempfile don't get cleaned up
---------------------------------+------------------------------------------
 Reporter:  neeracher@?          |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  minor                |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------

Comment(by lsansonetti@?):

 Looks like lib/tempfile.rb uses ObjectSpace.define_finalizer to register a
 block that will close the file. Since ObjectSpace.define_finalizer is not
 implemented yet in trunk, the file is never closed/removed.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/408#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 22:47:02 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 29 Oct 2009 05:47:02 -0000
Subject: [MacRuby-devel] [MacRuby] #408: leaked Tempfile don't get
	cleaned up
In-Reply-To: <050.add7e02be6f6ce5571f2c2cf5c12c200@macosforge.org>
References: <050.add7e02be6f6ce5571f2c2cf5c12c200@macosforge.org>
Message-ID: <059.c9cfc69d2b4c486f78cdf415c6eba044@macosforge.org>

#408: leaked Tempfile don't get cleaned up
---------------------------------+------------------------------------------
 Reporter:  neeracher@?          |        Owner:  lsansonetti@?        
     Type:  defect               |       Status:  closed               
 Priority:  minor                |    Milestone:  MacRuby 0.5          
Component:  MacRuby              |   Resolution:  fixed                
 Keywords:                       |  
---------------------------------+------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 I implemented ObjectSpace finalizers as part of r2918 and now your snippet
 behaves like the old Ruby. It's an experimental implementation and
 finalizers might potentially be called from foreign threads, so developers
 should be careful.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/408#comment:3>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 23:07:43 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 29 Oct 2009 06:07:43 -0000
Subject: [MacRuby-devel] [MacRuby] #133: Cannot install soap4r gem using
	macgem
In-Reply-To: <053.60f64cfcbf99a0caaa48dfacca773378@macosforge.org>
References: <053.60f64cfcbf99a0caaa48dfacca773378@macosforge.org>
Message-ID: <062.db0a0f5e17bfcbbb9b3df15e5ffd326f@macosforge.org>

#133: Cannot install soap4r gem using macgem
------------------------------------+---------------------------------------
 Reporter:  rebotfc@?               |        Owner:  lsansonetti@?        
     Type:  defect                  |       Status:  closed               
 Priority:  major                   |    Milestone:  MacRuby 0.5          
Component:  MacRuby                 |   Resolution:  fixed                
 Keywords:  macgem                  |  
------------------------------------+---------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 As of r2918, it seems to be installable.

 {{{
 $ macgem install soap4r
 WARNING:  Installing to ~/.gem since
 /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0
 and
           /usr/bin aren't both writable.
 WARNING:  You don't have /Users/lrz/.gem/macruby/1.9.0/bin in your PATH,
           gem executables will not run.
 Successfully installed httpclient-2.1.5.2
 Successfully installed soap4r-1.5.8
 2 gems installed
 }}}

 It may not fully work though, feel free to file a new bug if you find
 something.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/133#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 23:23:48 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 29 Oct 2009 06:23:48 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
Message-ID: <057.85f58ee0f874e6a16e6c6a722b042a2c@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:                     |  
-------------------------------+--------------------------------------------

Comment(by mattaimonetti@?):

 I tried your second example using trunk form today and everything worked
 for me:

 {{{
 text field is macruby is awesome
 called completions #<NSRange:0x200383b00> = 7 11
 }}}

 So, I believe this is fixed on trunkt.
 Feel free to give another try and reopen this ticket if needed.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:14>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Wed Oct 28 23:25:21 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 29 Oct 2009 06:25:21 -0000
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
Message-ID: <057.2fecb3528b7b8919e7691501a974af1b@macosforge.org>

#394: Unrecognized runtime type _NSRange=II
-------------------------------+--------------------------------------------
 Reporter:  cwdinfo@?          |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:                     |  
-------------------------------+--------------------------------------------

Comment(by lsansonetti@?):

 Maybe the fix didn't get into the nightly build, I will test with the
 latest one tomorrow.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:15>
MacRuby <http://macruby.org/>


From ruben at 0x82.com  Thu Oct 29 02:27:19 2009
From: ruben at 0x82.com (Ruben Fonseca)
Date: Thu, 29 Oct 2009 09:27:19 +0000
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com>
	<983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
Message-ID: <13EB4DB2-5E65-46F8-B1DF-8C3E8662FBF2@0x82.com>

Hi Laurent!

On Oct 28, 2009, at 12:31 AM, Laurent Sansonetti wrote:

> and to wrap this C API into an Objective-C class that you can call  
> from MacRuby in the meantime.
>
> Laurent

Just a quick question. Imagine I have an Objective-C class that wraps  
that API. How can I then use it on a Macruby script? I probably have  
to compile it somewhere...

Ruben

From al_skipp at fastmail.fm  Thu Oct 29 04:43:23 2009
From: al_skipp at fastmail.fm (Alan Skipp)
Date: Thu, 29 Oct 2009 11:43:23 +0000
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <13EB4DB2-5E65-46F8-B1DF-8C3E8662FBF2@0x82.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com><983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
	<13EB4DB2-5E65-46F8-B1DF-8C3E8662FBF2@0x82.com>
Message-ID: <1256816603.30500.1342565757@webmail.messagingengine.com>

It's really simple, you just need to create an Objective-C class in your
macruby application (header and implementation file). You can then use
it in your ruby code without any hassle, it's great. For example, if you
create an Objective-C class called 'MetaDataHelper', you can use it like
this:
helper = MetaDataHelper.new

and call methods on it like any other ruby object, eg:

metadata = helper.metadataForFile('/path/to/file/')

I can post a code example later today, if that would be helpful.



On Thu, 29 Oct 2009 09:27 +0000, "Ruben Fonseca" <ruben at 0x82.com> wrote:
> Hi Laurent!
> 
> On Oct 28, 2009, at 12:31 AM, Laurent Sansonetti wrote:
> 
> > and to wrap this C API into an Objective-C class that you can call  
> > from MacRuby in the meantime.
> >
> > Laurent
> 
> Just a quick question. Imagine I have an Objective-C class that wraps  
> that API. How can I then use it on a Macruby script? I probably have  
> to compile it somewhere...
> 
> Ruben
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
-- 
  Alan Skipp
  al_skipp at fastmail.fm

-- 
http://www.fastmail.fm - One of many happy users:
  http://www.fastmail.fm/docs/quotes.html


From ruby-noreply at macosforge.org  Thu Oct 29 06:03:02 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 29 Oct 2009 13:03:02 -0000
Subject: [MacRuby-devel] [MacRuby] #391: HotCocoa on_notification method
 stopped functioning in MacRuby 0.5 under Snow Leopard
In-Reply-To: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
References: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
Message-ID: <064.aef3b9bc253f907176b5b6582513d6e2@macosforge.org>

#391: HotCocoa on_notification method stopped functioning in MacRuby 0.5 under
Snow Leopard
--------------------------------------+-------------------------------------
 Reporter:  trevor@?                  |       Owner:  lsansonetti@?           
     Type:  defect                    |      Status:  new                     
 Priority:  blocker                   |   Milestone:                          
Component:  MacRuby                   |    Keywords:  HotCocoa on_notification
--------------------------------------+-------------------------------------

Comment(by hoffmann@?):

 # OS X 10.6.1
 # MacRuby 0.5 beta 1
 # MacRuby macruby_nightly-2009-10-28-1306.pkg

 # Simple script:

 require 'hotcocoa'
 include HotCocoa

 application do
  on_notification :named => 'NSWindowDidResizeNotification' do |
  notification|
    puts "A window resized!"
  end
 end

 # ERROR LOG:
 # 2009-10-29 13:54:05.667 macruby[11291:903]
 __CFServiceControllerBeginPBSLoadForLocalizations timed out while talking
 to pbs

 regards,

 Robert

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/391#comment:3>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 29 06:44:02 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 29 Oct 2009 13:44:02 -0000
Subject: [MacRuby-devel] [MacRuby] #410: Readline merge to the recent
	CRuby's.
Message-ID: <047.c2cc28060fed1350fb100e17eb29a9f9@macosforge.org>

#410: Readline merge to the recent CRuby's.
------------------------------+---------------------------------------------
 Reporter:  kouji@?           |       Owner:  lsansonetti@?        
     Type:  enhancement       |      Status:  new                  
 Priority:  blocker           |   Milestone:  MacRuby 0.5          
Component:  MacRuby           |    Keywords:  Readline             
------------------------------+---------------------------------------------
 Hi,

 I am the CRuby's Readline module maintainer.

 I created the patch for MacRuby's Readline module to merge it to the
 recent CRuby's.

 I checked it by spec.


 {{{
 $ ./mspec/bin/mspec run -B ./spec/macruby.mspec
 spec/frozen/library/readline
 MacRuby version 0.5 (ruby 1.9.0) [universal-darwin9.0, x86_64]
 ...................................................

 Finished in 1.079747 seconds

 25 files, 31 examples, 95 expectations, 0 failures, 0 errors
 }}}

 Thank you.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/410>
MacRuby <http://macruby.org/>


From ruben at 0x82.com  Thu Oct 29 08:44:56 2009
From: ruben at 0x82.com (Ruben Fonseca)
Date: Thu, 29 Oct 2009 15:44:56 +0000
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com>
	<983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
Message-ID: <23407BC3-B710-43FD-B958-3A779753C6A2@0x82.com>

Hi Laurent. Just a quick question.

On Oct 28, 2009, at 12:31 AM, Laurent Sansonetti wrote:

> Hi Alan,
>
> I'm afraid the MD* APIs haven't been covered by BridgeSupport yet,  
> so it may not be possible to call it directly from MacRuby at this  
> point. I would recommend to file a bug at http:// 
> bugreporter.apple.com so that we can consider this for a future Mac  
> OS X release, and to wrap this C API into an Objective-C class that  
> you can call from MacRuby in the meantime.
>
> Laurent

Does it make any sense to write wrappers to APIs not covered by  
BridgeSupport and bundle them in Macruby? (Isn't GCD such a case?).

If that's the case, I can help with writing some of these wrappers.

Ruben

From ruben at 0x82.com  Thu Oct 29 08:48:10 2009
From: ruben at 0x82.com (Ruben Fonseca)
Date: Thu, 29 Oct 2009 15:48:10 +0000
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <1256816603.30500.1342565757@webmail.messagingengine.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com><983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
	<13EB4DB2-5E65-46F8-B1DF-8C3E8662FBF2@0x82.com>
	<1256816603.30500.1342565757@webmail.messagingengine.com>
Message-ID: <EEED062A-7000-4DFF-9A40-FE84F1166415@0x82.com>

Hi Alan!

Thank you, that's very simple.

However I'm still curious about the daily non-Xcode scripts.

Image I want to write a macruby script that uses my Objective-C helper  
class. What's the easiest way to accomplish that outside XCode?

Ruben

On Oct 29, 2009, at 11:43 AM, Alan Skipp wrote:

> It's really simple, you just need to create an Objective-C class in  
> your
> macruby application (header and implementation file). You can then use
> it in your ruby code without any hassle, it's great. For example, if  
> you
> create an Objective-C class called 'MetaDataHelper', you can use it  
> like
> this:
> helper = MetaDataHelper.new
>
> and call methods on it like any other ruby object, eg:
>
> metadata = helper.metadataForFile('/path/to/file/')
>
> I can post a code example later today, if that would be helpful.

From ruben at 0x82.com  Thu Oct 29 09:24:10 2009
From: ruben at 0x82.com (Ruben Fonseca)
Date: Thu, 29 Oct 2009 16:24:10 +0000
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <1256816603.30500.1342565757@webmail.messagingengine.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com><983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
	<13EB4DB2-5E65-46F8-B1DF-8C3E8662FBF2@0x82.com>
	<1256816603.30500.1342565757@webmail.messagingengine.com>
Message-ID: <6C4DF82F-4FE2-411D-B12D-8A19DB2CBB54@0x82.com>

Hi Alan!

Thank you, that's very simple.

However I'm still curious about the daily non-Xcode scripts.

Image I want to write a macruby script that uses my Objective-C helper  
class. What's the easiest way to accomplish that outside XCode?

Ruben

On Oct 29, 2009, at 11:43 AM, Alan Skipp wrote:

> It's really simple, you just need to create an Objective-C class in  
> your
> macruby application (header and implementation file). You can then use
> it in your ruby code without any hassle, it's great. For example, if  
> you
> create an Objective-C class called 'MetaDataHelper', you can use it  
> like
> this:
> helper = MetaDataHelper.new
>
> and call methods on it like any other ruby object, eg:
>
> metadata = helper.metadataForFile('/path/to/file/')
>
> I can post a code example later today, if that would be helpful.

From jazzbox at 7zz.de  Thu Oct 29 09:46:42 2009
From: jazzbox at 7zz.de (B. Ohr)
Date: Thu, 29 Oct 2009 17:46:42 +0100
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <EEED062A-7000-4DFF-9A40-FE84F1166415@0x82.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com><983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
	<13EB4DB2-5E65-46F8-B1DF-8C3E8662FBF2@0x82.com>
	<1256816603.30500.1342565757@webmail.messagingengine.com>
	<EEED062A-7000-4DFF-9A40-FE84F1166415@0x82.com>
Message-ID: <62033956-250A-4925-AB27-5E61D4B1C08A@7zz.de>


Hi Ruben!

>
> However I'm still curious about the daily non-Xcode scripts.
>
> Image I want to write a macruby script that uses my Objective-C  
> helper class. What's the easiest way to accomplish that outside XCode?
>
> Ruben

Like you I played around a little with this issue. My current state is:

If you have a MacRuby helper named foo.rb you can simply compile it  
like that

macrubyc -V --arch x86_64 -C "foo.rb" -o "foo.rbo"

This "foo.rbo" can be included in another script via require.

If you have an ObjC you can compile it with

gcc -c foo.m -o foo1.o -fobjc-gc

but I failed to convert that foo1.o to an .rbo file. I tried some  
macrubyc options but none of them is working.

On the other side making an .o out of a .rb is no problem:

macrubyc -V --arch x86_64 -c "foo.rb" -o "foo.o"

So I think, there is just one step missing in the options in macrubyc  
(or I am unable to read the source).

Bernd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091029/b0c92bad/attachment.html>

From cwdinfo at gmail.com  Thu Oct 29 10:25:35 2009
From: cwdinfo at gmail.com (s.ross)
Date: Thu, 29 Oct 2009 10:25:35 -0700
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
	_NSRange=II
In-Reply-To: <057.2fecb3528b7b8919e7691501a974af1b@macosforge.org>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
	<057.2fecb3528b7b8919e7691501a974af1b@macosforge.org>
Message-ID: <A2669EB4-D140-46E6-B470-9911185BFFE9@gmail.com>

On Oct 28, 2009, at 11:25 PM, MacRuby wrote:

> #394: Unrecognized runtime type _NSRange=II
> ------------------------------- 
> +--------------------------------------------
> Reporter:  cwdinfo@?          |        Owner:  lsansonetti@?
>     Type:  defect             |       Status:  closed
> Priority:  blocker            |    Milestone:  MacRuby 0.5
> Component:  MacRuby            |   Resolution:  fixed
> Keywords:                     |
> ------------------------------- 
> +--------------------------------------------
>
> Comment(by lsansonetti@?):
>
> Maybe the fix didn't get into the nightly build, I will test with the
> latest one tomorrow.
>
> -- 
> Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:15>
> MacRuby <http://macruby.org/>
>

It got into the most recent nightly build. Thanks so much.

Is there a way to compare the version number against the one packaged  
for the nightly build?

From joshua.ballanco at apple.com  Thu Oct 29 10:48:44 2009
From: joshua.ballanco at apple.com (Josh Ballanco)
Date: Thu, 29 Oct 2009 10:48:44 -0700
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <13EB4DB2-5E65-46F8-B1DF-8C3E8662FBF2@0x82.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com>
	<983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
	<13EB4DB2-5E65-46F8-B1DF-8C3E8662FBF2@0x82.com>
Message-ID: <34EA88DB-3AB5-49B6-9138-FEDD74E6DF93@apple.com>

Hi Ruben,

Using an Objective-C class in a MacRuby script is the first step in  
both recipes currently posted to the MacRuby website (http://www.macruby.org/documentation.html 
). Your choices are either to add a "dummy" Init_foo{} function and  
make a foo.bundle from the class or compile the Objective-C files to a  
foo.framework and then either put the framework in a well known  
location (like /Library/Frameworks) or modify the DYLD_FRAMEWORK_PATH  
before running your MacRuby script.

If you want more details on wrapping C API, I am currently working on  
just such a project, and might be able to put together another recipe.  
What sort of information would you be looking for specifically? Is  
there a particular C API you'd be interested in seeing how to wrap?

Finally, as to your later question, there actually *is* a MacRuby API  
for GCD currently in the 0.5 beta and nightly builds.

Cheers,

Josh


On Oct 29, 2009, at 2:27 AM, Ruben Fonseca wrote:

> Hi Laurent!
>
> On Oct 28, 2009, at 12:31 AM, Laurent Sansonetti wrote:
>
>> and to wrap this C API into an Objective-C class that you can call  
>> from MacRuby in the meantime.
>>
>> Laurent
>
> Just a quick question. Imagine I have an Objective-C class that  
> wraps that API. How can I then use it on a Macruby script? I  
> probably have to compile it somewhere...
>
> Ruben
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruben at 0x82.com  Thu Oct 29 11:07:02 2009
From: ruben at 0x82.com (Ruben Fonseca)
Date: Thu, 29 Oct 2009 18:07:02 +0000
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <34EA88DB-3AB5-49B6-9138-FEDD74E6DF93@apple.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com>
	<983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
	<13EB4DB2-5E65-46F8-B1DF-8C3E8662FBF2@0x82.com>
	<34EA88DB-3AB5-49B6-9138-FEDD74E6DF93@apple.com>
Message-ID: <086E7B8D-E537-48C6-9174-84C5CD2A79F5@0x82.com>

Hi Josh!

On Oct 29, 2009, at 5:48 PM, Josh Ballanco wrote:

> Hi Ruben,
>
> Using an Objective-C class in a MacRuby script is the first step in  
> both recipes currently posted to the MacRuby website (http://www.macruby.org/documentation.html 
> ). Your choices are either to add a "dummy" Init_foo{} function and  
> make a foo.bundle from the class or compile the Objective-C files to  
> a foo.framework and then either put the framework in a well known  
> location (like /Library/Frameworks) or modify the  
> DYLD_FRAMEWORK_PATH before running your MacRuby script.

Perfect! I read both recipes and it seems pretty easy :) Thank you!

> If you want more details on wrapping C API, I am currently working  
> on just such a project, and might be able to put together another  
> recipe. What sort of information would you be looking for  
> specifically? Is there a particular C API you'd be interested in  
> seeing how to wrap?

Actually I was offering my time and help to create those wrappers :) I  
don't have any need for a particular C API right now...

> Finally, as to your later question, there actually *is* a MacRuby  
> API for GCD currently in the 0.5 beta and nightly builds.

Yes I know. That's why I've asked if it makes sense to include more  
wrappers to other C APIs into Macruby!

Cheers
Ruben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091029/57118c35/attachment-0001.html>

From neeracher at apple.com  Thu Oct 29 12:09:49 2009
From: neeracher at apple.com (Matthias Neeracher)
Date: Thu, 29 Oct 2009 20:09:49 +0100
Subject: [MacRuby-devel] [MacRuby] #407: NSData#bytes does not work
	(MacRuby)
In-Reply-To: <mailman.8296.1256821385.77573.macruby-devel@lists.macosforge.org>
References: <mailman.8296.1256821385.77573.macruby-devel@lists.macosforge.org>
Message-ID: <D77D4552-FCCF-43B4-BB8A-CAAC51E6B289@apple.com>

> #407: NSData#bytes does not work
[...]
> Changes (by lsansonetti@?):

> Comment:
>
> Should be fixed by r2916:

It is indeed fixed, thank you! My initial purpose for this was to get  
the data out of an NSData, which in RubyCocoa was

data.bytes.bytestr(data.length)

It seems the MacRuby "Pointer" class no longer has a bytestr method,  
so this no longer works, but

a) CFDataGetBytePtr(data) works and
b) The original reason for creating a CFData (converting a string to a  
particular encoding) can be achieved much more easily in ruby 1.9 with  
regular string methods, so my reason for creating an NSData is moot in  
the first place.

Matthias


From neeracher at apple.com  Thu Oct 29 12:18:20 2009
From: neeracher at apple.com (Matthias Neeracher)
Date: Thu, 29 Oct 2009 20:18:20 +0100
Subject: [MacRuby-devel] [MacRuby] #408: leaked Tempfile don't
	get	cleaned up (MacRuby)
In-Reply-To: <mailman.8296.1256821385.77573.macruby-devel@lists.macosforge.org>
References: <mailman.8296.1256821385.77573.macruby-devel@lists.macosforge.org>
Message-ID: <01C6D7B9-E6BB-4AB7-80D6-C85F3550B5B4@apple.com>

> #408: leaked Tempfile don't get cleaned up
[...]
> Changes (by lsansonetti@?):
>
>  * status:  new => closed
>  * resolution:  => fixed
>
> I implemented ObjectSpace finalizers as part of r2918 and now your  
> snippet
> behaves like the old Ruby.

This does indeed fix the main problem?the program running out of file  
descriptors. Thanks!

The behavior still differs significantly from Ruby 1.8 behavior  
(though it may match 1.9 this regard): When running the program I  
included in the bug to completion, the ruby 1.8 version will clean up  
all temp files, while the MacRuby version will leave behind dozens of  
temp files (everything created after the last gc run). Presumably, one  
could force this cleanup by running gc at the end of the program, but  
I'm not sure this would be a popular thing to do in the runtime, and  
if it matters to a client, this can be done in client code.

Matthias
  

From lsansonetti at apple.com  Thu Oct 29 12:26:05 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 29 Oct 2009 12:26:05 -0700
Subject: [MacRuby-devel] [MacRuby] #394: Unrecognized runtime type
 _NSRange=II
In-Reply-To: <A2669EB4-D140-46E6-B470-9911185BFFE9@gmail.com>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
	<057.2fecb3528b7b8919e7691501a974af1b@macosforge.org>
	<A2669EB4-D140-46E6-B470-9911185BFFE9@gmail.com>
Message-ID: <22A2C780-6DC5-40B5-A3B7-A05E56F53E2E@apple.com>

On Oct 29, 2009, at 10:25 AM, s.ross wrote:

> On Oct 28, 2009, at 11:25 PM, MacRuby wrote:
>
>> #394: Unrecognized runtime type _NSRange=II
>> ------------------------------- 
>> +--------------------------------------------
>> Reporter:  cwdinfo@?          |        Owner:  lsansonetti@?
>>    Type:  defect             |       Status:  closed
>> Priority:  blocker            |    Milestone:  MacRuby 0.5
>> Component:  MacRuby            |   Resolution:  fixed
>> Keywords:                     |
>> ------------------------------- 
>> +--------------------------------------------
>>
>> Comment(by lsansonetti@?):
>>
>> Maybe the fix didn't get into the nightly build, I will test with the
>> latest one tomorrow.
>>
>> -- 
>> Ticket URL: <http://www.macruby.org/trac/ticket/394#comment:15>
>> MacRuby <http://macruby.org/>
>>
>
> It got into the most recent nightly build. Thanks so much.

Excellent :)

> Is there a way to compare the version number against the one  
> packaged for the nightly build?

We define the MACRUBY_REVISION constant that you could use.

$ macruby -e "p MACRUBY_REVISION"
"svn revision 2915 from http://svn.macosforge.org/repository/ruby/MacRuby/trunk 
"

If MacRuby was built from Git (I think that's what the nightly build  
does), the constant will have the full Git line (with the sha1  
signature).

Laurent

From lsansonetti at apple.com  Thu Oct 29 12:29:43 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 29 Oct 2009 12:29:43 -0700
Subject: [MacRuby-devel] [MacRuby] #408: leaked Tempfile
 don't	get	cleaned up (MacRuby)
In-Reply-To: <01C6D7B9-E6BB-4AB7-80D6-C85F3550B5B4@apple.com>
References: <mailman.8296.1256821385.77573.macruby-devel@lists.macosforge.org>
	<01C6D7B9-E6BB-4AB7-80D6-C85F3550B5B4@apple.com>
Message-ID: <DB75E9EF-1A6E-4AC2-AD07-C25AA36C5FE7@apple.com>

On Oct 29, 2009, at 12:18 PM, Matthias Neeracher wrote:
>> #408: leaked Tempfile don't get cleaned up
> [...]
>> Changes (by lsansonetti@?):
>>
>> * status:  new => closed
>> * resolution:  => fixed
>>
>> I implemented ObjectSpace finalizers as part of r2918 and now your  
>> snippet
>> behaves like the old Ruby.
>
> This does indeed fix the main problem?the program running out of  
> file descriptors. Thanks!
>
> The behavior still differs significantly from Ruby 1.8 behavior  
> (though it may match 1.9 this regard): When running the program I  
> included in the bug to completion, the ruby 1.8 version will clean  
> up all temp files, while the MacRuby version will leave behind  
> dozens of temp files (everything created after the last gc run).  
> Presumably, one could force this cleanup by running gc at the end of  
> the program, but I'm not sure this would be a popular thing to do in  
> the runtime, and if it matters to a client, this can be done in  
> client code.

I think this is a different bug, it looks like we don't force the call  
of all finalizers before dying.

$ ./miniruby -e "o=Object.new; ObjectSpace.define_finalizer(o, proc{p  
42}); p :dying"
:dying
$ ruby19 -e "o=Object.new; ObjectSpace.define_finalizer(o, proc{p  
42}); p :dying"
:dying
42

I remember we trigger a full - synchronous collection before exiting  
but apparently it doesn't help.

Could you file a new ticket on Trac for this?

Thanks,

Laurent

From prabhaka at apple.com  Thu Oct 29 12:39:52 2009
From: prabhaka at apple.com (Ernest N. Prabhakar, Ph.D.)
Date: Thu, 29 Oct 2009 12:39:52 -0700
Subject: [MacRuby-devel] MACRUBY_REVISION
In-Reply-To: <22A2C780-6DC5-40B5-A3B7-A05E56F53E2E@apple.com>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
	<057.2fecb3528b7b8919e7691501a974af1b@macosforge.org>
	<A2669EB4-D140-46E6-B470-9911185BFFE9@gmail.com>
	<22A2C780-6DC5-40B5-A3B7-A05E56F53E2E@apple.com>
Message-ID: <98A8F345-E73F-4E18-B586-579EC5AD1BDF@apple.com>

Hi Laurent,

On Oct 29, 2009, at 12:26 PM, Laurent Sansonetti wrote:

> $ macruby -e "p MACRUBY_REVISION"
> "svn revision 2915 from http://svn.macosforge.org/repository/ruby/MacRuby/trunk"
> 
> If MacRuby was built from Git (I think that's what the nightly build does), the constant will have the full Git line (with the sha1 signature).
> 

Apparently not:

> prabhaka$ macruby -e "p MACRUBY_REVISION"
> "unknown revision"

-enp

From ruby-noreply at macosforge.org  Thu Oct 29 12:40:50 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 29 Oct 2009 19:40:50 -0000
Subject: [MacRuby-devel] [MacRuby] #410: Readline merge to the recent
	CRuby's.
In-Reply-To: <047.c2cc28060fed1350fb100e17eb29a9f9@macosforge.org>
References: <047.c2cc28060fed1350fb100e17eb29a9f9@macosforge.org>
Message-ID: <056.06b85f85e7a27093417c96293da885dc@macosforge.org>

#410: Readline merge to the recent CRuby's.
------------------------------+---------------------------------------------
 Reporter:  kouji@?           |        Owner:  lsansonetti@?        
     Type:  enhancement       |       Status:  closed               
 Priority:  blocker           |    Milestone:  MacRuby 0.5          
Component:  MacRuby           |   Resolution:  fixed                
 Keywords:  Readline          |  
------------------------------+---------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Thanks a lot kouji-san! I slightly modified the patch:

 rb_f_notimplement was implemented in MacRuby trunk a few days ago (no need
 to define it anymore).

 line 1492 of readline.c, I had to change the assignment from

 {{{
     rl_getc_function = (Function *) readline_getc
 }}}

 to

 {{{
     rl_getc_function = (int (*)(FILE *))readline_getc;
 }}}

 Otherwise a warning is generated by the compiler. Mac OS X uses libedit as
 the default readline implementation, and in
 /usr/include/editline/readline.h the rl_getc_function variable is defined
 as

 {{{
 extern int              (*rl_getc_function)(FILE *);
 }}}

 But Function is

 {{{
 typedef int       Function(const char *, int);
 }}}

 I didn't check with GNU readline.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/410#comment:1>
MacRuby <http://macruby.org/>


From lsansonetti at apple.com  Thu Oct 29 12:42:48 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 29 Oct 2009 12:42:48 -0700
Subject: [MacRuby-devel] MACRUBY_REVISION
In-Reply-To: <98A8F345-E73F-4E18-B586-579EC5AD1BDF@apple.com>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
	<057.2fecb3528b7b8919e7691501a974af1b@macosforge.org>
	<A2669EB4-D140-46E6-B470-9911185BFFE9@gmail.com>
	<22A2C780-6DC5-40B5-A3B7-A05E56F53E2E@apple.com>
	<98A8F345-E73F-4E18-B586-579EC5AD1BDF@apple.com>
Message-ID: <021BB72C-901A-4751-9AF1-FC2D752C420D@apple.com>

On Oct 29, 2009, at 12:39 PM, Ernest N. Prabhakar, Ph.D. wrote:

> Hi Laurent,
>
> On Oct 29, 2009, at 12:26 PM, Laurent Sansonetti wrote:
>
>> $ macruby -e "p MACRUBY_REVISION"
>> "svn revision 2915 from http://svn.macosforge.org/repository/ruby/MacRuby/trunk 
>> "
>>
>> If MacRuby was built from Git (I think that's what the nightly  
>> build does), the constant will have the full Git line (with the  
>> sha1 signature).
>>
>
> Apparently not:
>
>> prabhaka$ macruby -e "p MACRUBY_REVISION"
>> "unknown revision"

Where does your version of MacRuby come from? :-)

Laurent

From prabhaka at apple.com  Thu Oct 29 12:48:36 2009
From: prabhaka at apple.com (Ernest N. Prabhakar, Ph.D.)
Date: Thu, 29 Oct 2009 12:48:36 -0700
Subject: [MacRuby-devel] MACRUBY_REVISION
In-Reply-To: <021BB72C-901A-4751-9AF1-FC2D752C420D@apple.com>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
	<057.2fecb3528b7b8919e7691501a974af1b@macosforge.org>
	<A2669EB4-D140-46E6-B470-9911185BFFE9@gmail.com>
	<22A2C780-6DC5-40B5-A3B7-A05E56F53E2E@apple.com>
	<98A8F345-E73F-4E18-B586-579EC5AD1BDF@apple.com>
	<021BB72C-901A-4751-9AF1-FC2D752C420D@apple.com>
Message-ID: <C9B90310-AF4E-4D83-8798-A42ADCAB52FA@apple.com>

Hi Laurent,

On Oct 29, 2009, at 12:42 PM, Laurent Sansonetti wrote:
> On Oct 29, 2009, at 12:39 PM, Ernest N. Prabhakar, Ph.D. wrote:
> 
>> Hi Laurent,
>> 
>> On Oct 29, 2009, at 12:26 PM, Laurent Sansonetti wrote:
>> 
>>> $ macruby -e "p MACRUBY_REVISION"
>>> "svn revision 2915 from http://svn.macosforge.org/repository/ruby/MacRuby/trunk"
>>> 
>>> If MacRuby was built from Git (I think that's what the nightly build does), the constant will have the full Git line (with the sha1 signature).
>>> 
>> 
>> Apparently not:
>> 
>>> prabhaka$ macruby -e "p MACRUBY_REVISION"
>>> "unknown revision"
> 
> Where does your version of MacRuby come from? :-)

I'm pretty sure this was the latest nightly, installed using:


-------------- next part --------------
A non-text attachment was scrubbed...
Name: macruby_get_nightly.command
Type: application/octet-stream
Size: 327 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091029/b140390b/attachment-0001.obj>
-------------- next part --------------


-enp

From joshua.ballanco at apple.com  Thu Oct 29 12:54:32 2009
From: joshua.ballanco at apple.com (Josh Ballanco)
Date: Thu, 29 Oct 2009 12:54:32 -0700
Subject: [MacRuby-devel] MACRUBY_REVISION
In-Reply-To: <C9B90310-AF4E-4D83-8798-A42ADCAB52FA@apple.com>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
	<057.2fecb3528b7b8919e7691501a974af1b@macosforge.org>
	<A2669EB4-D140-46E6-B470-9911185BFFE9@gmail.com>
	<22A2C780-6DC5-40B5-A3B7-A05E56F53E2E@apple.com>
	<98A8F345-E73F-4E18-B586-579EC5AD1BDF@apple.com>
	<021BB72C-901A-4751-9AF1-FC2D752C420D@apple.com>
	<C9B90310-AF4E-4D83-8798-A42ADCAB52FA@apple.com>
Message-ID: <6827EB79-C933-478F-A315-9E3180D3448C@apple.com>

On Oct 29, 2009, at 12:48 PM, Ernest N. Prabhakar, Ph.D. wrote:

> Hi Laurent,
>
> On Oct 29, 2009, at 12:42 PM, Laurent Sansonetti wrote:
>> On Oct 29, 2009, at 12:39 PM, Ernest N. Prabhakar, Ph.D. wrote:
>>
>>> Hi Laurent,
>>>
>>> On Oct 29, 2009, at 12:26 PM, Laurent Sansonetti wrote:
>>>
>>>> $ macruby -e "p MACRUBY_REVISION"
>>>> "svn revision 2915 from http://svn.macosforge.org/repository/ruby/MacRuby/trunk 
>>>> "
>>>>
>>>> If MacRuby was built from Git (I think that's what the nightly  
>>>> build does), the constant will have the full Git line (with the  
>>>> sha1 signature).
>>>>
>>>
>>> Apparently not:
>>>
>>>> prabhaka$ macruby -e "p MACRUBY_REVISION"
>>>> "unknown revision"
>>
>> Where does your version of MacRuby come from? :-)
>
> I'm pretty sure this was the latest nightly, installed using:
>

Git will require an extra Attribute to properly do version  
substitution. See the section on "export-subst" in the Pro Git book: http://progit.org/book/ch7-2.html

- Josh

From ruby-noreply at macosforge.org  Thu Oct 29 12:56:36 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 29 Oct 2009 19:56:36 -0000
Subject: [MacRuby-devel] [MacRuby] #411: MacRuby does not force call to
	finalizers
Message-ID: <050.5c6b5e5e7dce70393440dc067fdf1822@macosforge.org>

#411: MacRuby does not force call to finalizers
---------------------------------+------------------------------------------
 Reporter:  neeracher@?          |       Owner:  lsansonetti@?        
     Type:  defect               |      Status:  new                  
 Priority:  blocker              |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------
 Per our discussion on macruby-devel:

 {{{
 macruby -e "o=Object.new; ObjectSpace.define_finalizer(o, proc{p
 42}); p :dying"
 }}}

 This calls the finalizer on other ruby platforms, but not on current
 Macruby

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/411>
MacRuby <http://macruby.org/>


From joshua.ballanco at apple.com  Thu Oct 29 12:57:11 2009
From: joshua.ballanco at apple.com (Josh Ballanco)
Date: Thu, 29 Oct 2009 12:57:11 -0700
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <086E7B8D-E537-48C6-9174-84C5CD2A79F5@0x82.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com>
	<983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
	<13EB4DB2-5E65-46F8-B1DF-8C3E8662FBF2@0x82.com>
	<34EA88DB-3AB5-49B6-9138-FEDD74E6DF93@apple.com>
	<086E7B8D-E537-48C6-9174-84C5CD2A79F5@0x82.com>
Message-ID: <BA3AA5B2-B29D-4BDA-A238-639031D805FA@apple.com>

Hi Ruben,

On Oct 29, 2009, at 11:07 AM, Ruben Fonseca wrote:

>> Finally, as to your later question, there actually *is* a MacRuby  
>> API for GCD currently in the 0.5 beta and nightly builds.
>
> Yes I know. That's why I've asked if it makes sense to include more  
> wrappers to other C APIs into Macruby!

Ah, my mistake. I misread your e-mail. So, actually the MacRuby GCD  
implementation isn't an Obj-C wrapper but rather a "baked-in" C  
wrapper around the C-level GCD API. As for whether it makes sense to  
include more wrappers, I would say "Yes! Definitely!". But, it's  
important to remember that these wrappers wouldn't just be MacRuby  
wrappers, they would also work as Obj-C wrappers for developers  
working with regular Obj-C Cocoa. So, if you'd like to get started,  
maybe the best thing to do would be to check with some Cocoa devs and  
see what C APIs they would like wrapped.

Cheers,

Josh

From lsansonetti at apple.com  Thu Oct 29 13:14:11 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 29 Oct 2009 13:14:11 -0700
Subject: [MacRuby-devel] MACRUBY_REVISION
In-Reply-To: <6827EB79-C933-478F-A315-9E3180D3448C@apple.com>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
	<057.2fecb3528b7b8919e7691501a974af1b@macosforge.org>
	<A2669EB4-D140-46E6-B470-9911185BFFE9@gmail.com>
	<22A2C780-6DC5-40B5-A3B7-A05E56F53E2E@apple.com>
	<98A8F345-E73F-4E18-B586-579EC5AD1BDF@apple.com>
	<021BB72C-901A-4751-9AF1-FC2D752C420D@apple.com>
	<C9B90310-AF4E-4D83-8798-A42ADCAB52FA@apple.com>
	<6827EB79-C933-478F-A315-9E3180D3448C@apple.com>
Message-ID: <B718060B-ABFB-4402-BF4B-7293B8F97D8F@apple.com>

On Oct 29, 2009, at 12:54 PM, Josh Ballanco wrote:
> On Oct 29, 2009, at 12:48 PM, Ernest N. Prabhakar, Ph.D. wrote:
>
>> Hi Laurent,
>>
>> On Oct 29, 2009, at 12:42 PM, Laurent Sansonetti wrote:
>>> On Oct 29, 2009, at 12:39 PM, Ernest N. Prabhakar, Ph.D. wrote:
>>>
>>>> Hi Laurent,
>>>>
>>>> On Oct 29, 2009, at 12:26 PM, Laurent Sansonetti wrote:
>>>>
>>>>> $ macruby -e "p MACRUBY_REVISION"
>>>>> "svn revision 2915 from http://svn.macosforge.org/repository/ruby/MacRuby/trunk 
>>>>> "
>>>>>
>>>>> If MacRuby was built from Git (I think that's what the nightly  
>>>>> build does), the constant will have the full Git line (with the  
>>>>> sha1 signature).
>>>>>
>>>>
>>>> Apparently not:
>>>>
>>>>> prabhaka$ macruby -e "p MACRUBY_REVISION"
>>>>> "unknown revision"
>>>
>>> Where does your version of MacRuby come from? :-)
>>
>> I'm pretty sure this was the latest nightly, installed using:
>>
>
> Git will require an extra Attribute to properly do version  
> substitution. See the section on "export-subst" in the Pro Git book: http://progit.org/book/ch7-2.html

This used to work before when we were using Git by default (albeit a  
different repository). Vincent probably knows what's going wrong here :)

Laurent

From lsansonetti at apple.com  Thu Oct 29 13:17:27 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 29 Oct 2009 13:17:27 -0700
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <23407BC3-B710-43FD-B958-3A779753C6A2@0x82.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com>
	<983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
	<23407BC3-B710-43FD-B958-3A779753C6A2@0x82.com>
Message-ID: <E6CFD4D9-72A2-4ADE-BF6D-45E39B56E27E@apple.com>

Hi Ruben,

On Oct 29, 2009, at 8:44 AM, Ruben Fonseca wrote:

> Hi Laurent. Just a quick question.
>
> On Oct 28, 2009, at 12:31 AM, Laurent Sansonetti wrote:
>
>> Hi Alan,
>>
>> I'm afraid the MD* APIs haven't been covered by BridgeSupport yet,  
>> so it may not be possible to call it directly from MacRuby at this  
>> point. I would recommend to file a bug at http://bugreporter.apple.com 
>>  so that we can consider this for a future Mac OS X release, and to  
>> wrap this C API into an Objective-C class that you can call from  
>> MacRuby in the meantime.
>>
>> Laurent
>
> Does it make any sense to write wrappers to APIs not covered by  
> BridgeSupport and bundle them in Macruby? (Isn't GCD such a case?).

It would definitely be interesting to share the wrappers, but I don't  
know if bundling them as part of MacRuby is a good idea. If we start  
doing that we would have to make sure all wrappers are consistent. And  
these wrappers would be temporary, until a new version of Mac OS X  
comes out with the support.

I guess that it's better if people share them on Github. We could have  
a list of them on the website so that people can easily find them.

Thoughts?

Laurent

From prabhaka at apple.com  Thu Oct 29 15:18:09 2009
From: prabhaka at apple.com (Ernest N. Prabhakar, Ph.D.)
Date: Thu, 29 Oct 2009 15:18:09 -0700
Subject: [MacRuby-devel] Another meaningless benchmark
Message-ID: <762D43E2-7949-4644-B99C-B40C50C4A838@apple.com>

But what the heck, they're fun. :-)

http://www.timestretch.com/FractalBenchmark.html

prabhaka$ ruby --version
ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0]
Ruby Elapsed 4.885692

prabhaka$ macruby --version
MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
Ruby Elapsed 0.251436

Roughly 20x faster!  That would make us comparable to Lua for this benchmark -- about 30x slower than C.

-- Ernie P.


From conradwt at gmail.com  Thu Oct 29 15:39:47 2009
From: conradwt at gmail.com (Conrad Taylor)
Date: Thu, 29 Oct 2009 15:39:47 -0700
Subject: [MacRuby-devel] Another meaningless benchmark
In-Reply-To: <762D43E2-7949-4644-B99C-B40C50C4A838@apple.com>
References: <762D43E2-7949-4644-B99C-B40C50C4A838@apple.com>
Message-ID: <7317d7610910291539y4caf3a82g7323226cfbc5a016@mail.gmail.com>

On Thu, Oct 29, 2009 at 3:18 PM, Ernest N. Prabhakar, Ph.D. <
prabhaka at apple.com> wrote:

> But what the heck, they're fun. :-)
>
> http://www.timestretch.com/FractalBenchmark.html
>
> prabhaka$ ruby --version
> ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0]
> Ruby Elapsed 4.885692
>
> prabhaka$ macruby --version
> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
> Ruby Elapsed 0.251436
>
> Roughly 20x faster!  That would make us comparable to Lua for this
> benchmark -- about 30x slower than C.
>
> -- Ernie P.
>
>
Ernie, what are the units of measure here?

-Conrad


> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091029/555ed764/attachment.html>

From vincent.isambart at gmail.com  Thu Oct 29 15:48:15 2009
From: vincent.isambart at gmail.com (Vincent Isambart)
Date: Fri, 30 Oct 2009 07:48:15 +0900
Subject: [MacRuby-devel] MACRUBY_REVISION
In-Reply-To: <B718060B-ABFB-4402-BF4B-7293B8F97D8F@apple.com>
References: <048.5239a8d480e856f10d617da8605ca00e@macosforge.org>
	<057.2fecb3528b7b8919e7691501a974af1b@macosforge.org>
	<A2669EB4-D140-46E6-B470-9911185BFFE9@gmail.com>
	<22A2C780-6DC5-40B5-A3B7-A05E56F53E2E@apple.com>
	<98A8F345-E73F-4E18-B586-579EC5AD1BDF@apple.com>
	<021BB72C-901A-4751-9AF1-FC2D752C420D@apple.com>
	<C9B90310-AF4E-4D83-8798-A42ADCAB52FA@apple.com>
	<6827EB79-C933-478F-A315-9E3180D3448C@apple.com>
	<B718060B-ABFB-4402-BF4B-7293B8F97D8F@apple.com>
Message-ID: <C78067A0-1215-469D-95E1-433330BBD296@gmail.com>

>>>>>> prabhaka$ macruby -e "p MACRUBY_REVISION"
>>>>>> "unknown revision"
>>>>
>>>> Where does your version of MacRuby come from? :-)
>>>
>>> I'm pretty sure this was the latest nightly, installed using:
>>>
>>
>> Git will require an extra Attribute to properly do version  
>> substitution. See the section on "export-subst" in the Pro Git  
>> book: http://progit.org/book/ch7-2.html
>
> This used to work before when we were using Git by default (albeit a  
> different repository). Vincent probably knows what's going wrong  
> here :)

It works on git:
% macruby -e "p MACRUBY_REVISION"
"git commit 35e069811a44e9346b00cfbcccedc24ae7cce48f"

I'm not using export-subst, but when their is a .svn directory I'm  
calling "svn info" and if there is a .git directory I'm reading .git/ 
HEAD. "unknown revision" should only appear if there is neither a .svn  
nor a .git directory. I haven't looked at the scripts that build the  
nightlies but does it do a svn export or something similar? If that's  
the case, could we switch to a normal checkout?

From prabhaka at apple.com  Thu Oct 29 15:49:12 2009
From: prabhaka at apple.com (Ernest N. Prabhakar, Ph.D.)
Date: Thu, 29 Oct 2009 15:49:12 -0700
Subject: [MacRuby-devel] Another meaningless benchmark
In-Reply-To: <7317d7610910291539y4caf3a82g7323226cfbc5a016@mail.gmail.com>
References: <762D43E2-7949-4644-B99C-B40C50C4A838@apple.com>
	<7317d7610910291539y4caf3a82g7323226cfbc5a016@mail.gmail.com>
Message-ID: <3BD46602-2592-4660-BFE7-01DF418155F6@apple.com>

Hi Conrad,

They are seconds of execution (clock) time, I believe.  Mostly arbitrary, since they're run on a different machine than the original.

-enp

On Oct 29, 2009, at 3:39 PM, Conrad Taylor wrote:

> On Thu, Oct 29, 2009 at 3:18 PM, Ernest N. Prabhakar, Ph.D. <prabhaka at apple.com> wrote:
> But what the heck, they're fun. :-)
> 
> http://www.timestretch.com/FractalBenchmark.html
> 
> prabhaka$ ruby --version
> ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0]
> Ruby Elapsed 4.885692
> 
> prabhaka$ macruby --version
> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
> Ruby Elapsed 0.251436
> 
> Roughly 20x faster!  That would make us comparable to Lua for this benchmark -- about 30x slower than C.
> 
> -- Ernie P.
> 
> 
> Ernie, what are the units of measure here?
> 
> -Conrad
>  
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> 
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091029/f504a94b/attachment.html>

From ruby-noreply at macosforge.org  Thu Oct 29 16:37:19 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Thu, 29 Oct 2009 23:37:19 -0000
Subject: [MacRuby-devel] [MacRuby] #411: MacRuby does not force call to
	finalizers
In-Reply-To: <050.5c6b5e5e7dce70393440dc067fdf1822@macosforge.org>
References: <050.5c6b5e5e7dce70393440dc067fdf1822@macosforge.org>
Message-ID: <059.9487099efca397ef245e05c9d7c1d180@macosforge.org>

#411: MacRuby does not force call to finalizers
---------------------------------+------------------------------------------
 Reporter:  neeracher@?          |        Owner:  lsansonetti@?        
     Type:  defect               |       Status:  closed               
 Priority:  blocker              |    Milestone:  MacRuby 0.5          
Component:  MacRuby              |   Resolution:  fixed                
 Keywords:                       |  
---------------------------------+------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Should be fixed by r2921.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/411#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 29 19:42:20 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 30 Oct 2009 02:42:20 -0000
Subject: [MacRuby-devel] [MacRuby] #391: HotCocoa on_notification method
 stopped functioning in MacRuby 0.5 under Snow Leopard
In-Reply-To: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
References: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
Message-ID: <064.ff9e758b60e50b86afba5013a240430c@macosforge.org>

#391: HotCocoa on_notification method stopped functioning in MacRuby 0.5 under
Snow Leopard
--------------------------------------+-------------------------------------
 Reporter:  trevor@?                  |       Owner:  lsansonetti@?           
     Type:  defect                    |      Status:  new                     
 Priority:  blocker                   |   Milestone:                          
Component:  MacRuby                   |    Keywords:  HotCocoa on_notification
--------------------------------------+-------------------------------------

Comment(by mattaimonetti@?):

 bug confirmed, I also added another example.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/391#comment:4>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 29 20:55:04 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 30 Oct 2009 03:55:04 -0000
Subject: [MacRuby-devel] [MacRuby] #391: HotCocoa on_notification method
 stopped functioning in MacRuby 0.5 under Snow Leopard
In-Reply-To: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
References: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
Message-ID: <064.cf651388e3429732656e292fea8cc489@macosforge.org>

#391: HotCocoa on_notification method stopped functioning in MacRuby 0.5 under
Snow Leopard
--------------------------------------+-------------------------------------
 Reporter:  trevor@?                  |       Owner:  lsansonetti@?           
     Type:  defect                    |      Status:  new                     
 Priority:  blocker                   |   Milestone:                          
Component:  MacRuby                   |    Keywords:  HotCocoa on_notification
--------------------------------------+-------------------------------------

Comment(by mattaimonetti@?):

 bug fixed by Rich.


 {{{
 $ ./miniruby -I./lib ~/tmp/hotcocoabug.rb
 Received notification of NSWindowDidUpdateNotification on my window
 Received notification of NSWindowDidUpdateNotification on my window
 Received notification of NSWindowDidUpdateNotification on my window
 Received notification of NSWindowDidUpdateNotification on my window
 Received notification of NSWindowDidBecomeMainNotification on my window
 Received notification of NSWindowDidBecomeKeyNotification on my window
 Received notification of NSWindowDidUpdateNotification on my window
 Received notification of NSWindowDidUpdateNotification on my window

 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/391#comment:5>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 29 20:55:17 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 30 Oct 2009 03:55:17 -0000
Subject: [MacRuby-devel] [MacRuby] #391: HotCocoa on_notification method
 stopped functioning in MacRuby 0.5 under Snow Leopard
In-Reply-To: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
References: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
Message-ID: <064.554629a06566517c48a902f790ebaad0@macosforge.org>

#391: HotCocoa on_notification method stopped functioning in MacRuby 0.5 under
Snow Leopard
--------------------------------------+-------------------------------------
 Reporter:  trevor@?                  |        Owner:  lsansonetti@?        
     Type:  defect                    |       Status:  closed               
 Priority:  blocker                   |    Milestone:                       
Component:  MacRuby                   |   Resolution:  fixed                
 Keywords:  HotCocoa on_notification  |  
--------------------------------------+-------------------------------------
Changes (by mattaimonetti@?):

  * status:  new => closed
  * resolution:  => fixed


-- 
Ticket URL: <http://www.macruby.org/trac/ticket/391#comment:6>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Thu Oct 29 20:59:43 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 30 Oct 2009 03:59:43 -0000
Subject: [MacRuby-devel] [MacRuby] #391: HotCocoa on_notification method
 stopped functioning in MacRuby 0.5 under Snow Leopard
In-Reply-To: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
References: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
Message-ID: <064.d9102490be0baf08d36d3366fa9c128e@macosforge.org>

#391: HotCocoa on_notification method stopped functioning in MacRuby 0.5 under
Snow Leopard
--------------------------------------+-------------------------------------
 Reporter:  trevor@?                  |        Owner:  lsansonetti@?        
     Type:  defect                    |       Status:  closed               
 Priority:  blocker                   |    Milestone:                       
Component:  MacRuby                   |   Resolution:  fixed                
 Keywords:  HotCocoa on_notification  |  
--------------------------------------+-------------------------------------

Comment(by rich@?):

 Replying to [comment:6 mattaimonetti@?]:
 Here is what i am observing is happening.  i just committed code to hold
 all listeners but when you do:

 on_notification ...
 end

 there is an object created internally which is the listener.  that object
 is being garbage collected.  it was likely a bug under 0.4 that did not
 garbage collect this but now it is.  you can do one of two things.
 reinstall macruby after my commit tonight OR just do:

 @listener = on_notification ...
 end

 thus you hold that in an instance variable so it will not be garbage
 collected.

 See if that works

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/391#comment:7>
MacRuby <http://macruby.org/>


From blowmage at gmail.com  Thu Oct 29 23:16:26 2009
From: blowmage at gmail.com (Mike Moore)
Date: Fri, 30 Oct 2009 00:16:26 -0600
Subject: [MacRuby-devel] RoxorReturnFromBlockException
Message-ID: <f5bedd150910292316u28caa4d9kfb24fed5a8dd261@mail.gmail.com>

It looks like MacRuby doesn't allow calling return in a block, which works
in 1.8 and 1.9. This looks to be by design, so I'm not sure if the team
wants a ticket created. Should I create a ticket?

----------------------------------------

def foo
  f = Proc.new { return "return from foo from inside Proc.new" }
  f.call # control leaves foo here
  return "return from foo"
end

def bar
  f = lambda { return "return from bar from inside lambda" }
  f.call # control does not leave bar here
  return "return from bar"
end

def baz
  f = proc { return "return from baz from inside proc" }
  f.call # control does not leave bar here in 1.8, but does in 1.9
  return "return from baz"
end

puts foo
puts bar
puts baz

----------------------------------------

$ ruby blocks.rb
return from foo from inside Proc.new
return from bar
return from baz
$ ruby19 blocks.rb
return from foo from inside Proc.new
return from bar
return from baz from inside proc
$ macruby blocks.rb
uncaught Objective-C/C++ exception...
terminate called after throwing an instance of
'RoxorReturnFromBlockException*'
Abort trap
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091030/7e5f6a30/attachment-0001.html>

From lsansonetti at apple.com  Thu Oct 29 23:43:59 2009
From: lsansonetti at apple.com (Laurent Sansonetti)
Date: Thu, 29 Oct 2009 23:43:59 -0700
Subject: [MacRuby-devel] RoxorReturnFromBlockException
In-Reply-To: <f5bedd150910292316u28caa4d9kfb24fed5a8dd261@mail.gmail.com>
References: <f5bedd150910292316u28caa4d9kfb24fed5a8dd261@mail.gmail.com>
Message-ID: <57C595D9-ECD2-4592-8318-840271C49B38@apple.com>

Hi Mike,

No, this is not by design, you found a bug :-) Please file a ticket.

Thanks,

Laurent

On Oct 29, 2009, at 11:16 PM, Mike Moore wrote:

> It looks like MacRuby doesn't allow calling return in a block, which  
> works in 1.8 and 1.9. This looks to be by design, so I'm not sure if  
> the team wants a ticket created. Should I create a ticket?
>
> ----------------------------------------
>
> def foo
>   f = Proc.new { return "return from foo from inside Proc.new" }
>   f.call # control leaves foo here
>   return "return from foo"
> end
>
> def bar
>   f = lambda { return "return from bar from inside lambda" }
>   f.call # control does not leave bar here
>   return "return from bar"
> end
>
> def baz
>   f = proc { return "return from baz from inside proc" }
>   f.call # control does not leave bar here in 1.8, but does in 1.9
>   return "return from baz"
> end
>
> puts foo
> puts bar
> puts baz
>
> ----------------------------------------
>
> $ ruby blocks.rb
> return from foo from inside Proc.new
> return from bar
> return from baz
> $ ruby19 blocks.rb
> return from foo from inside Proc.new
> return from bar
> return from baz from inside proc
> $ macruby blocks.rb
> uncaught Objective-C/C++ exception...
> terminate called after throwing an instance of  
> 'RoxorReturnFromBlockException*'
> Abort trap
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Thu Oct 29 23:56:46 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 30 Oct 2009 06:56:46 -0000
Subject: [MacRuby-devel] [MacRuby] #412: Calling return in a block raises an
	exception
Message-ID: <048.d7d6d16dc92aeb26270396abb5e0238c@macosforge.org>

#412: Calling return in a block raises an exception
-------------------------------+--------------------------------------------
 Reporter:  mike@?             |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  blocker            |   Milestone:                       
Component:  MacRuby            |    Keywords:                       
-------------------------------+--------------------------------------------
 MacRuby 0.5 beta 1 doesn't allow calling return in a block, which works in
 1.8 and 1.9.

 {{{
 #!ruby
 def foo
   f = Proc.new { return "return from foo from inside Proc.new" }
   f.call # control leaves foo here
   return "return from foo"
 end

 def bar
   f = lambda { return "return from bar from inside lambda" }
   f.call # control does not leave bar here
   return "return from bar"
 end

 def baz
   f = proc { return "return from baz from inside proc" }
   f.call # control does not leave bar here in 1.8, but does in 1.9
   return "return from baz"
 end

 puts foo
 puts bar
 puts baz
 }}}

 ----------------------------------------

 {{{
 #!sh
 $ ruby blocks.rb
 return from foo from inside Proc.new
 return from bar
 return from baz

 $ ruby19 blocks.rb
 return from foo from inside Proc.new
 return from bar
 return from baz from inside proc

 $ macruby blocks.rb
 uncaught Objective-C/C++ exception...
 terminate called after throwing an instance of
 'RoxorReturnFromBlockException*'
 Abort trap
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/412>
MacRuby <http://macruby.org/>


From blowmage at gmail.com  Thu Oct 29 23:57:47 2009
From: blowmage at gmail.com (Mike Moore)
Date: Fri, 30 Oct 2009 00:57:47 -0600
Subject: [MacRuby-devel] RoxorReturnFromBlockException
In-Reply-To: <57C595D9-ECD2-4592-8318-840271C49B38@apple.com>
References: <f5bedd150910292316u28caa4d9kfb24fed5a8dd261@mail.gmail.com>
	<57C595D9-ECD2-4592-8318-840271C49B38@apple.com>
Message-ID: <f5bedd150910292357g279277b1yfc410139a67ba1ad@mail.gmail.com>

But it is a named exception... Doesn't that mean it is by design? :)

Created #412

On Fri, Oct 30, 2009 at 12:43 AM, Laurent Sansonetti
<lsansonetti at apple.com>wrote:

> Hi Mike,
>
> No, this is not by design, you found a bug :-) Please file a ticket.
>
> Thanks,
>
> Laurent
>
>
> On Oct 29, 2009, at 11:16 PM, Mike Moore wrote:
>
>  It looks like MacRuby doesn't allow calling return in a block, which works
>> in 1.8 and 1.9. This looks to be by design, so I'm not sure if the team
>> wants a ticket created. Should I create a ticket?
>>
>> ----------------------------------------
>>
>> def foo
>>  f = Proc.new { return "return from foo from inside Proc.new" }
>>  f.call # control leaves foo here
>>  return "return from foo"
>> end
>>
>> def bar
>>  f = lambda { return "return from bar from inside lambda" }
>>  f.call # control does not leave bar here
>>  return "return from bar"
>> end
>>
>> def baz
>>  f = proc { return "return from baz from inside proc" }
>>  f.call # control does not leave bar here in 1.8, but does in 1.9
>>  return "return from baz"
>> end
>>
>> puts foo
>> puts bar
>> puts baz
>>
>> ----------------------------------------
>>
>> $ ruby blocks.rb
>> return from foo from inside Proc.new
>> return from bar
>> return from baz
>> $ ruby19 blocks.rb
>> return from foo from inside Proc.new
>> return from bar
>> return from baz from inside proc
>> $ macruby blocks.rb
>> uncaught Objective-C/C++ exception...
>> terminate called after throwing an instance of
>> 'RoxorReturnFromBlockException*'
>> Abort trap
>>
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091030/33b858d0/attachment.html>

From vincent.isambart at gmail.com  Fri Oct 30 00:18:14 2009
From: vincent.isambart at gmail.com (Vincent Isambart)
Date: Fri, 30 Oct 2009 16:18:14 +0900
Subject: [MacRuby-devel] RoxorReturnFromBlockException
In-Reply-To: <f5bedd150910292357g279277b1yfc410139a67ba1ad@mail.gmail.com>
References: <f5bedd150910292316u28caa4d9kfb24fed5a8dd261@mail.gmail.com>
	<57C595D9-ECD2-4592-8318-840271C49B38@apple.com>
	<f5bedd150910292357g279277b1yfc410139a67ba1ad@mail.gmail.com>
Message-ID: <7d9a1f530910300018g7aa91705o6b778b4b3f99df7f@mail.gmail.com>

> But it is a named exception... Doesn't that mean it is by design? :)
It's an exception used internally, you should not be able to see it
from the outside.

> Created #412
Thanks!

From ruben at 0x82.com  Fri Oct 30 05:12:33 2009
From: ruben at 0x82.com (Ruben Fonseca)
Date: Fri, 30 Oct 2009 12:12:33 +0000
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <E6CFD4D9-72A2-4ADE-BF6D-45E39B56E27E@apple.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com>
	<983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
	<23407BC3-B710-43FD-B958-3A779753C6A2@0x82.com>
	<E6CFD4D9-72A2-4ADE-BF6D-45E39B56E27E@apple.com>
Message-ID: <B532C46F-82CC-4D85-8301-7FFBD5C592AF@0x82.com>

Hi Lauren!

On Oct 29, 2009, at 8:17 PM, Laurent Sansonetti wrote:

> It would definitely be interesting to share the wrappers, but I  
> don't know if bundling them as part of MacRuby is a good idea. If we  
> start doing that we would have to make sure all wrappers are  
> consistent. And these wrappers would be temporary, until a new  
> version of Mac OS X comes out with the support.
>
> I guess that it's better if people share them on Github. We could  
> have a list of them on the website so that people can easily find  
> them.
>
> Thoughts?

Good to hear! I guess I agree with you.

Since I'm new to this thing of adapting a C API to the Objective-C/ 
Ruby paradigm, I think I will try my first wrapper around the  
Spotlight API. Just a quick question: what should I do with C  
constants? Should I maintain them? Alias them?

My plan is to make public version of the wrapper, ask for opinions,  
learn, rewrite, ..., profit :)

Cheers
Ruben

From ruby-noreply at macosforge.org  Fri Oct 30 08:57:28 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 30 Oct 2009 15:57:28 -0000
Subject: [MacRuby-devel] [MacRuby] #364: priority queue program crashes
	MacRuby
In-Reply-To: <054.0603c1304c7461cada1c6fed59280cf0@macosforge.org>
References: <054.0603c1304c7461cada1c6fed59280cf0@macosforge.org>
Message-ID: <063.a05d86c02fd333451986e6a8eb0cf4bf@macosforge.org>

#364: priority queue program crashes MacRuby
-------------------------------------+--------------------------------------
 Reporter:  jordan.breeding@?        |       Owner:  lsansonetti@?        
     Type:  defect                   |      Status:  new                  
 Priority:  blocker                  |   Milestone:  MacRuby 0.5          
Component:  MacRuby                  |    Keywords:                       
-------------------------------------+--------------------------------------

Comment(by jordan.breeding@?):

 I think that #412 might actually be a valid reduction for this ticket as
 well.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/364#comment:1>
MacRuby <http://macruby.org/>


From jordan.breeding at me.com  Fri Oct 30 08:58:32 2009
From: jordan.breeding at me.com (Jordan Breeding)
Date: Fri, 30 Oct 2009 10:58:32 -0500
Subject: [MacRuby-devel] RoxorReturnFromBlockException
In-Reply-To: <7d9a1f530910300018g7aa91705o6b778b4b3f99df7f@mail.gmail.com>
References: <f5bedd150910292316u28caa4d9kfb24fed5a8dd261@mail.gmail.com>
	<57C595D9-ECD2-4592-8318-840271C49B38@apple.com>
	<f5bedd150910292357g279277b1yfc410139a67ba1ad@mail.gmail.com>
	<7d9a1f530910300018g7aa91705o6b778b4b3f99df7f@mail.gmail.com>
Message-ID: <7E021CA3-38B2-4149-A8EC-D0492F2B90D8@me.com>

On Oct 30, 2009, at 02:18, Vincent Isambart wrote:

>> But it is a named exception... Doesn't that mean it is by design? :)
> It's an exception used internally, you should not be able to see it
> from the outside.
>
>> Created #412
> Thanks!
>

I put a comment on ticket #364, I think that #412 is a reduction of  
the same problem I was seeing.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3820 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091030/300214ed/attachment.bin>

From ruby-noreply at macosforge.org  Fri Oct 30 10:24:27 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 30 Oct 2009 17:24:27 -0000
Subject: [MacRuby-devel] [MacRuby] #413: ruby_deploy embeds more than one
	version of macruby
Message-ID: <054.9e346436b60026409f3c1ce26ad090e6@macosforge.org>

#413: ruby_deploy embeds more than one version of macruby
-------------------------------------+--------------------------------------
 Reporter:  mattaimonetti@?          |       Owner:  lsansonetti@?        
     Type:  defect                   |      Status:  new                  
 Priority:  blocker                  |   Milestone:                       
Component:  MacRuby                  |    Keywords:  ruby_deploy          
-------------------------------------+--------------------------------------
 When using the new embedded target, the ruby_deploy script locates the
 MacRuby framework by doing:


 {{{
     @macruby_framework_path =
 Config::CONFIG['libdir'].scan(/^.+MacRuby\.framework/)[0]
 }}}

 Which will usually return a path like:


 {{{
 => "/Library/Frameworks/MacRuby.framework"
 }}}

 Later on in the script, the entire framework is copied to:


 {{{
     cp_r(@macruby_framework_path, File.join(@app_bundle,
 'Contents/Frameworks'))

 }}}


 The problem is that you might have multiple versions of MacRuby installed:

 {{{
 ls /Library/Frameworks/MacRuby.framework/Versions/
 => 0.4  0.5     Current
 }}}

 I think the deploy script should, by default, only ship the current
 version, and let you pass an argument to ship another version.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/413>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 30 12:06:20 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 30 Oct 2009 19:06:20 -0000
Subject: [MacRuby-devel] [MacRuby] #413: ruby_deploy embeds more than
 one version of macruby
In-Reply-To: <054.9e346436b60026409f3c1ce26ad090e6@macosforge.org>
References: <054.9e346436b60026409f3c1ce26ad090e6@macosforge.org>
Message-ID: <063.ee6b1171fe5e5f6b486cef4642ed145c@macosforge.org>

#413: ruby_deploy embeds more than one version of macruby
-------------------------------------+--------------------------------------
 Reporter:  mattaimonetti@?          |        Owner:  lsansonetti@?        
     Type:  defect                   |       Status:  closed               
 Priority:  blocker                  |    Milestone:  MacRuby 0.5          
Component:  MacRuby                  |   Resolution:  fixed                
 Keywords:  ruby_deploy              |  
-------------------------------------+--------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Should be fixed in r2929.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/413#comment:1>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 30 12:14:34 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 30 Oct 2009 19:14:34 -0000
Subject: [MacRuby-devel] [MacRuby] #412: Calling return from a Proc
 raises an exception (was: Calling return in a block raises an exception)
In-Reply-To: <048.d7d6d16dc92aeb26270396abb5e0238c@macosforge.org>
References: <048.d7d6d16dc92aeb26270396abb5e0238c@macosforge.org>
Message-ID: <057.3963decb2d138a76c998b7067fbd0f86@macosforge.org>

#412: Calling return from a Proc raises an exception
-------------------------------+--------------------------------------------
 Reporter:  mike@?             |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  blocker            |   Milestone:                       
Component:  MacRuby            |    Keywords:                       
-------------------------------+--------------------------------------------

Comment(by lsansonetti@?):

 Looks like #call is dispatched outside the return-from-block handler.

 {{{
 $ gdb --args ./miniruby -e "proc { return 42 }.call"
 GNU gdb 6.3.50-20050815 (Apple version gdb-1344) (Fri Jul  3 01:19:56 UTC
 2009)
 Copyright 2004 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and you
 are
 welcome to change it and/or distribute copies of it under certain
 conditions.
 Type "show copying" to see the conditions.
 There is absolutely no warranty for GDB.  Type "show warranty" for
 details.
 This GDB was configured as "x86_64-apple-darwin"...Reading symbols for
 shared libraries ......... done

 (gdb) r
 Starting program: /Users/lrz/src/macruby-trunk/miniruby -e proc\ \{\
 return\ 42\ \}.call
 Reading symbols for shared libraries .++++++++.................... done
 uncaught Objective-C/C++ exception...
 terminate called after throwing an instance of
 'RoxorReturnFromBlockException*'

 Program received signal SIGABRT, Aborted.
 0x00007fff80158096 in __kill ()
 (gdb) p RoxorCompiler::module->dump()
 ; ModuleID = 'Roxor'
 target triple = "x86_64-apple-darwin"

 define i64 @__ruby_scope(i64 %self, i8* %sel) {
 MainBlock:
   %0 = tail call i8* (i8*, i32, i64, i64, i8**, i8*, i32, ...)*
 @rb_vm_prepare_block(i8* inttoptr (i64 4311691648 to i8*), i32 0, i64
 %self, i64 0, i8** null, i8* null, i32 0, i32 0) ; <i8*> [#uses=1]
   %1 = invoke i64 (i8*, i64, i64, i8*, i8*, i8, i32, ...)*
 @rb_vm_dispatch(i8* inttoptr (i64 4311694496 to i8*), i64 %self, i64
 %self, i8* inttoptr (i64 4311539472 to i8*), i8* %0, i8 2, i32 0)
           to label %normal unwind label %return-from-block ; <i64>
 [#uses=1]

 return-from-block:                                ; preds = %MainBlock
   %2 = tail call i8* @llvm.eh.exception()         ; <i8*> [#uses=2]
   %3 = tail call i64 (i8*, i8*, ...)* @llvm.eh.selector.i64(i8* %2, i8*
 bitcast (i8* ()* @__gxx_personality_v0 to i8*), i8* null) ; <i64>
 [#uses=0]
   %4 = tail call i8* @__cxa_begin_catch(i8* %2)   ; <i8*> [#uses=1]
   %5 = tail call i64 @rb_vm_check_return_from_block_exc(i8* %4, i32 0) ;
 <i64> [#uses=2]
   %6 = icmp eq i64 %5, 6                          ; <i1> [#uses=1]
   br i1 %6, label %rethrow, label %ret

 normal:                                           ; preds = %MainBlock
   %7 = tail call i64 (i8*, i64, i64, i8*, i8*, i8, i32, ...)*
 @rb_vm_dispatch(i8* inttoptr (i64 4311690384 to i8*), i64 %self, i64 %1,
 i8* inttoptr (i64 140735458816510 to i8*), i8* null, i8 0, i32 0) ; <i64>
 [#uses=1]
   ret i64 %7

 ret:                                              ; preds = %return-from-
 block
   tail call void @__cxa_end_catch()
   ret i64 %5

 rethrow:                                          ; preds = %return-from-
 block
   tail call void @__cxa_rethrow()
   unreachable
 }

 define i64 @__ruby_scope1(i64 %self, i8* %sel, i64** %dvars, i8*
 %running_block) {
 MainBlock:
   tail call void @rb_vm_return_from_block(i64 169, i32 0)
   ret i64 169
 }

 declare void @rb_vm_return_from_block(i64, i32)

 declare i8* @rb_vm_prepare_block(i8*, i32, i64, i64, i8**, i8*, i32, ...)

 declare i64 @rb_vm_dispatch(i8*, i64, i64, i8*, i8*, i8, i32, ...)

 declare i8* @llvm.eh.exception() nounwind

 declare i64 @llvm.eh.selector.i64(i8*, i8*, ...) nounwind

 declare i8* @__gxx_personality_v0()

 declare i8* @__cxa_begin_catch(i8*)

 declare i64 @rb_vm_check_return_from_block_exc(i8*, i32)

 declare void @__cxa_end_catch()

 declare void @__cxa_rethrow()
 $1 = void
 }}}

 Note that this is a problem with Proc#call. Calling return from a non-Proc
 block should work. I altered the title.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/412#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 30 12:19:02 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 30 Oct 2009 19:19:02 -0000
Subject: [MacRuby-devel] [MacRuby] #412: Calling return from a Proc
	raises an exception
In-Reply-To: <048.d7d6d16dc92aeb26270396abb5e0238c@macosforge.org>
References: <048.d7d6d16dc92aeb26270396abb5e0238c@macosforge.org>
Message-ID: <057.222676acfa631b8503fc91213db2be90@macosforge.org>

#412: Calling return from a Proc raises an exception
-------------------------------+--------------------------------------------
 Reporter:  mike@?             |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  blocker            |   Milestone:                       
Component:  MacRuby            |    Keywords:                       
-------------------------------+--------------------------------------------

Comment(by mike@?):

 I get the exception when calling return from a lambda as well.

 {{{
 $ macruby -e "lambda { return 'hi' }.call"
 uncaught Objective-C/C++ exception...
 terminate called after throwing an instance of
 'RoxorReturnFromBlockException*'
 Abort trap
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/412#comment:3>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 30 12:34:56 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 30 Oct 2009 19:34:56 -0000
Subject: [MacRuby-devel] [MacRuby] #412: Calling return from a Proc
	raises an exception
In-Reply-To: <048.d7d6d16dc92aeb26270396abb5e0238c@macosforge.org>
References: <048.d7d6d16dc92aeb26270396abb5e0238c@macosforge.org>
Message-ID: <057.33aafc2caa05135a3e0f01ec0950dd14@macosforge.org>

#412: Calling return from a Proc raises an exception
-------------------------------+--------------------------------------------
 Reporter:  mike@?             |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  blocker            |   Milestone:                       
Component:  MacRuby            |    Keywords:                       
-------------------------------+--------------------------------------------

Comment(by lsansonetti@?):

 Yes, a lambda is a Proc too.

 {{{
 $ ./miniruby -e "def foo; 1.times { return 42 }; end; p foo"
 42
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/412#comment:4>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 30 12:40:54 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 30 Oct 2009 19:40:54 -0000
Subject: [MacRuby-devel] [MacRuby] #412: Calling return from a Proc
	raises an exception
In-Reply-To: <048.d7d6d16dc92aeb26270396abb5e0238c@macosforge.org>
References: <048.d7d6d16dc92aeb26270396abb5e0238c@macosforge.org>
Message-ID: <057.76e984449643a260490878fafd49bf9e@macosforge.org>

#412: Calling return from a Proc raises an exception
-------------------------------+--------------------------------------------
 Reporter:  mike@?             |       Owner:  lsansonetti@?        
     Type:  defect             |      Status:  new                  
 Priority:  blocker            |   Milestone:                       
Component:  MacRuby            |    Keywords:                       
-------------------------------+--------------------------------------------

Comment(by mike@?):

 Ah, I see what you mean. You are right of course. :)

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/412#comment:5>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Fri Oct 30 14:42:45 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Fri, 30 Oct 2009 21:42:45 -0000
Subject: [MacRuby-devel] [MacRuby] #410: Readline merge to the recent
	CRuby's.
In-Reply-To: <047.c2cc28060fed1350fb100e17eb29a9f9@macosforge.org>
References: <047.c2cc28060fed1350fb100e17eb29a9f9@macosforge.org>
Message-ID: <056.83fd26cba0f90662458ff8a60a955d38@macosforge.org>

#410: Readline merge to the recent CRuby's.
------------------------------+---------------------------------------------
 Reporter:  kouji@?           |        Owner:  lsansonetti@?        
     Type:  enhancement       |       Status:  closed               
 Priority:  blocker           |    Milestone:  MacRuby 0.5          
Component:  MacRuby           |   Resolution:  fixed                
 Keywords:  Readline          |  
------------------------------+---------------------------------------------

Comment(by eloy.de.enige@?):

 Nice work!

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/410#comment:2>
MacRuby <http://macruby.org/>


From eloy.de.enige at gmail.com  Fri Oct 30 14:50:01 2009
From: eloy.de.enige at gmail.com (Eloy Duran)
Date: Fri, 30 Oct 2009 22:50:01 +0100
Subject: [MacRuby-devel] spotlight - MDItemRef
In-Reply-To: <B532C46F-82CC-4D85-8301-7FFBD5C592AF@0x82.com>
References: <1256688797.10538.1342295669@webmail.messagingengine.com>
	<983FF4BC-F143-4447-9519-D3A4491DA950@apple.com>
	<23407BC3-B710-43FD-B958-3A779753C6A2@0x82.com>
	<E6CFD4D9-72A2-4ADE-BF6D-45E39B56E27E@apple.com>
	<B532C46F-82CC-4D85-8301-7FFBD5C592AF@0x82.com>
Message-ID: <BAC5FC13-AF43-4C14-A936-2068B2EE99CD@gmail.com>

Hey,

Forgive me that I haven't read the complete thread, so ignore this if  
it's not a possibility. But couldn't you use NSMetadataItem etc?

Eloy

On 30 okt 2009, at 13:12, Ruben Fonseca wrote:

> Hi Lauren!
>
> On Oct 29, 2009, at 8:17 PM, Laurent Sansonetti wrote:
>
>> It would definitely be interesting to share the wrappers, but I  
>> don't know if bundling them as part of MacRuby is a good idea. If  
>> we start doing that we would have to make sure all wrappers are  
>> consistent. And these wrappers would be temporary, until a new  
>> version of Mac OS X comes out with the support.
>>
>> I guess that it's better if people share them on Github. We could  
>> have a list of them on the website so that people can easily find  
>> them.
>>
>> Thoughts?
>
> Good to hear! I guess I agree with you.
>
> Since I'm new to this thing of adapting a C API to the Objective-C/ 
> Ruby paradigm, I think I will try my first wrapper around the  
> Spotlight API. Just a quick question: what should I do with C  
> constants? Should I maintain them? Alias them?
>
> My plan is to make public version of the wrapper, ask for opinions,  
> learn, rewrite, ..., profit :)
>
> Cheers
> Ruben
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


From ruby-noreply at macosforge.org  Fri Oct 30 22:50:41 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 31 Oct 2009 05:50:41 -0000
Subject: [MacRuby-devel] [MacRuby] #412: Calling return from a Proc
	raises an exception
In-Reply-To: <048.d7d6d16dc92aeb26270396abb5e0238c@macosforge.org>
References: <048.d7d6d16dc92aeb26270396abb5e0238c@macosforge.org>
Message-ID: <057.b237f6c328ed86eb47f2613a1b3cacdb@macosforge.org>

#412: Calling return from a Proc raises an exception
-------------------------------+--------------------------------------------
 Reporter:  mike@?             |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:                     |  
-------------------------------+--------------------------------------------
Changes (by lsansonetti@?):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => MacRuby 0.5


Comment:

 Should be fixed as of r2935:

 {{{
 $ ./miniruby t.rb
 return from foo from inside Proc.new
 return from bar
 return from baz from inside proc
 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/412#comment:6>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 31 00:27:17 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 31 Oct 2009 07:27:17 -0000
Subject: [MacRuby-devel] [MacRuby] #412: Calling return from a Proc
	raises an exception
In-Reply-To: <048.d7d6d16dc92aeb26270396abb5e0238c@macosforge.org>
References: <048.d7d6d16dc92aeb26270396abb5e0238c@macosforge.org>
Message-ID: <057.ac7616d360df885f9cb7c20b651e4aa6@macosforge.org>

#412: Calling return from a Proc raises an exception
-------------------------------+--------------------------------------------
 Reporter:  mike@?             |        Owner:  lsansonetti@?        
     Type:  defect             |       Status:  closed               
 Priority:  blocker            |    Milestone:  MacRuby 0.5          
Component:  MacRuby            |   Resolution:  fixed                
 Keywords:                     |  
-------------------------------+--------------------------------------------

Comment(by conradwt@?):

 In Ruby 1.9, lambda produces a different variant of the Proc object than
 Proc.new.  Also, proc is no longer a synonym for lambda.  However, one can
 use proc as a synonym for Proc.new.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/412#comment:7>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 31 00:44:26 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 31 Oct 2009 07:44:26 -0000
Subject: [MacRuby-devel] [MacRuby] #413: ruby_deploy embeds more than
 one version of macruby
In-Reply-To: <054.9e346436b60026409f3c1ce26ad090e6@macosforge.org>
References: <054.9e346436b60026409f3c1ce26ad090e6@macosforge.org>
Message-ID: <063.1b81224d45f740f072c5022fee544624@macosforge.org>

#413: ruby_deploy embeds more than one version of macruby
-------------------------------------+--------------------------------------
 Reporter:  mattaimonetti@?          |        Owner:  lsansonetti@?        
     Type:  defect                   |       Status:  closed               
 Priority:  blocker                  |    Milestone:  MacRuby 0.5          
Component:  MacRuby                  |   Resolution:  fixed                
 Keywords:  ruby_deploy              |  
-------------------------------------+--------------------------------------

Comment(by mattaimonetti@?):

 tested and confirmed.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/413#comment:2>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 31 01:09:36 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 31 Oct 2009 08:09:36 -0000
Subject: [MacRuby-devel] [MacRuby] #414: Printing Block Instances
	Inconsistent
Message-ID: <049.da03a8e6d88a75f7b88088f34413bab8@macosforge.org>

#414: Printing Block Instances Inconsistent
--------------------------------+-------------------------------------------
 Reporter:  conradwt@?          |       Owner:  lsansonetti@?        
     Type:  defect              |      Status:  new                  
 Priority:  minor               |   Milestone:  MacRuby 0.5          
Component:  MacRuby             |    Keywords:  Beta 1               
--------------------------------+-------------------------------------------
 The printing of block instances, lambda and proc, are not consistent with
 Ruby 1.9.1/1.9.2:

 block-instance-output.rb:

 {{{

 a_proc = Proc.new { puts "This is a test proc" }
 p a_proc

 a_lambda = lambda { puts "This is a test lambda" }
 p a_lambda

 }}}

 from command line:

 {{{
 macruby block-instance-output.rb

 #<Proc:0x2000246c0>
 #<Proc:0x200024600>

 }}}

 {{{
 ruby  block-instance-output.rb

 #<Proc:0x000001010399e0 at block-instance-output.rb:1>
 #<Proc:0x00000101039900 at block-instance-output.rb:4 (lambda)>

 }}}

 from irb:

 {{{

 $ macirb
 irb(main):001:0> load "block-instance-output.rb"
 #<Proc:0x200247480>
 #<Proc:0x2002473c0>
 => true

 }}}


 {{{

 $ irb
 irb(main):001:0> load "block-instance-output.rb"
 #<Proc:0x00000101014398@/Users/conradwt/block-instance-output.rb:1>
 #<Proc:0x000001010141a0@/Users/conradwt/block-instance-output.rb:4
 (lambda)>
 => true

 }}}

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/414>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 31 01:42:10 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 31 Oct 2009 08:42:10 -0000
Subject: [MacRuby-devel] [MacRuby] #391: HotCocoa on_notification method
 stopped functioning in MacRuby 0.5 under Snow Leopard
In-Reply-To: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
References: <055.fb6b4ed02e3bbc9c3b7477764b178354@macosforge.org>
Message-ID: <064.fcc88abb342bb0ca7299112b5aa11a03@macosforge.org>

#391: HotCocoa on_notification method stopped functioning in MacRuby 0.5 under
Snow Leopard
--------------------------------------+-------------------------------------
 Reporter:  trevor@?                  |        Owner:  lsansonetti@?        
     Type:  defect                    |       Status:  closed               
 Priority:  blocker                   |    Milestone:                       
Component:  MacRuby                   |   Resolution:  fixed                
 Keywords:  HotCocoa on_notification  |  
--------------------------------------+-------------------------------------

Comment(by trevor@?):

 Workaround with instance variable works just fine. Thank you.

 And thanks to Robert for his help.

 Rgds
 Trevor Hills

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/391#comment:8>
MacRuby <http://macruby.org/>


From ruby-noreply at macosforge.org  Sat Oct 31 10:37:28 2009
From: ruby-noreply at macosforge.org (MacRuby)
Date: Sat, 31 Oct 2009 17:37:28 -0000
Subject: [MacRuby-devel] [MacRuby] #409: Attribute setter should be
 accepted as KVO setter
In-Reply-To: <050.33a0371df802951a6ff2317cfe09a9fa@macosforge.org>
References: <050.33a0371df802951a6ff2317cfe09a9fa@macosforge.org>
Message-ID: <059.52baaee30a1303571f877df220835cee@macosforge.org>

#409: Attribute setter should be accepted as KVO setter
---------------------------------+------------------------------------------
 Reporter:  neeracher@?          |       Owner:  lsansonetti@?        
     Type:  enhancement          |      Status:  new                  
 Priority:  minor                |   Milestone:                       
Component:  MacRuby              |    Keywords:                       
---------------------------------+------------------------------------------

Comment(by dylan@?):

 *poke* I just ran into this one and traced it down. Any updates ?

 I've attached a project that shows a naive implementation with bindings
 that shows how someone could get into trouble with this.

 I think this is a little more severe than it appears at first glance. It
 violates the principle of least surprise in a big way; even something a
 simple as adapting example code to a new Mac interface will run afoul of
 this pretty quickly.

 Even if you're familiar with both Ruby and ObjC this generates some
 confusion since you can no longer use idiomatic ruby to change your model
 if you want it bound to the UI at any future date. You currently have to
 get used to always using the ObjC setValue way.

 If you're not familiar with both you're going to be scratching your head
 for a while.

 This is also insidious since your model unit tests will pass and only the
 less easily testable UI will fail, unless you set up explicit bindings
 tests for each property.

 That said, this may not be as simple a fix as it appears. My gut feeling
 was to override attr_accessor and writer to generate a value= method that
 just calls setValue. This works 95% of the time, but gets murky when you
 want to create a custom setter. Which do you override ? Do you always have
 to call setValue from your value= method ? How should it be documented if
 that's the case ? Of course, you still have that confusion the way it
 exists now. Going to implement value= and then finding that your bindings
 don't call that method, for instance.

-- 
Ticket URL: <http://www.macruby.org/trac/ticket/409#comment:1>
MacRuby <http://macruby.org/>