Hi,
I've been working on rewriting the preferences code of LimeChat
and have now extracted it for use in other projects.
I thought it might be interesting for HotCocoa as well.
See the readme and tests for an idea of the usage:
http://github.com/alloy/rubycocoa-prefs/tree/master
Currently it's
Hi Matt,
This is a crash report submit plugin I wrote.
It currently only supports RubyCocoa, but I guess it would be trivial
to get it to run on MacRuby.
Maybe Laurent already ported it, because it's used by LimeChat as well:
http://rucola.rubyforge.org/svn/extras/plugins/SACrashReporter/
Ch
I wonder if it really would add much benefit to add a CoreData DM
adapter…
I would just use DM with sqlite, without CoreData adding an extra
layer of abstraction.
This works in RubyCocoa, so except for maybe some incompatibilities
with 1.9/MacRuby
it should work great as well.
Eloy
On 9 no
Hi,
I like the idea of HotCocoa, but it should not go too far, and this is
maybe taking it one step too far imo.
The problem is that at some point you _will_ have to use real Cocoa,
because HotCocoa can't wrap everything.
If you are frightened by the verbosity of this line of code, well than
On 9 nov 2008, at 16:19, Matt Aimonetti wrote:
hmm I guess I disagree but since I just got started with MacRuby and
don't know Cocoa I might be totally wrong.
Yes, this is what I thought too when first starting with Cocoa in
RubyCocoa, but I was very wrong.
Most helpful docs/references are
Have you tried building it without using RubyGems?
- Eloy
On 9 nov 2008, at 16:14, Matt Aimonetti wrote:
DM uses DO which uses C extensions and C drivers. I'm not sure how
to get DM working with MacRuby yet :(
-Matt
On Sun, Nov 9, 2008 at 10:09 AM, Eloy Duran
<[EMAIL PROTECTED
Here's some code which does that:
http://github.com/alloy/rucola/tree/master/lib/rucola/tasks/deploy.rake
- Eloy
On Nov 11, 2008, at 1:38 PM, Richard Kilmer wrote:
As always, Laurent did all the hard work!
I also wonder whether it makes sense to add 'package' or something
as a rake task tha
On Nov 12, 2008, at 4:31 PM, Matt Aimonetti wrote:
One thing the "cowboys", from Rails for instance, have done right
is that there are tests for almost everything,
which is something that is seriously lacking atm imo.
Rails testing suite is in a very sad state,
Definitely not going to argue
Hi Rich,
That seems like a sensible list to me.
Thanks for the info!
- Eloy
On Nov 12, 2008, at 4:10 PM, Richard Kilmer wrote:
On Nov 12, 2008, at 9:16 AM, Richard Kilmer wrote:
All,
As the main author of HotCocoa let me chime in on what I see its
main purpose is.
In a nutshell here i
* Focus on design and engineering
In an age of "cowboy programming", I find it refreshing to
see that some programming projects actually embrace design
and engineering.
One thing the “cowboys”, from Rails for instance, have done right
is that there are tests for almost everything,
which i
The result we're looking for (IMHO) is a way to write Cocoa apps
that "look right" to Ruby programmers. The number of Objective-C
programmers who don't work on OSX apps is vanishingly small.
By opening up OSX programming to MacBook-carrying Rubyists, Apple
can grow its developer base in relative
Hi listees,
The critical question, then, is how to create an environment that
allows
(nay, encourages!) frameworks to be created, tested, polished,
documented,
indexed, shared, etc. My intuition is that GitHub should be part of
this,
because it promotes free-flowing cooperation, merging, e
OK; here's a partly-baked idea, loosely inspired by Python
docstrings.
The HC declarations are (I assume) stashing information away in some
sort of data structure. If not, they certainly could be (:-). Once
the information is available at runtime, any HC script could
retrieve
them for
Hi Chris,
What a coincidence :) gen_bridge_doc is the tool I was speaking of in
an email I've just send in this thread :)
Eloy
On Dec 3, 2008, at 9:34 AM, Chris McGrath wrote:
On 3 Dec 2008, at 04:05, Richard Kilmer wrote:
The mapping files do create data structures, I was totally going
Hi Laurent,
I agree HotCocoa should be covered by tests, at least to catch
regressions.
HotCocoa was initially started as an experiment and we (well, Rich)
iterated a lot on the interface, now it's maybe time to start
thinking about freezing some parts of the API (most probably the
mapp
db's you mean?
On Dec 3, 2008, at 10:42 AM, Laurent Sansonetti wrote:
On Dec 3, 2008, at 12:56 AM, Eloy Duran wrote:
OK; here's a partly-baked idea, loosely inspired by Python
docstrings.
The HC declarations are (I assume) stashing information away in
some
sort of data str
On Dec 3, 2008, at 11:26 AM, Laurent Sansonetti wrote:
On Dec 3, 2008, at 2:09 AM, Eloy Duran wrote:
Hi Laurent,
I agree HotCocoa should be covered by tests, at least to catch
regressions.
HotCocoa was initially started as an experiment and we (well,
Rich) iterated a lot on the
Hiya,
As someone experiencing this discussion from the 3rd person
perspective, I'd like to chime in.
The current issue seems to be that there are some problems with the
current MR,
which will get properly fixed by a future software update.
Until then there apparently is the need to work
About this. More than anything, I'd like to keep discussions on the ML,
because I cannot express enough the hatred I feel for the format of
Trac's emails :-)
Eloy
On 8 dec 2008, at 22:35, Jordan K. Hubbard wrote:
Guys?
This is a very suboptimal, to say nothing of weird, way to
communicat
Your best bet is to take a look at the bridgesupport files for most
system frameworks
and learn from those. They are found inside Resources/BridgeSupport.
Nonetheless, it would indeed be very nice if a more elaborate guide
could be written.
Eloy
On Dec 19, 2008, at 4:45 PM, Jim Getzen wrot
No RubyGems does not work in the current trunk.
The specific problem you are running into is a problem with YAML,
filed at: https://www.macruby.org/trac/ticket/187
Only thing you can do atm is to try and install the library by hand.
- Eloy
On 26 dec 2008, at 17:25, Tim Rand wrote:
I know proble
Hi,
While porting Rucola to MR, I noticed MR throws warnings like:
“macruby(686,0x10366b000) malloc: free_garbage: garbage ptr =
0x8004d8de0, has non-zero refcount = 1”
What is the significance of this?
Should I do something different?
- Eloy
___
M
Hi (Laurent),
I have been busy making mocha work on MR, which somewhat works now:
http://github.com/alloy/mocha/commits/macruby
But there are quite some other interesting failures with the mocha
tests, which might be interesting to look into.
Cheers,
Eloy
% macrake test:units
(in /Users/e
tcher(InstanceOfTest)
[/Users/eloy/Documents/DEVELOPMENT/MacRuby/mocha/test/unit/
parameter_matchers/instance_of_test.rb:22]:
<"instance_of(String)"> expected but was
<"instance_of(NSMutableString)">.
perhaps: assert_equal(str, str.to_s) instead?
On Wed, Dec 31, 2008
Hey Vincent,
Is there a good reason why MacRuby would need to warn the user
about the hazzards of removing methods?
Example:
/Library/Frameworks/MacRuby.framework/Versions/0.4/usr/lib/ruby/
site_ruby/mocha/class_method.rb:50: warning: removing pure
Objective-C method `__stubba__require__stu
Hi,
Is there a good reason why MacRuby would need to warn the user about
the hazzards of removing methods?
Removing methods is always a risky business, also in pure Ruby. But
this is the power that a Ruby user gets and with it comes
responsibility.
And since Ruby doesn't warn for this, MacR
I have discussed this with Laurent and will post the results here for
completeness.
The problem with the objc runtime is that if a method were to be
removed and is called from the objc runtime,
it would lead to seg faults. Therefor the warning is raised, so people
don't have to look through
Yes, that might be a better option.
In my naivety, I mentioned this to Laurent as well, but it got lost in
the discussion a bit.
So Laurent, any input?
Eloy
On Jan 6, 2009, at 11:17 AM, Matt Mower wrote:
On Tue, Jan 6, 2009 at 9:55 AM, Eloy Duran
wrote:
on pure objc classes. It would
How about @text_view.setString("foo") or as @text_view.string = "foo" ?
http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/NSText_Class/Reference/Reference.html#/
/apple_ref/doc/uid/2367-setString_
- Eloy
On 13 jan 2009, at 00:46, Timothy McDowell wrote:
Y'kn
DF (it has
not been released yet to paper I believe) from the Pragmatic
Programmers.
Both Marick's and Hillegas's books are important reads for the
beginning (eg me) macruby programmer.
Cheers,
J
On Jan 13, 2009, at 1:22 AM, Eloy Duran wrote:
How about @text_view.setSt
Hi,
Today I merged some patches by Alexander Flatter.
He wrote some test cases for HotCocoa, namely: mapping_test.rb,
mappings_test.rb, and plist_test.rb.
And he also merged and tested Vincent's patch #209.
http://www.macruby.org/trac/ticket/209
So first, thanks to you both! :)
There are sti
Hey,
The test looks good to me and I totally agree, false is more
unexpected then nil in this case.
So then I looked up the tests for it from extlib:
http://github.com/sam/extlib/blob/2bc2e8a42c7a49e2e5daf530c29fb2840d0e299d/spec/object_spec.rb#L29
And it doesn't even test for the case that a
; A::B
Object.full_const_get 'A::B'
=> A::B
/SNIP
Giving some tests back to extlib should be no problem.
On Thu, Jan 22, 2009 at 12:06 AM, Eloy Duran
wrote:
Hey,
The test looks good to me and I totally agree, false is more
unexpected then
nil in this case.
So then
isted as the only one. ;-)
I'll try to take look into the graphics demo and see what's wrong.
Greetings
On Tue, Jan 20, 2009 at 9:13 PM, Eloy Duran
wrote:
Hi,
Today I merged some patches by Alexander Flatter.
He wrote some test cases for HotCocoa, namely: mapping_test.rb,
mappin
Hey Nic,
Even though a page about RubyCocoa, the steps descried there are
pretty general:
http://rubycocoa.sourceforge.net/EmbedRubyCocoa
The standaloneify script that's mentioned there might give you insight
in what you
would need to do to bundle everything.
Cheers,
Eloy
On 23 jan 2009,
repo with these
patches applied? Or do you have one already?
Cheers
Nic
On Fri, Jan 23, 2009 at 8:30 PM, Matt Mower
wrote:
On Fri, Jan 23, 2009 at 10:21 AM, Eloy Duran > wrote:
Even though a page about RubyCocoa, the steps descried there are
pretty
general:
http://rubycocoa.sourceforge
Hi Arlen,
Welcome to the list and MacRuby in general and thanks for your patch!
I'd love to take a look at your patch, however, as I've noted on the
ticket
please add test coverage of the problem it fixes first.
And then we'll discuss it further on the ticket.
Cheers,
Eloy
On Jan 26, 2009,
Hi,
As some of you might already know, we are organizing a Ruby and Cocoa
only conference in may in Amsterdam.
This email is purely meant as a request for proposals, so we can work
on the schedule.
Once we have the details we will post an elaborate article about it on
our blog.
So please
I downloaded hotconsole, but can't seem to get it raked / built /
installed. I can't find any install instructions. There is a
mention that you need the latest branch, so I grabbed the testing
branch and built it, but still no luck with hotconsole.
The latest code is in trunk. The testing
Hi,
As most people know installing gems on MacRuby still fails for most
gems.
I was getting so annoyed looking through the source of RubyGems
that I decided to write a clean room implementation of it.
For now it only does installing, but was the only goal since that's
what fails on MacRuby.
ct but may I suggest you drop
the µ letter that most of us probably don't know how to type :
( Sticking to ASCII might be better.
- Matt
On Mon, Feb 9, 2009 at 12:40 AM, Eloy Duran
wrote:
Hi,
As most people know installing gems on MacRuby still fails for most
gems.
I was getting
Hehehe, ok ok ok.
I surrender…
http://files.myopera.com/Inquisitor/files/old_forum_import/surrender.jpg
Just released 0.2.0 which includes as an alternative the way lamer
version: `ugem' ;-)
- Eloy
On 9 feb 2009, at 23:43, John Barnette wrote:
On Mon, Feb 9, 2009 at 1:36 AM, Eloy
Hi,
If this is a problem with the Objective-C Hash implementation, I would
be inclined to say that the test case should go in test-macruby/cases/
rubyspec/hash_test.rb.
Because we might need to move this into the rubyspec project, if it's
not already in there, once we start on integrating ru
patch.
I glanced at the hash tests in the RubySpec project and there is not
much there, so moving this test into RubySpec sounds like a good
idea. Is that something that I should take care of now?
-Scott
On Feb 12, 2009, at 8:53 AM, Eloy Duran wrote:
Hi,
If this is a problem with the
, or that I might have
missed another part of your tests.
- Eloy
On 12 feb 2009, at 16:29, M. Scott Ford wrote:
Eloy,
Here is an updated patch that uses spec style tests.
-Scott
On Feb 12, 2009, at 9:16 AM, Eloy Duran wrote:
Hi Scott,
If you would like to re write your patch in a more
Hi Tim,
I think you meant to direct your question at me rather then Matt, but
since you're using the Greek character you are forgiven for anything ;-)
So the problem with sqlite3 is that it requires a C extension, which
is one of the things not yet supported by MicroGem.
I don't think it's
No, please just use trunk. You can switch the "location" of a
checkout: http://svnbook.red-bean.com/en/1.0/re27.html
Laurent, should we remove the testing branch, I think it's misleading
and un-useful atm.
Cheers,
Eloy
On Feb 8, 2009, at 3:43 PM, Pedo Borges wrote:
Checkout the testing b
Hey Matt,
I think a gem is fine. You can always choose to vendor it when you
deploy. (Something which Rucola for instance does.)
Taking on the responsibility of a dependency framework is a bit too
far away from where the current focus of MacRuby should lie imho.
Eloy
On 9 mrt 2009, at 22
deal with this
issue cleanly.
- Matt
On Mon, Mar 9, 2009 at 2:58 PM, Eloy Duran
wrote:
Hey Matt,
I think a gem is fine. You can always choose to vendor it when you
deploy. (Something which Rucola for instance does.)
Taking on the responsibility of a dependency framework is a bit too
Hi,
Have you included the Gems directory in your xcode project so that it
copies the complete dir when building?
This probably then tells you that the dir does not exist "p File.exist?
(File.expand_path('../Gems', __FILE__))".
Second, are you sure you actually need rubygems if you are alread
I think you've translated that a little wrong. This is untested, but
I'd suggest trying:
def webView(sender, didReceiveTitle:title, forFrame:frame)
sender.window.setTitle(title)
end
Does that sound right to anybody else? The method name should be the
bit after the first ), and before
No definitely not. This is Ruby, so we can do better ;-)
I have not yet finished porting Rucola to MacRuby, as of yet MacRuby
is not mature enough to run some code we have on RubyCocoa yet.
However, the port process was started, especially on our test case
helper, so this might currently wo
Yeah after some extensive benchmarking it seemed the performance of
(Mac)Ruby was never gonna be enough compared to perl.
An example of some code that 99% of the apps exist of:
% time ./miniruby -e "print 'hello world'"
hello world./miniruby -e "print 'hello world'" 0,05s user 0,08s
system 8
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,
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
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
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
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
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
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`)
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 ple
parts ;-)
Cheers,
Eloy
On 6 apr 2009, at 17:39, Chris McGrath wrote:
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 h
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 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,
It;'s not clear to me whether you're talking about purely MRI Ruby 1.9
or MacRuby.
At least with MacRuby there are indeed problems with RubyGems, see the
tickets.
Cheers,
Eloy
On Apr 9, 2009, at 5:23 PM, K H wrote:
Hi. I switched my ruby to 1.9.1 on OS X.5.6. I figured there's no
point to
Hey John,
I think we'll need to move the to_yaml definition for String into
NSString in the MacRuby case.
I tried to do that as an example [1], but it seems that NSString
completely breaks after opening the class, but this is probably just a
bug in 0.4:
"--- foo\n"
"--- !str:NSString foo\
Hi Matt,
Testing is indeed an area I find interesting. But it's not so much
that I like testing itself, but rather the results that one can
achieve with it. Be it fixing bugs or rigorously refactoring. Real UI
testing, like Squish does, is very cumbersome imo, maybe that's why
that testin
Oh hey, thanks for pointing me to it again. There's nothing wrong with
that article I failed at properly looking at the article. I think the
layout instantly reminded me of an article which suggested installing
ruby into /usr which a lot of people did and consequently broke their
installati
Hi, another not-Laurent here,
On the topic of the RubySpec, which Jordan mentions as RSpecs; I have
written a README on how to help out with the specs:
http://github.com/alloy/mr-experimental/blob/master/spec/README.rdoc
Cheers,
Eloy
On 29 mei 2009, at 06:35, Jordan K. Hubbard wrote:
On M
I haven't actively spoken about this with Laurent over the last week,
but afaik not much changed since last time, which means that the
support is not nearly far enough to start using it. We decided that we
want the FFI specs in the repo in order to finish this work
appropriately, which woul
Spot on :)
On 29 mei 2009, at 23:10, Rich Morin wrote:
At 14:01 -0700 5/29/09, Tim Rand wrote:
Tim Rand added you as a friend on MyLife™.
Please confirm you know Tim so we can connect you.
Do you know Tim?
Sorry, Tim, MacRuby likes you, but is too busy right now
(what with all the surgery,
Hi,
Yes, any help would be very nice!
Over the last few days I have been tagging as much of the core specs
as possible. Which means that the total of specs we now run is:
886 files, 3742 examples, 12050 expectations, 0 failures, 0 errors
However, of all the tagged specs, not all are failures
No you're not. Unfortunately xcode does not have Ruby specific debug
support. The debugger will give you GDB, which _can_ be used with
Ruby, but I have not tried it with MacRuby yet.
The more general solution is to use ruby-debug, but again, I haven't
tried it with MacRuby yet.
Good luck :)
What would be great is if you could first complete the openssl part of
the rubyspec, which desperately needs some love.
Once that's done, and someone helped you out with a dev. setup, you
can use it to make sure the port works as it should.
Eloy
On 5 jun 2009, at 09:52, Allison Newman wrote:
Don't worry Eloy, I wouldn't dream of writing code before having
written the tests first ;-)
On Friday, June 05, 2009, at 10:05AM, "Eloy Duran" > wrote:
What would be great is if you could first complete the openssl part
of
the rubyspec, which desperately needs some love.
O
Ah there are even some samples:
http://kenai.com/projects/ruby-ffi/sources/mercurial/content/samples
On 5 jun 2009, at 10:11, Eloy Duran wrote:
Awesome Alli :D
Maybe that the specs of Ruby-FFI can give you the insights on how to
use it?
It would be best to work on a clone of rubyspec
Hi Markus,
Very nice! Thanks a lot.
If people who didn't have LLVM and MacRuby 0.5 compiled try this,
please report if it works so we can add info about it to the README.
Eloy
On 6 jun 2009, at 21:30, Markus Prinz wrote:
Hey everyone,
Since not everyone has the time and patience to compi
I think this is the one you mean:
http://github.com/atduskgreg/MacRuby-Document-App-Template/tree/master
Eloy
On 17 jun 2009, at 09:23, Matt Aimonetti wrote:
I believe someone already worked on a template like that, you might
want to do a twitter search before giving it a try.
- Matt
On T
Hi Pual,
I sometimes use GDB when I need to debug RubyCocoa/MacRuby
_themselves_, as they're written in C. For Ruby code, however, I
almost never need a debugger.
Maybe it's because I write most code test driven so I know that the
code is probably ok when I actually use it. In the cases wh
bugger but that might be cool.
- Matt
On Thu, Jun 18, 2009 at 12:33 AM, Eloy Duran
wrote:
Hi Pual,
I sometimes use GDB when I need to debug RubyCocoa/MacRuby
_themselves_, as they're written in C. For Ruby code, however, I
almost never need a debugger.
Maybe it's because I wr
I had a little play with IRB. With some “easy” workarounds, plain Ruby
at least, I was able to get IRB in the right context. However, on
MacRuby (at least on 0.5), this doesn't work completely, as the
binding of a proc returns the wrong context:
% ruby -e "class Foo; def initialize; p eval(
Hi Perry,
I wouldn't worry too much about duplicate efforts, there aren't many
people working on the core itself.
What you could do to start out, is to run the rubyspecs in spec/frozen/
language, as they should all run iirc, but there are some tagged ones.
To run spec all which are tagged as
Hi,
I'm not sure if you want this traffic on the list.
Sure no problem, it's not that we that much traffic yet :)
I got everything compiled, etc. Ran the command below and captured
the output. As you mentioned, there is a segment fault.
I installed ruby 1.9.1p129 and changed the command
Ugh, sorry Perry. It seems I forgot to actually send my email...
Anyways, Mike is correct. For more info on MSpec, and all the options
for the runners, see: http://rubyspec.org/wiki/mspec
Eloy
On Jul 7, 2009, at 10:36 PM, Mike Sassak wrote:
On Fri, Jul 3, 2009 at 9:30 AM, Perry Smith wrote
Yes indeed, the ones that segfault should be tagged as critical.
To list all current critical tags:
$ ./mspec/bin/mspec tag --list critical -B ./spec/macruby.mspec :full
Cheers,
Eloy
On Jul 10, 2009, at 4:21 AM, Laurent Sansonetti wrote:
I think the plan is to tag these as "critical". At least
I think Laurent will write specific MacRuby specs for these
differences, so you could look it up from there and write the wiki. Or
others interested could simply check the specs to see it for themselves.
Eloy
On Jul 9, 2009, at 10:12 PM, Rich Morin wrote:
I've been studiously avoiding doin
rtion/expectation level, rather than at the interpreter
level, should that tag be changed to "fails"?
Mike
On Fri, Jul 10, 2009 at 2:59 AM, Eloy Duran
wrote:
Yes indeed, the ones that segfault should be tagged as critical.
To list all current critical tags:
$ ./mspec/bin/mspec tag --l
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
Hi,
I'm un-jet lagging a bit, so I thought I'd update the ruby specs
again. We are now passing: 18160 examples.
@Matt: Great work on the StringScanner! Could you please make sure the
specs run on 1.8 as well? Currently 4 fail:
$ mspec -B ruby.1.8.mspec library/stringscanner
StringScanner
n 2 aug 2009, at 19:49, Matt Aimonetti wrote:
Hi Eloy,
Welcome back. Unfortunatelly, due to API changes, the specs can't
all pass on 1.8 and 1.9 unless we use a version check mechanism.
My understanding was that we should focus on 1.9.2 preview 1.
What do you want me to do?
- Matt
Sent from
11:30 AM, Matt Aimonetti > wrote:
Thanks for the tip, I'll go back and fix strscan and will make the
modifications before pushing stringio.
- Matt
On Sun, Aug 2, 2009 at 11:22 AM, Eloy Duran
wrote:
Thanks Matt :)
Indeed, in order to specify the API changes between 1.8 and 1.9 you
Awesome work Patrick! Thanks a lot for your work on this.
Eloy
On 3 aug 2009, at 19:51, Patrick Thomson wrote:
Hi everyone,
I've just pushed my work on a new YAML module to the experimental
branch (revision 2184). Rather than being backed by the old syck
code that 1.8/1.9 use, this is bac
Btw: About git-svn creating many commits, I wouldn't worry about it :)
But if you'd like to normalize, I'd do something like:
$ git checkout -b yaml_branch
# work on it
$ git checkout master
$ git diff yaml_branch | patch -p1
$ git add .
$ git commit -v
Eloy
On 3 aug 2009, at 19:51, Patric
t annoyed me so
much I went back to svn)
Eloy, would you mind giving a quick rundown of your setup and
workflow?
Thanks,
- Matt
On Mon, Aug 3, 2009 at 1:01 PM, Eloy Duran
wrote:
Btw: About git-svn creating many commits, I wouldn't worry about
it :) But if you'd like to normali
Nice! :)
On 3 aug 2009, at 22:23, Brian Mitchell wrote:
You could also use:
$ git merge --squash yaml_branch
A little easier than piping a diff.
Brian.
On Mon, Aug 3, 2009 at 16:01, Eloy Duran
wrote:
Btw: About git-svn creating many commits, I wouldn't worry about
it :) But
if
Applied and removed tag, thanks!
Eloy
On Aug 4, 2009, at 4:15 AM, dan sinclair wrote:
The attached patch gets the NSNumber boolean conversion spec
working. I'm not sure if the change is correct but I changed the
spec from should != to should_not == and it appears to be working
correctly
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
Hi,
On Aug 5, 2009, at 5:31 PM, Clay Bridges wrote:
The google didn't yield much guidance on this. Before I started a
deep-dive on the MacRuby source, and/or the standard ruby way to
handle this sort of thing, I thought I would ask a couple of
questions:
1) Any easy advice?
Yes, use RubyCocoa
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
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 Rub
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
1 - 100 of 259 matches
Mail list logo
