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/jsche
-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
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 have
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
-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
stunt
Woot. Nice work Laurent.
Tres Bien!
-Gp
On 5-Aug-09, at 7: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
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,
On Aug 6, 2009, at 1:49 AM, Laurent Sansonetti wrote:
It seems that the following command could be used:
$ sysctl hw.cpu64bit_capable
On my machines (all 64-bit unfortunately) this returns 1. Could one
on 32-bit check that it returns 0?
$ sysctl hw.cpu64bit_capable
hw.cpu64bit_capable: 0
It seems that the following command could be used:
$ sysctl hw.cpu64bit_capable
On my machines (all 64-bit unfortunately) this returns 1. Could one on
32-bit check that it returns 0?
Thanks,
Laurent
On Aug 5, 2009, at 3:29 AM, Eloy Duran wrote:
The latter seems a good option to me, if you
The latter seems a good option to me, if you have a patch I'll gladly
apply it.
Eloy
On Aug 5, 2009, at 12:25 PM, M. Scott Ford wrote:
This is the last experimental branch status update, we accomplished I
think all the goals required to merge the branch into trunk. There
will be more status
> This is the last experimental branch status update, we accomplished I
> think all the goals required to merge the branch into trunk. There
> will be more status updates after, but they will focus on trunk and
> the 0.5 release objectives :)
To be clear, this means that the trunk is going to be b
On Wed, Aug 5, 2009 at 2:17 AM, Conrad Taylor wrote:
>
>
> On Wed, Aug 5, 2009 at 2:13 AM, Laurent Sansonetti
> wrote:
>
>> Hi Conrad,
>>
>> On Aug 5, 2009, at 2:00 AM, Conrad Taylor wrote:
>>
>>> Laurent
>>>
>>> I'm seeing the following warning messages after "sudo rake install":
>>>
>>> unknow
On Wed, Aug 5, 2009 at 2:13 AM, Laurent Sansonetti wrote:
> Hi Conrad,
>
> On Aug 5, 2009, at 2:00 AM, Conrad Taylor wrote:
>
>> Laurent
>>
>> I'm seeing the following warning messages after "sudo rake install":
>>
>> unknown: warning: File::new() does not take block; use File::open()
>> instead
>
Hi Conrad,
On Aug 5, 2009, at 2:00 AM, Conrad Taylor wrote:
Laurent
I'm seeing the following warning messages after "sudo rake install":
unknown: warning: File::new() does not take block; use File::open()
instead
Sorry about that, I just fixed that in r2219.
Also, running "rake spec:ci"
On Tue, Aug 4, 2009 at 1:59 PM, Laurent Sansonetti wrote:
> Headlines:
>
> - macirb should work as before. The local variable bug has been fixed.
>
> - macrake should work as before. Running HotCocoa projects should work, you
> can even build MacRuby with macrake.
>
> - new YAML module, API compat
On 04.08.2009, at 22:59, 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 :)
This screams for a DVCS but I guess you already had that d
Headlines:
- macirb should work as before. The local variable bug has been fixed.
- macrake should work as before. Running HotCocoa projects should
work, you can even build MacRuby with macrake.
- new YAML module, API compatible with syck, was added. It is still
under development, but it's
>
> - The strscan C extension was rewritten in pure Ruby and imported into the
> repository. All the specs but one pass and new specs have been written too.
>
Just a tiny clarification, the new Ruby version passes all the Rubyspecs
available upstream, however I added and modified specs to be 1.9 c
Here is another status update on the experimental branch. I forgot to
send this one earlier, sorry.
Highlights:
- Unicode strings! You can now create strings containing multibyte
characters in your MacRuby programs and apply the String methods on
them (even regular expressions!).
- Diges
Boomshakalaka, you's the man!
On 12 jul 2009, at 07:25, Laurent Sansonetti wrote:
Another update on the experimental branch!
Highlights are:
- A much better AOT (ahead-of-time) compiler, now available as a
separate command line executable, macrubyc. It can compile some
MacRuby sample code
Another update on the experimental branch!
Highlights are:
- A much better AOT (ahead-of-time) compiler, now available as a
separate command line executable, macrubyc. It can compile some
MacRuby sample code. Details at the very end of this message.
- IB support is back! Once you install e
The clang support seems to be pretty solid. It does use llvm-g++ to
compile the C++ files as noted, so that helps while clang itself
doesn't do C++.
I am attaching another patch that helps out when clang can't be found
in /usr/bin, and also looks for gcc/g++ in /Developer (or where you
ha
Awesome job Laurent, as usual!
- Matt
On Mon, Jun 29, 2009 at 1:19 PM, Laurent Sansonetti
wrote:
> Last week's status on the experimental branch work!
>
> - It's now possible to build MacRuby with clang (assuming you installed it)
> by issuing the following command:
> $ rake use_clang=true minir
Last week's status on the experimental branch work!
- It's now possible to build MacRuby with clang (assuming you
installed it) by issuing the following command:
$ rake use_clang=true miniruby
This will compile all C and Objective-C files with clang and C++ files
with llvm-g++. Apparently th
Yet another status update on the experimental branch work!
Highlights are:
- More Ruby & Cocoa compatibility work. All samples should now run on
experimental on both 10.5 and 10.6. Rake and HotCocoa are now somewhat
usable (but not at 100% yet).
- Floating-point arithmetic optimization (se
Another week, another status update on the experimental branch!
Highlights are:
- A much better Cocoa support. We are almost as stable as trunk, I
think. I was able to run a significant internal MacRuby application
with the experimental branch.
- The project is now able to be installed and
Hi Rich,
I forgot to mention that 32-bit support is a bit b0rked for now, which
is probably what's problematic in your case.
Laurent
On May 29, 2009, at 1:59 PM, Rich Morin wrote:
As of revision 1634, my PPC build is still failing in spots.
See http://cfcl.com/rdm/macruby/2009.0529.0500 fo
As of revision 1634, my PPC build is still failing in spots.
See http://cfcl.com/rdm/macruby/2009.0529.0500 for details.
-r
...
You appear to be using a PowerPC machine. MacRuby's primary
architectures are Intel 32-bit and 64-bit (i386 and x86_64).
Consequently, PowerPC support may be lackin
Hi all,
The last status was sent the 4th May, so this one is a bit lengthy. I
am sorry about that and I will try to do status updates more often.
Before listing the changes, 2 important things happened since and I
think they need to be mentioned!
- The very first RubyOnOSX conference was
I'd be glad to help you review your samples and commit them to the repo when
ready since Laurent seems to encourage community submitted samples.
- Matt
On Thu, May 7, 2009 at 3:18 PM, Laurent Sansonetti wrote:
> Hi Brian
>
> Afaik you are the first to work on this ;-)
>
> As you could see I port
Hi Brian
Afaik you are the first to work on this ;-)
As you could see I ported several of them to rubycocoa and macruby as
part of their respective sample code, so feel free to reuse the
existing work.
Regarding macruby I think it would be awesome to ship them with the
project, ultimatel
On May 7, 2009, at 4:19 PM, Matt Aimonetti wrote:
On May 4, 2009, at 5:35 PM, Laurent Sansonetti wrote:
We can pass more Cocoa examples thanks to that.
I've started translating the examples in /Developer/Examples into
RubyCocoa & MacRuby. Is the MacRuby part redundant?
http://github.com/m
You probably meant: Ist the RubyCocoa part redundant? right? ;)
- Matt
On Thu, May 7, 2009 at 1:26 PM, Brian Marick wrote:
>
> On May 4, 2009, at 5:35 PM, Laurent Sansonetti wrote:
>
> We can pass more Cocoa examples thanks to that.
>>
>
>
> I've started translating the examples in /Developer/
On May 4, 2009, at 5:35 PM, Laurent Sansonetti wrote:
We can pass more Cocoa examples thanks to that.
I've started translating the examples in /Developer/Examples into
RubyCocoa & MacRuby. Is the MacRuby part redundant?
http://github.com/marick/cocoa-examples-translated/tree/master
Here is the weekly status update of the experimental branch! I'm sure
you were all expecting it and holding your breath!
- Implemented BridgeSupport constants, in a lazy fashion (the symbol
is retrieved and converted at demand).
- The Pointer class was re-implemented. Same behavior as in tr
A status update on the recent progresses on the experimental branch!
Last week did not see a status update, mea culpa.
- A new C/Objective-C dispatcher has been written. The idea is to use
LLVM to compile stubs instead of using libffi. The previous libffi-
based implementation is no longer u
> - Vincent started working on a spec regarding 1.9 string encodings!
As Laurent said I commited a spec for String#valid_encoding? last week
and I just commited a second one (String#getbyte).
It's just a start and I intend to make more of those but I gladly
accept any help. I probably have forgott
Another week, another status update on the experimental branch!
Unfortunately, the work done this week was pretty light.
- More work on IO (IO#readlines, IO#each_byte and IO#each_char).
- A better implementation for catch/throw was added.
- Tail-call elimination was introduced. This optimizat
slightly out topic: w00t!! great job guys!
- Matt
2009/4/7 Eloy Duran
> Hi,
> I just added a spec:ci32 task which will run the specs in 32 bit mode.
> It uses a simple script (miniruby32) which runs miniruby through
> /usr/bin/arch.
>
>
> http://github.com/alloy/mr-experimental/commit/321cc9b0
Hi,
I just added a spec:ci32 task which will run the specs in 32 bit mode.
It uses a simple script (miniruby32) which runs miniruby through /usr/
bin/arch.
http://github.com/alloy/mr-experimental/commit/321cc9b0ae0acce82bdb59bdc11e4f688e6233c6
And indeed :)
% rake spec:ci32
(in /Users/eloy/D
Hi Chris,
I've finally had some time to write an explanation on how to work on
the specs.
You can find it in spec/README.rdoc, or view it at:
http://github.com/alloy/mr-experimental/blob/master/spec/README.rdoc
Let me know if there are any questions, I probably left out important
parts ;-)
Based on that I would say that it is a good idea going forward to try
having 64-bit machines run tests in 64-bit and 32-bit mode. I look
forward to seeing any solution to running the tests in 32-bit mode
that you come up with.
Jordan
On Apr 06, 2009, at 13:07, Eloy Duran wrote:
Hmm, so i
Hmm, so it's indeed a 32/64 bit issue.
Thanks for trying Mike!
- Eloy
On 6 apr 2009, at 18:56, Mike Moore wrote:
On Mon, Apr 6, 2009 at 3:16 AM, Eloy Duran
wrote:
One last question I have for everyone on the list. If there's
someone with a 32 bit intel machine, could you please please r
On Mon, Apr 6, 2009 at 3:16 AM, Eloy Duran wrote:
>
> One last question I have for everyone on the list. If there's someone with
> a 32 bit intel machine, could you please please run the spec:ci task and see
> if you get any failures?
> It seems that, at least, because of a 32/64 bit issue some I
On Mon, Apr 6, 2009 at 10:16 AM, Eloy Duran wrote:
> If there are people who would like to work on getting examples up-to-date,
> please respond and I will try to give you an outline on a workflow.
>
I'd be interested in helping out, but atm I'm not up to speed enough
to have even built the exper
1) test for 64-bit enabled machines, if you are on a 32-bit
machine build normally an run specs normally
2) ok you are on a 64-bit machine, during build make miniruby and
miniruby32 (which can be made with lipo from miniruby, something
like `lipo -extract i386 -output miniruby 32 miniruby`)
On Apr 06, 2009, at 08:40, Eloy Duran wrote:
On Apr 6, 2009, at 3:28 PM, Jordan Breeding wrote:
On Apr 06, 2009, at 08:09, Eloy Duran wrote:
Ah, on that bike! (Which is a direct translation of a Dutch saying
meaning basically just "Aha!" ;-) )
Yes that sounds like an excellent idea, will
On Apr 6, 2009, at 3:28 PM, Jordan Breeding wrote:
On Apr 06, 2009, at 08:09, Eloy Duran wrote:
Ah, on that bike! (Which is a direct translation of a Dutch saying
meaning basically just "Aha!" ;-) )
Yes that sounds like an excellent idea, will do.
Thanks,
Eloy
After taking a quick look a
On Apr 06, 2009, at 08:09, Eloy Duran wrote:
Ah, on that bike! (Which is a direct translation of a Dutch saying
meaning basically just "Aha!" ;-) )
Yes that sounds like an excellent idea, will do.
Thanks,
Eloy
After taking a quick look at the spec tasks and the way they run it
might be e
Ah, on that bike! (Which is a direct translation of a Dutch saying
meaning basically just "Aha!" ;-) )
Yes that sounds like an excellent idea, will do.
Thanks,
Eloy
On Apr 6, 2009, at 2:54 PM, Jordan Breeding wrote:
On Apr 06, 2009, at 07:50, Eloy Duran wrote:
As Laurent noted we are now
On Apr 06, 2009, at 07:50, Eloy Duran wrote:
As Laurent noted we are now passing most language specs. The ones
that we don't pass yet are either because we simply fail, or these
examples (tests) are simply not updated for Ruby 1.9 yet. Which as
you all know is what MacRuby is based on. Thi
As Laurent noted we are now passing most language specs. The ones
that we don't pass yet are either because we simply fail, or these
examples (tests) are simply not updated for Ruby 1.9 yet. Which as
you all know is what MacRuby is based on. This is an area where all
of you Ruby devs can he
On Apr 06, 2009, at 04:16, Eloy Duran wrote:
Hi,
On Apr 6, 2009, at 10:47 AM, Laurent Sansonetti wrote:
Hi guys,
I figured out that it would be a good idea to give periodical
status updates on what's happening in the experimental branch, so
here is the first one :)
- The compiler is no
Hi,
On Apr 6, 2009, at 10:47 AM, Laurent Sansonetti wrote:
Hi guys,
I figured out that it would be a good idea to give periodical status
updates on what's happening in the experimental branch, so here is
the first one :)
- The compiler is now able (AFAIK) to compile all the language
sp
Hi guys,
I figured out that it would be a good idea to give periodical status
updates on what's happening in the experimental branch, so here is the
first one :)
- The compiler is now able (AFAIK) to compile all the language specs,
so I guess it's now roughly complete.
- Lots of progres
55 matches
Mail list logo
