Hi,
i have the problem, that under MacRuby cropping of an CIImage fails.
Whether i use CIFilter or CIImage#imageByCroppingToRect.
Whereas a Cocoa-Application the same code works just fine, my Ruby
version repeats the same cropped Image over and over again.
Have a look at the Screenshot:
htt
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
Am 06.04.2009 um 10:52 schrieb Laurent Sansonetti:
Did you try the Objective-C version in 1) a garbage-collected
environment 2) 64-bit?
My XCode build settings state the following:
Architectures: Standard (32-bit)
Objective-C Garbage Collection: Unsupported
Ben
__
Hi all,
I would like to try MRE[1] on my laptop with coexisting the last stable version
0.4
To do that, I have installed LLVM into a directory named ~/local
and I have specified during the installation of MRE[1] that rake must install it
into the directory ~/Library/Frameworks with the followin
Hi Stephane,
The experimental branch does not install yet. The only thing you can
do is to build miniruby (rake miniruby) and use that.
Eg: $ ./miniruby -e "p :foo"
Eloy
On Apr 6, 2009, at 12:31 PM, Stephane Wirtel wrote:
Hi all,
I would like to try MRE[1] on my laptop with coexisting the
Hi Eloy,
Thank you for your reply,
What's the relation between miniruby and MacRuby ?
Stephane
On 06 Apr 2009, at 12:39, Eloy Duran wrote:
Hi Stephane,
The experimental branch does not install yet. The only thing you can
do is to build miniruby (rake miniruby) and use that.
Eg: $ ./mini
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 Benjamin,
On Apr 6, 2009, at 1:38 AM, Benjamin Mollenhauer wrote:
Hi,
i have the problem, that under MacRuby cropping of an CIImage fails.
Whether i use CIFilter or CIImage#imageByCroppingToRect.
Whereas a Cocoa-Application the same code works just fine, my Ruby
version repeats the same
On Apr 6, 2009, at 12:58 PM, Stéphane Wirtel wrote:
Hi Eloy,
Thank you for your reply,
What's the relation between miniruby and MacRuby ?
miniruby is basically the same as the ruby binary that we all know and
love, but _before_ it is installed.
If you compile ruby (any MRI version) you wil
Did you try the Objective-C version in 1) a garbage-collected
environment 2) 64-bit?
Thanks for pointing me in the right direction:
In my Ruby project Architecture was set to "$(NATIVE_ARCH_ACTUAL)",
probably due the use of the "MacRuby Application" project template.
I changed it to "Native
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
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 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
Thank you,
Stef
Eloy Duran wrote:
On Apr 6, 2009, at 12:58 PM, Stéphane Wirtel wrote:
Hi Eloy,
Thank you for your reply,
What's the relation between miniruby and MacRuby ?
miniruby is basically the same as the ruby binary that we all know and
love, but _before_ it is installed.
If you co
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 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
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: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
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 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
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
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
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
Hi,
MacRuby is getting better and better at great speed, but there is one
point where MacRuby still has much to do: strings, encodings and IO.
If you have some interest in that, but do not know Ruby 1.9's strings
well, I recommend you check at least the 2 last posts of James Gray
II's series abou
On Apr 7, 2009, at 7:47 AM, Vincent Isambart wrote:
I have two small comments and a general statement about your essay;
A few functions of 1.9 may also be disabled (like force_encoding). Of
course it would be possible to add the full functionality of Ruby 1.9
strings on ByteString but it would
> Finally; I don't think it's a good idea to discuss this a great length
> without actual code but in order to write a compatible implementation most
> (if not all) of the String awkwardness will have to be implemented.
Thank you very much for the remarks. We will indeed need to go to
actual code
26 matches
Mail list logo
