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] wrote:
I
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
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
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,
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
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
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
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
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
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
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,
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
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 eloy.de.en...@gmail.com
wrote:
on pure
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'know
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.setString(foo) or as @text_view.string
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
/SNIP
Giving some tests back to extlib should be no problem.
On Thu, Jan 22, 2009 at 12:06 AM, Eloy Duran
eloy.de.en...@gmail.com wrote:
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
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
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.
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
eloy.de.en...@gmail.com wrote:
Hi,
As most people know installing gems on MacRuby still fails for most
gems.
I
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
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
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
;-)
Cheers,
Eloy
On 6 apr 2009, at 17:39, Chris McGrath wrote:
On Mon, Apr 6, 2009 at 10:16 AM, Eloy Duran
eloy.de.en...@gmail.com 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
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, Eloy
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
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\n
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
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
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
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
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
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 eloy.de.en...@gmail.com
wrote:
What would be great is if you could first complete the openssl part
of
the rubyspec, which desperately needs some love.
Once
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
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
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
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
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
/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
eloy.de.en...@gmail.com wrote:
Yes indeed, the ones that segfault should be tagged as critical.
To list all current critical tags:
$ ./mspec/bin/mspec tag
. 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 my iPhone
On Aug 2, 2009, at 6:42, Eloy Duran eloy.de.en...@gmail.com
AM, Matt Aimonetti mattaimone...@gmail.com
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
eloy.de.en...@gmail.com wrote:
Thanks Matt :)
Indeed, in order to specify the API
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
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,
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 eloy.de.en...@gmail.com
wrote:
Btw: About git-svn creating many commits, I wouldn't worry about
it :) But if you'd like to normalize, I'd
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
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
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
Hey Patrick,
How about the getting the ffi zlib implementation to work? Seems to me
that it would kill two birds with one stone, i.e. getting FFI in a
more usable state and a C backed zlib implementation.
Eloy
On 18 aug 2009, at 23:52, Patrick Thomson wrote:
Hi everyone,
I'm working on
Here's a smaller/simpler example of creating a gist, although it uses
RubyCocoa (it's written for LimeChat), it would be easy to port that
MacRuby: http://github.com/alloy/CocoaGist/tree/master
Cheers,
Eloy
On 20 aug 2009, at 08:57, Matt Aimonetti wrote:
Haha, let's add that to the todo
, Eloy Duran wrote:
Hey Patrick,
How about the getting the ffi zlib implementation to work? Seems to
me that it would kill two birds with one stone, i.e. getting FFI in
a more usable state and a C backed zlib implementation.
Eloy
On 18 aug 2009, at 23:52, Patrick Thomson wrote:
Hi everyone
Great news, thanks William! Now if we could only have push support… Oh
well, another day.
wink So when can we expect CVS push access? Or even better, tarrball-
email-push-support? /wink
Cheers,
Eloy
On 21 aug 2009, at 02:55, Laurent Sansonetti wrote:
Hi,
We now have git mirrors of our
with git-
format-patch could be e-mailed to subversion repo maintainers and
applied with git-apply. Just saying...
- Josh
On Aug 21, 2009, at 12:14 AM, Eloy Duran wrote:
Great news, thanks William! Now if we could only have push support…
Oh well, another day.
wink So when can we expect CVS
Hi,
I just installed Snow Leopard, I still have the LLVM that I had
compiled on Slow Leopard (10.5), then:
$ rake clean
$ rake
$ rake spec
All worked for me. So this is after the last fix committed by Laurent.
Cheers,
Eloy
On 29 aug 2009, at 16:46, Robert Schaaf wrote:
Hello Laurent,
Added in r2452, thanks!
Btw: I prefer a git format-patch diff :)
Eloy
On 1 sep 2009, at 20:58, Alexey Borzenkov wrote:
On Tue, Sep 1, 2009 at 1:12 AM, Laurent Sansonettilsansone...@apple.com
wrote:
Hi Alexey,
Looks like you found a bug in super :) Would you be willing to
contribute a
Hey Conrad,
The readme that should get you started with the specs is available in
spec/README.rdoc (http://github.com/masterkain/macruby/blob/master/spec/README.rdoc
).
I'm sure there will be some issues you run into as I haven't updated
it in a while. Feel free to update it and/or ask me
Hey Ben,
Awesome stuff lads.
Perhaps this could be added to your .irbrc files to have it always
present until backtraces are available?
That wouldn't do any good though, as __FILE__ and __LINE always point
to the file and line of the binding that it's evaluated from. So
putting it in
On Sep 21, 2009, at 7:58 PM, William Siegrist wrote:
On Sep 21, 2009, at 1:28 AM, MacRuby wrote:
#309: String, Hash, Array: singleton attr_accessor cannot be defined
+---
Reporter: d...@… | Owner:
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
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.en
me too much time to write them…
- Dylan
On Fri, Oct 2, 2009 at 3:31 AM, Eloy Duran eloy.de.en...@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
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
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
step to his nightly building app.
- Matt
On Fri, Oct 2, 2009 at 12:11 PM, Eloy Duran
eloy.de.en...@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
Laurent,
as they say in french; congratulations on le grande effort! \m/
Eloy
On Thursday, October 8, 2009, Laurent Sansonetti lsansone...@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
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
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. prabh...@apple.com
wrote:
I wonder if this will help MacRuby applications:
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
Laurent,
as they say in french; congratulations on le grande effort! \m/
Eloy
On Thursday, October 8, 2009, Laurent Sansonetti lsansone...@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
I think the best solution would be if RubyGems would apply the same
program prefix or suffix to the executables it installs. So in the
case of MacRuby, the executable would be: /usr/bin/macspec.
I haven't had the time to look at RubyGems yet though, if anyone wants
to take a stab at fixing
Hey Conrad,
Hi Eloy, I have spent a bit of time with it. Here's what I did to
get things going:
1) sudo gem install rvm
2) add the following to your .profile after the last 'export PATH='
setting:
if [ -s ~/.rvm/scripts/rvm ] ; then source ~/.rvm/scripts/
rvm ; fi
Hi,
See my replies inline.
Frustrated, not upset. I never trust a system where the CI has been red for
this long.
Here are the results I get, and they are fairly consistent. I don't know how
you got the output you are showing, I am running rake spec:ci as described
in the readme.
a single patch. But I will continue to try.
Cheers,
-Gp
On 2009-12-08, at 7:55 AM, Eloy Duran wrote:
Hi,
See my replies inline.
Frustrated, not upset. I never trust a system where the CI has
been red for this long.
Here are the results I get, and they are fairly consistent. I
don't
Yup, Rails doesn't work yet. However, that specific bug with
ActiveSupport and others are fixed in the current trunk.
Eloy
On 11 dec 2009, at 23:23, Mike Moore wrote:
AFAIK, Rails (including ActiveRecord) is not known to work in
MacRuby yet.
On Fri, Dec 11, 2009 at 3:14 PM, Mark
Hi,
Work on a FFI interface for Nokogiri has already been started by the
author, you can find it here: http://github.com/tenderlove/nokogiri/tree/macruby
I have no idea on how good or not it works, though.
Eloy
On 27 dec 2009, at 09:34, Conrad Taylor wrote:
Jarred, after further analysis
Hey Michael,
You might also want to consider NSView's
enterFullScreenMode:withOptions: [1]
It's available from 10.5 and higher only, but with MacRuby that should
not be a problem.
Cheers,
Eloy
[1]
Aimonetti wrote:
+1 for enterFullScreenMode:withOptions: MacRuby won't run on
anything 10.5 anyway.
- Matt
On Wed, Jul 7, 2010 at 10:44 AM, Eloy Duran
eloy.de.en...@gmail.com wrote:
Hey Michael,
You might also want to consider NSView's
enterFullScreenMode:withOptions: [1]
It's
The problem with a folder reference is that it does sync the class info with
IB. I have CLI generators, rails like, which add the rb files to the xcodeproj.
The xcodeproj is just a plist after all :)
If interested, I can try to do a first release of my lib with just the
generator part. Because
You can safely ignore these warnings, they're left-overs in the QuickLook
framework. Afaik Laurent already filed a radar ticket for this.
I can't help you with your printing problem, but filing a ticket with a
reproducible reduction never hurts :)
Eloy
Sent from my iPad
On 12 aug. 2010, at
There has been some improvement around exceptions. For instance, no backtrace
would printed to the console for Ruby exceptions. But there are probably still
cases where the exceptions aren't as helpful as you'd like.
Eloy
Sent from my iPad
On 12 aug. 2010, at 17:31, Robert Rice
I verified that it does work:
sudo macgem install awesome_print
Password:
unknown: warning: ignoring alias
Successfully installed awesome_print-0.2.1
1 gem installed
% cat ~/.irbrc
require 'rubygems'
require 'ap'
% macirb
irb(main):001:0 data = [ false, 42, %w(forty two), { :now = Time.now,
I did see it, but since the gem does actually seem to work with DietRB, I
didn't want to go into that, yet.
Brad, could you please check where/what code is Calling IRB::Irb? I think it’s
another lib, maybe something like Wirble. In which case, please see this
ticket:
it to work in macirb.
It looks like the internals of IRB is completely different.
Has anyone had an luck with this?
Matt
On Oct 6, 2010, at 2:10 AM, Eloy Duran wrote:
I verified that it does work:
sudo macgem install awesome_print
Password:
unknown: warning: ignoring alias
calling conventions and OSX module stuff, portability is
kind of a pain. I use the Kernel.respond_to?(:framework) construct often,
but I welcome better suggestions.
Matt
On Oct 6, 2010, at 9:02 AM, Eloy Duran wrote:
I did, in the email that you replied on. Could you please send some more
Yes, see this email from wednesday:
http://lists.macosforge.org/pipermail/macruby-devel/2010-October/006146.html
HTH,
Eloy
On Sat, Oct 9, 2010 at 4:51 PM, Brad Hutchins oshyb...@gmail.com wrote:
Any head way on macirb issue that I understand some others have also
experienced as well with
Hi,
I haven’t heard back from Matt (from the original thread) or you and
am still wondering if this solved it in a satisfactory way?
Cheers,
Eloy
On Sat, Oct 9, 2010 at 6:13 PM, Eloy Duran eloy.de.en...@gmail.com wrote:
Yes, see this email from wednesday:
http://lists.macosforge.org/pipermail
To be clear, by version I meant: are you using 0.7 release or did you compile
it yourself from a different revision?
On Oct 14, 2010, at 3:33 PM, Eloy Duran wrote:
Hi,
It seems to work for me:
% macruby -e 'p MACRUBY_VERSION, MACRUBY_REVISION'
0.7
svn revision 4566 from
http
Thanks for the reduction. Could you create a ticket and assign to me?
Eloy
On Oct 14, 2010, at 4:11 PM, Louis-Philippe wrote:
It seems to work for me:
% macruby -e 'p MACRUBY_VERSION, MACRUBY_REVISION'
0.7
svn revision 4566 from
These work for me too on trunk, but I am seeing some GC issues. I’ve
updated the ticket with examples.
On Fri, Oct 15, 2010 at 12:23 AM, Laurent Sansonetti
lsansone...@apple.com wrote:
Hi Perry,
If you install the nightly build, you can still go back to 0.7 by
re-installing 0.7 on top of it
Since an Array is a NSArray: http://bit.ly/de3kxd, maybe something
like the following?
$ macirb
irb(main):001:0 a = ['apple', 'tuna', 'orange']
= [apple, tuna, orange]
irb(main):002:0 indices = NSIndexSet.indexSetWithIndex(1)
= #NSIndexSet:0x20023fe80
irb(main):003:0 fish =
Oops, forgot to paste the result:
% macirb
irb(main):001:0 framework
'/Users/eloy/Documents/DEVELOPMENT/MacRuby/ObjCHiredis/ObjCHiredis/build/Debug/ObjCHiredis.framework'
= true
irb(main):002:0 redis = ObjCHiredis.alloc.init
= #ObjCHiredis:0x200226600
irb(main):003:0 redis.connect(127.0.0.1,
)
so I guess that is a bug, isn't it?
2010/11/4 Eloy Duran eloy.de.en...@gmail.com
Oops, forgot to paste the result:
% macirb
irb(main):001:0 framework
'/Users/eloy/Documents/DEVELOPMENT/MacRuby/ObjCHiredis/ObjCHiredis/build/Debug/ObjCHiredis.framework'
= true
irb(main):002:0 redis
)
ArgumentError: wrong number of arguments (2 for 0)
so I guess that is a bug, isn't it?
2010/11/4 Eloy Duran eloy.de.en...@gmail.com
Oops, forgot to paste the result:
% macirb
irb(main):001:0 framework
'/Users/eloy/Documents/DEVELOPMENT/MacRuby/ObjCHiredis/ObjCHiredis/build/Debug
Hi,
As some of you may know, we have a new implementation of IRB since
MacRuby 0.7. My hope was nobody would notice the changes, but this was
obviously wishful thinking :) So from now on, whenever there are major
changes, I’ll write an update about them. I’d be very grateful if
people can try
Normally this is not a bug. Most people lazy initialize instance variables, but
you will get warned if you ask it to be more verbose. However, I have been
unable to trigger it on MacRuby myself:
% ruby19 -w -e '!...@foo'
-e:1: warning: instance variable @foo not initialized
% macruby -w -e
You can check which macruby version you have, like so:
% macruby -v
MacRuby 0.8 (ruby 1.9.2) [universal-darwin10.0, x86_64]
Also:
* which OS versions do you have?
* did you install the BridgeSupport preview pkg?
Eloy
On 15 nov 2010, at 13:51, András Zalavári wrote:
(I'm not sure if the
I don't have an example of a class that uses conformsToProtocol: on the
delegate, so I can't give you a code example, but I would try to override the
conformsToProtocol: class and instance methods and return true for those you
support.
On 15 nov 2010, at 00:15, Martijn Walraven wrote:
Hi,
protocol ==
Protocol.protocolWithName('...') leads to the same result.
Any ideas as to how this could be made to work?
On Nov 16, 2010, at 19:59 , Eloy Duran wrote:
I don't have an example of a class that uses conformsToProtocol: on the
delegate, so I can't give you a code example, but I
1 - 100 of 185 matches
Mail list logo
