Re: [MacRuby-devel] experimental branch: status update

2009-08-06 Thread John-Paul Bader 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,


I just forked the "official" github macruby repository and updated it. 
http://github.com/hukl/macruby/tree/master

I will deploy a script later on to keep it up to date.

Kind regards, John (who is still shaking his head about those svn  
stunts being practised at apple ;)


On 06.08.2009, at 01:27, Laurent Sansonetti wrote:


On Aug 4, 2009, at 1:59 PM, Laurent Sansonetti wrote:
I will proceed with the merge tomorrow at 3PM California time  
(midnight Amsterdam time, 7AM Tokyo time). Feel free to commit  
before, but please hold off your commits at that time :)


OK, I wasn't able to really merge the branch into trunk, because I  
didn't remember which revision of SVN I used to create experimental  
last year (I was experimenting with git at that time), and svn merge  
got confused when I used the default parameters.


Since I'm a lazy person [1], I simply moved trunk as branches/yarv  
and copied branches/experimental as trunk.  This method has the  
inconvenience of losing the history of what happened in trunk  
before, but we can live without it (and it's still available in  
branches/yarv if we can't sleep).


Please make a *fresh checkout* of trunk and let's continue the good  
work there :)


$ svn co http://svn.macosforge.org/repository/ruby/MacRuby/trunk  
macruby-trunk


Laurent

[1] "Laziness is a virtue" - Larry Wall
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel



-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkp6gIUACgkQK6xKqn9SkYNzFgCguOeKJuDRU3A04fNqoBoQ+2D0
Yz0Anjd/+GGTKCVRezAAaTtgeaY+g0iP
=rKJH
-END PGP SIGNATURE-
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] How to use custom C struct's?

2009-08-06 Thread Eloy Duran 
FYI, BridgeSupport is mostly implemented in MacRuby, at least the  
part that deals with C structures. The only part that we didn't  
implement yet is C function pointers, the rest (roughly 90%) is  
done, and it is faster / more stable than the RubyCocoa code (you  
will have to believe me, since I wrote both :-)).


LOL, I'm a believer :-)

@Jordan: Thanks for putting it up on the wiki.

Eloy
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Base64 specs

2009-08-06 Thread Eloy Duran 

Hey Dan,

By just reading the patch it seems there are no new versions of these  
examples on how the method works on 1.9.x. Could you please add those  
as well?


Cheers,
Eloy

On Aug 5, 2009, at 5:44 AM, dan sinclair wrote:


Hello,

The attached patch marks some specs that don't execute on Ruby 1.9.2  
for me.  The other Base64 specs that are broken are due to the TODO  
in vm_method.c,  rb_mod_modfunc to do with changing scope.


dan


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] experimental branch: status update

2009-08-06 Thread Conrad Taylor 
On Wed, Aug 5, 2009 at 4:27 PM, Laurent Sansonetti wrote:

> On Aug 4, 2009, at 1:59 PM, Laurent Sansonetti wrote:
>
>> I will proceed with the merge tomorrow at 3PM California time (midnight
>> Amsterdam time, 7AM Tokyo time). Feel free to commit before, but please hold
>> off your commits at that time :)
>>
>
> OK, I wasn't able to really merge the branch into trunk, because I didn't
> remember which revision of SVN I used to create experimental last year (I
> was experimenting with git at that time), and svn merge got confused when I
> used the default parameters.
>
> Since I'm a lazy person [1], I simply moved trunk as branches/yarv and
> copied branches/experimental as trunk.  This method has the inconvenience of
> losing the history of what happened in trunk before, but we can live without
> it (and it's still available in branches/yarv if we can't sleep).
>
> Please make a *fresh checkout* of trunk and let's continue the good work
> there :)
>
> $ svn co http://svn.macosforge.org/repository/ruby/MacRuby/trunkmacruby-trunk
>
> Laurent
>
> [1] "Laziness is a virtue" - Larry Wall
>

Hi, revision 2239 looks good:

Finished in 108.039708 seconds

1540 files, 6265 examples, 18457 expectations, 0 failures, 0 errors

Are we tracking the execution time versus the number of expectations
anywhere?

-Conrad



>
> ___
> MacRuby-devel mailing list
> [email protected]
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] experimental branch: status update

2009-08-06 Thread Eloy Duran 
Nope not yet. I personally would like to have something like the  
following up:

http://blog.jimmy.schementi.com/2009/02/ironrubyinfo.html
http://github.com/jschementi/ironruby-stats/tree/master

Which reports a bit on performance and the RubySpec compliance.

Alas, like so many fun things, I haven't had any time yet for it and  
don't see any in the near future. So if you'd like something like that  
as well, please go ahead :)


Cheers,
Eloy

On Aug 6, 2009, at 9:57 AM, Conrad Taylor wrote:

On Wed, Aug 5, 2009 at 4:27 PM, Laurent Sansonetti > wrote:

On Aug 4, 2009, at 1:59 PM, Laurent Sansonetti wrote:
I will proceed with the merge tomorrow at 3PM California time  
(midnight Amsterdam time, 7AM Tokyo time). Feel free to commit  
before, but please hold off your commits at that time :)


OK, I wasn't able to really merge the branch into trunk, because I  
didn't remember which revision of SVN I used to create experimental  
last year (I was experimenting with git at that time), and svn merge  
got confused when I used the default parameters.


Since I'm a lazy person [1], I simply moved trunk as branches/yarv  
and copied branches/experimental as trunk.  This method has the  
inconvenience of losing the history of what happened in trunk  
before, but we can live without it (and it's still available in  
branches/yarv if we can't sleep).


Please make a *fresh checkout* of trunk and let's continue the good  
work there :)


$ svn co http://svn.macosforge.org/repository/ruby/MacRuby/trunk  
macruby-trunk


Laurent

[1] "Laziness is a virtue" - Larry Wall

Hi, revision 2239 looks good:

Finished in 108.039708 seconds

1540 files, 6265 examples, 18457 expectations, 0 failures, 0 errors

Are we tracking the execution time versus the number of expectations  
anywhere?


-Conrad



___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] experimental branch: status update

2009-08-06 Thread John-Paul Bader 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi again,

I just created another repo on my github account called macruby-mirror  
which includes all branches/tags as well.


I wasn't able to add those to the existing fork within the last two  
hours so I created a clean svn import. If everything works as  
expected, changes on svn branches should now appear on github as well.


URL: http://github.com/hukl/macruby-mirror/

Kind regards, John

On 06.08.2009, at 09:04, John-Paul Bader wrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,


I just forked the "official" github macruby repository and updated  
it. http://github.com/hukl/macruby/tree/master


I will deploy a script later on to keep it up to date.

Kind regards, John (who is still shaking his head about those svn  
stunts being practised at apple ;)


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkp6rqgACgkQK6xKqn9SkYMYGwCdFFUxNyu1h9XhoEyWM4DJ7EFa
BW8AoLCMrLWQ10NPXRrNuv8Yfx6S6g+h
=oJii
-END PGP SIGNATURE-
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #302: 0.5 in trunk does not compile

2009-08-06 Thread William Siegrist 

The inability to login has been fixed.

-Bill



On Aug 5, 2009, at 11:50 PM, Laurent Sansonetti wrote:

Looks like it's impossible to log in for this bug, so I'm replying  
by e-mail...


Building LLVM and MacRuby is only for the developer and LLVM is  
statically linked. In order to ship your app you can either bundle  
MacRuby.framework or compile it ahead-of-time (this one is still  
under development).


Laurent

On Aug 5, 2009, at 11:33 PM, MacRuby wrote:


#302: 0.5 in trunk does not compile
- 
+--

Reporter:  kieran...@…  |Owner:  lsansone...@…
   Type:  defect   |   Status:  closed
Priority:  blocker  |Milestone:  MacRuby 0.5
Component:  MacRuby  |   Resolution:  invalid
Keywords:  bug compile  |
- 
+--


Comment(by kieran...@…):

So in order for someone to ship MacRuby/HotCocoa apps, the person  
using it
has to take the trouble to compile or is the lvvm something  
that can

be bundled in a lightweight form?

--
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] experimental branch: status update

2009-08-06 Thread Laurent Sansonetti 
I started working on that yesterday, but it's not yet done... stay  
tuned :)


Laurent

On Aug 6, 2009, at 1:08 AM, Eloy Duran wrote:

Nope not yet. I personally would like to have something like the  
following up:

http://blog.jimmy.schementi.com/2009/02/ironrubyinfo.html
http://github.com/jschementi/ironruby-stats/tree/master

Which reports a bit on performance and the RubySpec compliance.

Alas, like so many fun things, I haven't had any time yet for it and  
don't see any in the near future. So if you'd like something like  
that as well, please go ahead :)


Cheers,
Eloy

On Aug 6, 2009, at 9:57 AM, Conrad Taylor wrote:

On Wed, Aug 5, 2009 at 4:27 PM, Laurent Sansonetti > wrote:

On Aug 4, 2009, at 1:59 PM, Laurent Sansonetti wrote:
I will proceed with the merge tomorrow at 3PM California time  
(midnight Amsterdam time, 7AM Tokyo time). Feel free to commit  
before, but please hold off your commits at that time :)


OK, I wasn't able to really merge the branch into trunk, because I  
didn't remember which revision of SVN I used to create experimental  
last year (I was experimenting with git at that time), and svn  
merge got confused when I used the default parameters.


Since I'm a lazy person [1], I simply moved trunk as branches/yarv  
and copied branches/experimental as trunk.  This method has the  
inconvenience of losing the history of what happened in trunk  
before, but we can live without it (and it's still available in  
branches/yarv if we can't sleep).


Please make a *fresh checkout* of trunk and let's continue the good  
work there :)


$ svn co http://svn.macosforge.org/repository/ruby/MacRuby/trunk  
macruby-trunk


Laurent

[1] "Laziness is a virtue" - Larry Wall

Hi, revision 2239 looks good:

Finished in 108.039708 seconds

1540 files, 6265 examples, 18457 expectations, 0 failures, 0 errors

Are we tracking the execution time versus the number of  
expectations anywhere?


-Conrad



___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Base64 specs

2009-08-06 Thread dan sinclair 
As far as I can tell, those methods don't exist in the Base64 class on  
Ruby 1.9.2.  Not sure if I'm missing something but I didn't find them.


dan





On Aug 6, 2009, at 3:53 AM, Eloy Duran wrote:


Hey Dan,

By just reading the patch it seems there are no new versions of  
these examples on how the method works on 1.9.x. Could you please  
add those as well?


Cheers,
Eloy

On Aug 5, 2009, at 5:44 AM, dan sinclair wrote:


Hello,

The attached patch marks some specs that don't execute on Ruby  
1.9.2 for me.  The other Base64 specs that are broken are due to  
the TODO in vm_method.c,  rb_mod_modfunc to do with changing scope.


dan


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] Intro, looking to get involved

2009-08-06 Thread Greg Vaughn 
Hello, I thought I'd take a minute to introduce myself. I've seen a  
few posts of people having trouble building, but wanted to report that  
it went clean for me right off the bat. There's a few test failures  
and errors though.


rake spec:ci
Finished in 156.295783 seconds
1553 files, 6256 examples, 18175 expectations, 8 failures, 134 errors

I pulled from the macruby-mirror github repo John-Paul Bader posted  
today.


For starters, are those test failures/errors to be expected? If so, is  
the easiest way to get my feet wet to tackle some of those? Any in  
particular I should avoid because of the complexity for a newbie, or  
that someone else is deep into?


My pedigree, in case that helps anyone nudge me in the right  
direction: taught myself BASIC in Jr. High, Apple II assembler in High  
School, C during college pursuing a Physics degree, first job in  
Newtonscript, Java (for a long time, too long), bought Pickaxe the  
hour it was released . Lately I'm been directing my career more  
towards Ruby and Javascript. Last year was almost all Rails.


I live in the Dallas area. I'm a husband and father, so my free time  
would not be considered copious, but I'm excited about MacRuby and  
will make time to help.


-Greg Vaughn

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #302: 0.5 in trunk does not compile

2009-08-06 Thread MacRuby 
#302: 0.5 in trunk does not compile
-+--
 Reporter:  kieran...@…  |Owner:  lsansone...@…
 Type:  defect   |   Status:  closed   
 Priority:  blocker  |Milestone:  MacRuby 0.5  
Component:  MacRuby  |   Resolution:  invalid  
 Keywords:  bug compile  |  
-+--

Comment(by vincent.isamb...@…):

 Laurent's answer on the mailing list
 (http://lists.macosforge.org/pipermail/macruby-
 devel/2009-August/002175.html):

 Building LLVM and MacRuby is only for the developer and LLVM is statically
 linked. In order to ship your app you can either bundle  MacRuby.framework
 or compile it ahead-of-time (this one is still under development).

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Intro, looking to get involved

2009-08-06 Thread Laurent Sansonetti 

Hello Greg,

On Aug 6, 2009, at 8:02 PM, Greg Vaughn wrote:

Hello, I thought I'd take a minute to introduce myself. I've seen a  
few posts of people having trouble building, but wanted to report  
that it went clean for me right off the bat. There's a few test  
failures and errors though.


rake spec:ci
Finished in 156.295783 seconds
1553 files, 6256 examples, 18175 expectations, 8 failures, 134 errors

I pulled from the macruby-mirror github repo John-Paul Bader posted  
today.


I think these errors are because you did not install MacRuby before  
running the specs.


This is a temporary problem with C extension bundles, they must be  
installed before we can run their specs.


Hopefully this will be very soon fixed.

For starters, are those test failures/errors to be expected? If so,  
is the easiest way to get my feet wet to tackle some of those? Any  
in particular I should avoid because of the complexity for a newbie,  
or that someone else is deep into?


My pedigree, in case that helps anyone nudge me in the right  
direction: taught myself BASIC in Jr. High, Apple II assembler in  
High School, C during college pursuing a Physics degree, first job  
in Newtonscript, Java (for a long time, too long), bought Pickaxe  
the hour it was released . Lately I'm been directing my career  
more towards Ruby and Javascript. Last year was almost all Rails.


I live in the Dallas area. I'm a husband and father, so my free time  
would not be considered copious, but I'm excited about MacRuby and  
will make time to help.


Very glad you like the project :-)

There are various ways to help the project: writing documentation  
(tutorials), creating or porting code examples, finding & reporting  
bugs (and possibly with a patch :-)), helping passing all RubySpecs,  
contributing missing features to the VM/compiler, etc.


Let us know what you prefer to do and we can surely find you work :-)

Laurent
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Base64 specs

2009-08-06 Thread Eloy Duran 
Ok I see, Base64 was removed from 1.9 in favour of using Array#pack  
and String#unpack. Which means we only need to omit it from the ruby  
specific mspec script. In our case macruby.mspec. If it's not yet in  
the obsolete list of libraries in the ruby.1.9.mspec script, then it  
should be added there.


Eloy

On 7 aug 2009, at 02:13, dan sinclair wrote:

As far as I can tell, those methods don't exist in the Base64 class  
on Ruby 1.9.2.  Not sure if I'm missing something but I didn't find  
them.


dan





On Aug 6, 2009, at 3:53 AM, Eloy Duran wrote:


Hey Dan,

By just reading the patch it seems there are no new versions of  
these examples on how the method works on 1.9.x. Could you please  
add those as well?


Cheers,
Eloy

On Aug 5, 2009, at 5:44 AM, dan sinclair wrote:


Hello,

The attached patch marks some specs that don't execute on Ruby  
1.9.2 for me.  The other Base64 specs that are broken are due to  
the TODO in vm_method.c,  rb_mod_modfunc to do with changing scope.


dan


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel