[MacRuby-devel] Installing MacRuby on SL?

[Conrad Taylor]

Hi, I'm attempting to build MacRuby on SL but I'm getting the following
message:
The `llvm-config` executable was not located in your PATH.

Could someone tell me the best course action to resolve the above issue?

-Conrad
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] [MacRuby][0.5] Which version of rake version to use?

[Conrad Taylor]

Hi, I was wondering, which version of rake should one use to build and run
the specs/benchmarks with?  I ask this questions because my default points
to
/opt/local/bin/rake

which is the version
that's parts of my MacPorts install of Ruby 1.9.1p129.  Also, I
noticed that there's a version
called macrake which generates the following error on execution:

Segementation fault

-Conrad
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] [MacRuby][0.5] Bison Error

[Conrad Taylor]

The following error prevents the build from moving forward:
BEGIN ERROR:

bison -t -v -oy.tab.c ripper.y
ripper.y:2960.25-26: $$ for the midrule at $6 of `primary' has no declared
type
make: *** [ripper.c] Error 1

END ERROR:

-Conrad
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby][0.5] Which version of rake version to use?

[Conrad Taylor]

The ruby 1.9.1 rake does work without any issues but I wasn't 100% sure
because there's also a version of rake in
/macruby-experimental/bin

-Conrad

On Sun, Jul 5, 2009 at 4:54 PM, Laurent Sansonetti wrote:

> Hi,
>
> Our Rakefile-based system has only been tested with /usr/bin/rake, the
> version that ships with Mac OS X and that uses Ruby 1.8.
>
> I did not try with 1.9's rake (though it may perhaps work), and I am sure
> that it won't work with macruby's macrake (this explains your SEGV) for the
> moment.
>
> HTH
> Laurent
>
>
> On Jul 5, 2009, at 4:40 PM, Conrad Taylor wrote:
>
>  Hi, I was wondering, which version of rake should one use to build and run
>> the specs/benchmarks with?  I ask this questions because my default points
>> to
>>
>> /opt/local/bin/rake
>>
>> which is the version that's parts of my MacPorts install of Ruby
>> 1.9.1p129.  Also, I noticed that there's a version called macrake which
>> generates the following error on execution:
>>
>> Segementation fault
>>
>> -Conrad
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby][0.5] Bison Error

[Conrad Taylor]

I guess when I updated another port bison was a dependency.  Thus, bison
2.4.1 was being used during the build MacRuby 0.5.  After deactivating this
port, everything is building successfully using bison 2.3.0 which is the
system default.

-Conrad

On Sun, Jul 5, 2009 at 8:19 PM, Laurent Sansonetti wrote:

> What's the version of your bison?
>
> I am guessing you have a version of bison that is incompatible in your
> $PATH.
>
> MacRuby should build fine with the system one.
>
> Laurent
>
>
> On Jul 5, 2009, at 4:56 PM, Conrad Taylor wrote:
>
>  The following error prevents the build from moving forward:
>>
>> BEGIN ERROR:
>>
>> bison -t -v -oy.tab.c ripper.y
>> ripper.y:2960.25-26: $$ for the midrule at $6 of `primary' has no declared
>> type
>> make: *** [ripper.c] Error 1
>>
>> END ERROR:
>>
>> -Conrad
>>
>>
>>
>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] compiling macruby

[Conrad Taylor]

On Wed, Jul 22, 2009 at 4:19 AM, Daniel  wrote:

> Hi,
>
> I've been compiling macruby from source, svn with tag 0.4
>
> One observation I made is that if there's a different bison in my path,
> such as the one from macports in /opt/local/bin/bison, then macruby will not
> compile.
>
> In Rakefile, bison is hardcoded to /usr/bin/bison
>
> In the generated ext/ripper/Makefile however, bison is simply the bison
> from the environment.
>
> It seems the real fix should be that the generated Makefile should also be
> hardcoded to use /usr/bin/bison, as opposed to me changing my path.
>
> -d
>

Daniel, this has been resolved in macruby experimental branch.

-Conrad
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] RubySpec updated

[Conrad Taylor]

Hi, I'm getting the following after pulling the latest sources:

BEGIN Transcript:

darnoc-laptop:macruby-experimental conradwt$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.6
BuildVersion: 10A421a
darnoc-laptop:macruby-experimental conradwt$ rake spec:ci
(in /Users/conradwt/macruby.dir/projects/macruby-experimental)
./mspec/bin/mspec ci -I./lib -B ./spec/macruby.mspec  :full
MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
.[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/method.m'
.[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/constant.m'
.[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/exception.m'
..[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/object.m'
.unknown:
[BUG] Segmentation fault
MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]

rake aborted!
Command failed with status (): [./mspec/bin/mspec ci -I./lib -B
./spec/mac...]

END Transcript:

On Sun, Aug 2, 2009 at 12:26 PM, Laurent Sansonetti
wrote:

> Welcome back \o/
>
> $ sw_vers
> ProductName:Mac OS X
> ProductVersion: 10.6
> BuildVersion:   10A421a
>
> $ rake spec:ci
> (in /Users/lrz/src/macruby-experimental)
> ./mspec/bin/mspec ci -I./lib -B ./spec/macruby.mspec  :full
> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
>
> ...
>
> Finished in 94.124748 seconds
>
> 1519 files, 6142 examples, 18161 expectations, 0 failures, 0 errors
>
> Laurent
>
>
> On Aug 2, 2009, at 6:42 AM, Eloy Duran wrote:
>
>  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#getch is multi-byte character sensitive FA

Re: [MacRuby-devel] RubySpec updated

[Conrad Taylor]

On Sun, Aug 2, 2009 at 2:13 PM, Laurent Sansonetti wrote:

> That's weird, did you do rake and rake install before starting the specs? I
> think it must be done otherwise the C extension bundles won't be properly
> loaded. (We should pass the appropriate flags to mspec so that it loads C
> extension bundles from the local build directory.)
>

Laurent, I invoked the following commands at the command line in the order
given earlier:

svn update
rake
sudo rake install

Now, after doing the following commands at the command line in the order
given:

svn update  -->  At revision 2153.
rake clean
rake
sudo rake install

I'm getting the following result:

Finished in 104.085941 seconds

1519 files, 6142 examples, 18162 expectations, 0 failures, 0 errors

-Conrad


>
> If it's still crashing, could you do the following inside the macruby
> directory:
>
> $ DYLD_LIBRARY_PATH=. gdb --args ./macruby -I./lib mspec/bin/mspec-ci -B
> ./spec/macruby.mspec :full
>
> Inside gdb, do "r", and once it crashes, do "thread apply all bt" and
> copy/paste the output.
>
> Laurent
>
>
> On Aug 2, 2009, at 12:54 PM, Conrad Taylor wrote:
>
>  Hi, I'm getting the following after pulling the latest sources:
>>
>> BEGIN Transcript:
>>
>> darnoc-laptop:macruby-experimental conradwt$ sw_vers
>> ProductName:Mac OS X
>> ProductVersion: 10.6
>> BuildVersion:   10A421a
>> darnoc-laptop:macruby-experimental conradwt$ rake spec:ci
>> (in /Users/conradwt/macruby.dir/projects/macruby-experimental)
>> ./mspec/bin/mspec ci -I./lib -B ./spec/macruby.mspec  :full
>> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
>> .[!] Compiling fixture
>> `/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/method.m'
>> .[!] Compiling fixture
>> `/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/constant.m'
>> .[!] Compiling fixture
>> `/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/exception.m'
>> ..[!] Compiling fixture
>> `/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/object.m'
>> .unknown:
>> [BUG] Segmentation fault
>> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
>>
>> rake aborted!
>> Command failed with status (): [./mspec/bin/mspec ci -I./lib -B
>> ./spec/mac...]
>>
>> END Transcript:
>>
>> On Sun, Aug 2, 2009 at 12:26 PM, Laurent Sansonetti <
>> lsansone...@apple.

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

[Conrad Taylor]

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 compatible with syck, was added. It is still under
> development, but it's currently good enough for most uses, including
> HotCocoa rakefile tasks.
>
> 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 :)
>
> 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 :)
>
> Changes:
>
> - fixed an incompatibility that showed up in switching between libedit and
> GNU readline
>
> - added support to delete environment variables using ENV[]=nil
>
> - fixed the clean task to remove binary build producfs too.
>
> - fixed GC problems in oniguruma: make sure st.c tables are
> retained/released appropriately since they use GC memory
>
> - fixed a problem in IO#gets where the stream wasn't marked as EOF after
> reading the last separator-terminated line
>
> - implemented Thread.start/fork
>
> - added support for creation of Binding local variables
>
> - fixed a bug in the way we compile return-from-block handlers
>
> - fixed a bug in IO#reopen
>
> - #fork is now raising a "not yet supported" exception, because it doesn't
> work well with CF and libauto. We will try to support it, but later.
>
> - fixed String#inspect to escape some characters
>
> - ported Rational and Complex to the new runtime APIs
>
> - various unicode/bytestring fixes
>
> - fixed AOT compilation of keep locals.
>
> - fixed bytestring -> path conversion
>
> - keep IO streams that should never be closed into a static array to avoid
> them being collected
>
> - fixed a bug in the fast aref primitive: convert fixnum argument to long
> and not int
>
> - fix a bug in the dispatcher where calling a method with an empty splat
> array wasn't dispatching a zero arity method
>
> - optimize numeric coerce dispatch calls
>
> - overwrite -[NSObject description] in every new subclass that calls #to_s
> + optimized other overloaded methods
>
> - changed the way %s is implemented to behave like the ruby spec and send
> #to_s
>
> - updated the stringscanner specs to be 1.9.2 compatible
>
> - updated the stringio specs to be 1.9.2 compatible
>
> - RubySpec was updated from upstream
>
> - implemented conditional assignment of class variables
>
> - work around a crash while raising an objc exception from a ruby one
>
> - ported the compiler to 32-bit (including the floating point optimization)
>
> - removed the negative-index feature of Readline::HISTORY (of libedit) to
> behave like readline
>
> - optimized Math.sqrt
>
> - fixed super within a method that has a splat argument
>
> - added Integer#ord
>
> - a YAML module has been written, based on the libyaml C library. It is
> still under development but load and dump should work. See the previous
> e-mail on the mailing-list for more information.
>
> - a pure Ruby stringio module is under development
>
> Laurent


I'm seeing the following warning messages after "sudo rake install":

unknown: warning: File::new() does not take block; use File::open() instead

Also, running "rake spec:ci" generates the following message:

Begin Message:

$ rake spec:ci
(in /Users/conradwt/macruby.dir/projects/macruby-experimental)
./mspec/bin/mspec ci -I./lib -B ./spec/macruby.mspec  :full
MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
.[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/method.m'
.[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/constant.m'
.[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/exception.m'
..[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/object.m'
.internal
error while reading stream: The operation couldn’t be completed. Bad file
desc

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

[Conrad Taylor]

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
>>
>
> Sorry about that, I just fixed that in r2219.
>
>  Also, running "rake spec:ci" generates the following message:
>>
>> Begin Message:
>>
>> $ rake spec:ci
>> (in /Users/conradwt/macruby.dir/projects/macruby-experimental)
>> ./mspec/bin/mspec ci -I./lib -B ./spec/macruby.mspec  :full
>> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
>> .[!] Compiling fixture
>> `/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/method.m'
>> .[!] Compiling fixture
>> `/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/constant.m'
>> .[!] Compiling fixture
>> `/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/exception.m'
>> ..[!] Compiling fixture
>> `/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/object.m'
>> .internal
>>  error
>> while reading stream: The operation couldn’t be completed. Bad file
>> descriptorises an ArgumentError if not given an argument
>> fails:Integer#lcm raises an ArgumentError if given more than one argument
>> fails:Integer#lcm raises an ArgumentErro??%?` (RuntimeError)
>> rake aborted!
>> Command failed with status (1): [./mspec/bin/mspec ci -I./lib -B
>> ./spec/mac...]
>>
>> (See full trace by running task with --trace)
>>
>
> That shouldn't happen... in my environment (Snow Leopard) I don't get any
> failure, but Vincent told me today that he gets failures sometimes on his
> Leopard machine.


I'm using the following:

$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.6
BuildVersion: 10A421a


>
>
> I will try to find a Leopard box here and stress the specs to reproduce
> these.
>
> Laurent
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

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

[Conrad Taylor]

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":
>>>
>>> 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" generates the following message:
>>>
>>> Begin Message:
>>>
>>> $ rake spec:ci
>>> (in /Users/conradwt/macruby.dir/projects/macruby-experimental)
>>> ./mspec/bin/mspec ci -I./lib -B ./spec/macruby.mspec  :full
>>> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
>>> .[!] Compiling fixture
>>> `/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/method.m'
>>> .[!] Compiling fixture
>>> `/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/constant.m'
>>> .[!] Compiling fixture
>>> `/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/exception.m'
>>> ..[!] Compiling fixture
>>> `/Users/conradwt/macruby.dir/projects/macruby-experimental/spec/macruby/fixtures/object.m'
>>> .internal
>>>  error
>>> while reading stream: The operation couldn’t be completed. Bad file
>>> descriptorises an ArgumentError if not given an argument
>>> fails:Integer#lcm raises an ArgumentError if given more than one argument
>>> fails:Integer#lcm raises an ArgumentErro??%?` (RuntimeError)
>>> rake aborted!
>>> Command failed with status (1): [./mspec/bin/mspec ci -I./lib -B
>>> ./spec/mac...]
>>>
>>> (See full trace by running task with --trace)
>>>
>>
>> That shouldn't happen... in my environment (Snow Leopard) I don't get any
>> failure, but Vincent told me today that he gets failures sometimes on his
>> Leopard machine.
>
>
> I'm using the following:
>
> $ sw_vers
> ProductName: Mac OS X
> ProductVersion: 10.6
> BuildVersion: 10A421a
>
>
>>
>>
>> I will try to find a Leopard box here and stress the specs to reproduce
>> these.
>>
>> Laurent
>>
>
OK, using r2219, I was able to achieve the following without error:

svn update
rake
sudo rake install
rake spec:ci

Begin Result:

Finished in 93.141017 seconds

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

End Result:


>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

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

[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
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] Git or Subversion?

[Conrad Taylor]

Hi,  I was wondering, are we using Git or Subversion these days?  If we're
switching to Git, how does one migrate to it from an existing SVN
repository.
Thanks,

-Conrad
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Git or Subversion?

[Conrad Taylor]

Matt, I asked the question because I noticed that there hasn't been any
updates to the SVN repository.  At this time, I'm at revision 2272.  Is this
correct?

-Conrad

On Mon, Aug 10, 2009 at 6:19 PM, Matt Aimonetti wrote:

> The official repository is on SVN but a few of us use git-svn to work on
> our branches and commit back to SVN.
>
> If you are planning on contributing patches, whatever SCM you want to use
> is fine as long as your patches apply fine on the svn repo.
>
> If you wish to switch to git-svn, see the discussion we recently had about
> the best process. (It's a thread started by Patrick letting people know
> about the work he did on the YAML rewrite and I went OT asking Eloy and
> others about git-svn.)
>
> Good luck,
>
> - Matt
>
>
>
> On Mon, Aug 10, 2009 at 6:10 PM, Conrad Taylor  wrote:
>
>> Hi,  I was wondering, are we using Git or Subversion these days?  If we're
>> switching to Git, how does one migrate to it from an existing SVN
>> repository.
>> Thanks,
>>
>> -Conrad
>>
>>
>>
>>
>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Git or Subversion?

[Conrad Taylor]

Laurent, thanks because I was thinking that the SVN went away.

-Conrad

On Mon, Aug 10, 2009 at 6:40 PM, Laurent Sansonetti
wrote:

> The last SVN update is indeed r2272, committed 2009-08-10 10:10:24 -0700
> today. The SVN repository is up to date and is the master copy of the
> project.
>
> Several people (including me) work a lot offline and commit after, to not
> break the main branch. Some of them use git-svn :-)
>
> HTH,
> Laurent
>
>
> On Aug 10, 2009, at 6:29 PM, Conrad Taylor wrote:
>
>  Matt, I asked the question because I noticed that there hasn't been any
>> updates to the SVN repository.  At this time, I'm at revision 2272.  Is this
>> correct?
>>
>> -Conrad
>>
>> On Mon, Aug 10, 2009 at 6:19 PM, Matt Aimonetti 
>> wrote:
>> The official repository is on SVN but a few of us use git-svn to work on
>> our branches and commit back to SVN.
>>
>> If you are planning on contributing patches, whatever SCM you want to use
>> is fine as long as your patches apply fine on the svn repo.
>>
>> If you wish to switch to git-svn, see the discussion we recently had about
>> the best process. (It's a thread started by Patrick letting people know
>> about the work he did on the YAML rewrite and I went OT asking Eloy and
>> others about git-svn.)
>>
>> Good luck,
>>
>> - Matt
>>
>>
>>
>> On Mon, Aug 10, 2009 at 6:10 PM, Conrad Taylor 
>> wrote:
>> Hi,  I was wondering, are we using Git or Subversion these days?  If we're
>> switching to Git, how does one migrate to it from an existing SVN
>> repository.
>>
>> Thanks,
>>
>> -Conrad
>>
>>
>>
>>
>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] MacRuby Document-based Application template in XCode?

[Conrad Taylor]

Laurent, I have r2286 but I'm not seeing the template within "New Project".
 It seems that I have gone from r2272 to r2286 with no visible updates
and/or additions.
-Conrad

On Tue, Aug 11, 2009 at 12:08 PM, Laurent Sansonetti
wrote:

> Awesome James!
>
> I just committed it to trunk, in r2282.
>
> Thanks a lot!
>
> Laurent
>
>
> On Aug 11, 2009, at 11:55 AM, James Granby wrote:
>
>  Hi,
>>
>> I have made a template for NSDocument-based MacRuby applications and would
>> be very happy for it to be included in the next release, if it would be
>> helpful. The template can be found here:
>>
>> http://jgranby.net/articles/2009/macruby-nsdocument-template.html
>>
>> Kind regards,
>>
>> James Granby
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] MacRuby Document-based Application template in XCode?

[Conrad Taylor]

Laurent, that was the issue.
Thanks,

-Conrad

On Tue, Aug 11, 2009 at 3:17 PM, Laurent Sansonetti
wrote:

> One more question.. are you sure you are on trunk and not on the
> experimental branch anymore?
>
> Laurent
>
>
> On Aug 11, 2009, at 3:16 PM, Laurent Sansonetti wrote:
>
>  Did you run `sudo rake install'? I just installed trunk on another machine
>> and was able to find the template in Xcode (under the "User Templates"
>> section).
>>
>> Otherwise, what's your environment and version of Xcode?
>>
>> Thanks,
>> Laurent
>>
>> On Aug 11, 2009, at 2:30 PM, Conrad Taylor wrote:
>>
>>  Laurent, I have r2286 but I'm not seeing the template within "New
>>> Project".  It seems that I have gone from r2272 to r2286 with no visible
>>> updates and/or additions.
>>>
>>> -Conrad
>>>
>>> On Tue, Aug 11, 2009 at 12:08 PM, Laurent Sansonetti <
>>> lsansone...@apple.com> wrote:
>>> Awesome James!
>>>
>>> I just committed it to trunk, in r2282.
>>>
>>> Thanks a lot!
>>>
>>> Laurent
>>>
>>>
>>> On Aug 11, 2009, at 11:55 AM, James Granby wrote:
>>>
>>> Hi,
>>>
>>> I have made a template for NSDocument-based MacRuby applications and
>>> would be very happy for it to be included in the next release, if it would
>>> be helpful. The template can be found here:
>>>
>>> http://jgranby.net/articles/2009/macruby-nsdocument-template.html
>>>
>>> Kind regards,
>>>
>>> James Granby
>>> ___
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>> ___
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>> ___
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>
>>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] What's the current state of macgem?

[Conrad Taylor]

Hi, I was wondering, could someone provide information on the state of
macgem?  At this time, I'm looking to get some top gems working in macgem if
it is at all possible at this time or help fix macgem so that I can do it.
Thanks,

-Conrad
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] malloc: resurrection error

[Conrad Taylor]

On Tue, Aug 18, 2009 at 2:43 AM, Conrad Taylor  wrote:

> Hi, I'm seeing the following issue with r2344:
>
> Begin Message:
>
> $ rake spec:ci
> (in /Users/conradwt/macruby.dir/projects/macruby-trunk)
> ./mspec/bin/mspec ci -B ./spec/macruby.mspec  :full
> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
> .macruby(6809,0x7fff70ccbbe0)
> malloc: resurrection error for object 0x2010d1920 while assigning
> {conservative-block}[32](0x20101e260)[0] = Bignum[64](0x2010d1920)
> garbage pointer stored into reachable memory, break on
> auto_zone_resurrection_error to debug
> macruby(6809,0x109c81000) malloc: garbage block 0x2010d1920(Bignum[64]) was
> over-retained during finalization, refcount = 1
> This could be an unbalanced CFRetain(), or CFRetain() balanced with
> -release.
> Break on auto_zone_resurrection_error() to debug.
> macruby(6809,0x109c81000) malloc: fatal resurrection error for garbage
> block 0x2010d1920(Bignum[64]): over-retained during finalization, refcount =
> 1rake aborted!
> Command failed with status (132): [./mspec/bin/mspec ci -B
> ./spec/macruby.msp...]
>
> End Message:
>

Also, here are some additional details:

$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.6
BuildVersion: 10A432

-Conrad
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] malloc: resurrection error

[Conrad Taylor]

Hi, I'm seeing the following issue with r2344:

Begin Message:

$ rake spec:ci
(in /Users/conradwt/macruby.dir/projects/macruby-trunk)
./mspec/bin/mspec ci -B ./spec/macruby.mspec  :full
MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
.macruby(6809,0x7fff70ccbbe0)
malloc: resurrection error for object 0x2010d1920 while assigning
{conservative-block}[32](0x20101e260)[0] = Bignum[64](0x2010d1920)
garbage pointer stored into reachable memory, break on
auto_zone_resurrection_error to debug
macruby(6809,0x109c81000) malloc: garbage block 0x2010d1920(Bignum[64]) was
over-retained during finalization, refcount = 1
This could be an unbalanced CFRetain(), or CFRetain() balanced with
-release.
Break on auto_zone_resurrection_error() to debug.
macruby(6809,0x109c81000) malloc: fatal resurrection error for garbage block
0x2010d1920(Bignum[64]): over-retained during finalization, refcount = 1rake
aborted!
Command failed with status (132): [./mspec/bin/mspec ci -B
./spec/macruby.msp...]

End Message:

On Mon, Aug 17, 2009 at 5:50 PM, Matt Aimonetti wrote:

> We are almost there, Etc, Zlib and Socket are still missing.
> Last I heard, Laurent had a "plan" for Zlib, knowing him, it's probably a
> great and efficient idea.
> Make sure to check with him before starting on that. (running some
> benchmarks on zliby wouldn't hurt anyone)
>
> Once function_method will be working again, many more stdlibs should also
> be in a better shape (Math, CMath etc..)
>
> There is a lot of work being done, unfortunately not much we can see yet.
>
> - Matt
>
>
>
> On Mon, Aug 17, 2009 at 5:41 PM, Josh Ballanco 
> wrote:
>
>> Hey Conrad,
>>
>> I was just looking at this last week. Some recent work on marshalling
>> landed on trunk recently (thanks Laurent!), which is one of the pieces
>> needed. The other major missing piece is zlib. I was looking at what would
>> be needed to port this to MacRuby. However, there is also Zliby (
>> http://zliby.rubyforge.org/), a Pure-Ruby zlib that was written for
>> IronRuby. Not sure what the preference regarding these two options is.
>> Perhaps some benchmarking could settle the debate?
>>
>> - Josh
>>
>>
>>
>> On Aug 17, 2009, at 4:58 PM, Conrad Taylor wrote:
>>
>>  Hi, I was wondering, could someone provide information on the state of
>>> macgem?  At this time, I'm looking to get some top gems working in macgem if
>>> it is at all possible at this time or help fix macgem so that I can do it.
>>>
>>> Thanks,
>>>
>>> -Conrad
>>>
>>>
>>>
>>>
>>> ___
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] 2 NameError with r2359

[Conrad Taylor]

Hi, I'm seeing the following 2 failures with r2359:

Begin Transcript:
$ macrake spec:ci
(in /Users/conradwt/macruby.dir/projects/macruby-trunk)
unknown: warning: already initialized constant MACRUBY_VERSION
./mspec/bin/mspec ci -B ./spec/macruby.mspec  :full
MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
F..

1)
Module#private_class_method raises a NameError when the given name is not a
method FAILED
Expected NameError but no exception was raised
0:in `fail:'
0:in `fail_with:'
0:in `should:'

2)
Module#private_class_method raises a NameError when the given name is an
instance method FAILED
Expected NameError but no exception was raised
0:in `fail:'
0:in `fail_with:'
0:in `should:'

Finished in 103.286393 seconds

1659 files, 6746 examples, 19396 expectations, 2 failures, 0 errors
rake aborted!
Command failed with status (1): [./mspec/bin/mspec ci -B
./spec/macruby.msp...]


End Transcript:

$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.6
BuildVersion: 10A432

-Conrad
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] NameError: uninitialized constant NSObject::AF_INET

[Conrad Taylor]

Hi ALL, I was wondering, is the following the correct state of the
specifications:

begin transcript:

$ rake spec:ci
(in /Users/conradwt/macruby.dir/projects/macruby-trunk)
./mspec/bin/mspec ci -B ./spec/macruby.mspec  :full
MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
.[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-trunk/spec/macruby/fixtures/method.m'
.[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-trunk/spec/macruby/fixtures/constant.m'
.[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-trunk/spec/macruby/fixtures/exception.m'
[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-trunk/spec/macruby/fixtures/object.m'
.E.E...F.

1)
An exception occurred during: before :each
Socket#bind binds to a port ERROR
NameError: uninitialized constant NSObject::AF_INET
0:in `const_missing:'
0:in `protect:'
0:in `each'
0:in `all?'
0:in `protect:'
0:in `each'
0:in `process'
0:in `describe:'

2)
An exception occurred during: before :each
Socket#bind raises an error if we try to bind to an already bound port ERROR
NameError: uninitialized constant NSObject::AF_INET
0:in `const_missing:'
0:in `protect:'
0:in `each'
0:in `all?'
0:in `protect:'
0:in `each'
0:in `process'
0:in `describe:'

3)
An exception occurred during: before :each
Socket#listen verifies we can listen for incoming connections ERROR
NameError: uninitialized constant NSObject::AF_INET
0:in `const_missing:'
0:in `protect:'
0:in `each'
0:in `all?'
0:in `protect:'
0:in `each'
0:in `process'
0:in `describe:'

4)
YAML.load accepts numbers FAILED
Expected "-1" to equal -1
0:in `fail:'
0:in `fail_with:'
0:in `==:'
0:in `protect:'
0:in `each'
0:in `all?'
0:in `protect:'
0:in `each'
0:in `process'
0:in `describe:'

Finished in 178.585049 seconds

1812 files, 7501 examples, 20619 expectations, 1 failure, 3 errors
rake aborted!
Command failed with status (1): [./mspec/bin/mspec ci -B
./spec/macruby.msp...]

end regression:

Lastly, what's the total number of expectations?

Thanks,

-Conrad
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] macruby nightly build 2009-09-10

[Conrad Taylor]

On Thu, Sep 10, 2009 at 11:24 AM, Matt Aimonetti wrote:

> Latest trunk code available as an unofficial pkg ready to install:
> http://rubyurl.com/5K3W
>
> Lots of bug fixes, improved macgem (not finished yet but you can install
> gems and load them using `gem 'gem_name'; require 'whatever'`).
> Things are looking pretty good on trunk :)
>

Hi, should one use 'macgem' instead of 'gem'?  In any case, I wanted to give
it a try by installing sinatra:

sudo macgem install sinatra

and I received the following error message:

ERROR:  While executing gem ... (ArgumentError)
wrong number of arguments (1 for 2)

In a clean installation, the following directory doesn't exist but
attempting to install something creates the directory and the installation
of the gem fails:

/Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0

Now, when I tried to install the gem again, everything worked as expected.
 For example,

$ sudo macgem install sinatra
Password:
Successfully installed rack-1.0.0
Successfully installed sinatra-0.9.4
2 gems installed

-Conrad


>
> - Matt
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] macruby nightly build 2009-09-10

[Conrad Taylor]

Is there a page where can locate what's not working?  Or open projects that
need help?  I would be interested in both erb and the webserver (i.e.
webrick, mongrel, and/or thin)?

Thanks in advance,

-Conrad

On Tue, Sep 15, 2009 at 4:02 PM, Matt Aimonetti wrote:

> You should always use macgem when working with macruby.
> However, Sinatra isn't running yet as erb isn't fully working neither rack
> and we don't have a compatible webserver ;)
>
> You will have to wait a little before that works, but as we are going
> through the std libs, things should start looking better.
>
> - Matt
>
>
>
> On Tue, Sep 15, 2009 at 2:13 PM, Conrad Taylor  wrote:
>
>> On Thu, Sep 10, 2009 at 11:24 AM, Matt Aimonetti > > wrote:
>>
>>> Latest trunk code available as an unofficial pkg ready to install:
>>> http://rubyurl.com/5K3W
>>>
>>> Lots of bug fixes, improved macgem (not finished yet but you can install
>>> gems and load them using `gem 'gem_name'; require 'whatever'`).
>>> Things are looking pretty good on trunk :)
>>>
>>
>> Hi, should one use 'macgem' instead of 'gem'?  In any case, I wanted to
>> give it a try by installing sinatra:
>>
>> sudo macgem install sinatra
>>
>> and I received the following error message:
>>
>> ERROR:  While executing gem ... (ArgumentError)
>> wrong number of arguments (1 for 2)
>>
>> In a clean installation, the following directory doesn't exist but
>> attempting to install something creates the directory and the installation
>> of the gem fails:
>>
>> /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/1.9.0
>>
>> Now, when I tried to install the gem again, everything worked as expected.
>>  For example,
>>
>> $ sudo macgem install sinatra
>> Password:
>> Successfully installed rack-1.0.0
>> Successfully installed sinatra-0.9.4
>> 2 gems installed
>>
>> -Conrad
>>
>>
>>>
>>> - Matt
>>>
>>> ___
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>>
>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] macruby nightly build 2009-09-10

[Conrad Taylor]

Hi Matt, thanks for gettih back to me.  In regards to the failing  
specs, how does one determine what's failing?  I have been running the  
following:


rake spec:ci

In any case, I would like to get started on this as soon as possible.   
Thus, if someone can provide the details, it would be greatly  
appreciated.


Thanks in advance,

-Conrad

Sent from my iPhone

On Sep 15, 2009, at 4:34 PM, Matt Aimonetti   
wrote:


Unfortunately, we don't have a check list of all the std libs and  
other gems that are compatible/incompatible.


The todo list mentions the following:

Planned for 0.5
[ ] fix irb Binding bugs
[/] sockets
[ ] backtracing / symbolication
[/] rubygems should work (modulo C extensions)
  [X] fix version numbers
  [X] fix YAML deserialization of booleans
  [ ] fix ~/.gemrc
  [X] `source --add http://gems.github.com' crashes (outside gdb)
  [ ] `install rest-client' prints parsing errors (encoding problem  
in thor.gemspec)

  [ ] `gem uninstall bacon' doesn't work (Unknown gem bacon >= 0)
  [ ] `macgem install rails --version 2.3.2' crashes  
(MAX_DISPATCH_ARGS assertion)

[ ] rewrite load.c (needed for RubyGems' #require hack)

For 0.5 (must do):

[ ] implement Enumerable::Enumerator
[/] 32-bit should be back
[X] Array subclass for immediates
[ ] Hash subclass for immediates
[ ] try/catch should use a C++ exception
[ ] ObjC exceptions should be catchable in Ruby
[ ] fully implement FFI API
[ ] support for bigdecimal
[ ] support for json
[/] support for yaml
[ ] support for openssl
[/] support for zlib
[ ] merge stdlib from 1.9.2 trunk
[/] most language/core/library specs should run (modulo a very few  
exceptions)

[X] port all rb_define_method() calls to rb_objc_define_method()
[/] port all rb_funcall() calls to rb_vm_call()
[/] port all rb_num_coerce_bin() calls to rb_objc_num_coerce_bin()
[/] port all rb_obj_respond_to() calls to rb_vm_respond_to()

For 0.5 (tentative):

[ ] write a pass manager to eliminate unnecessary arrays generated  
by massigns

[ ] vectorize bignums
[ ] block inlining
[ ] fast regexp =~
[ ] rakefile-ize instruby.rb
[/] finish AOT compiler (only normal mode)
[/] sync with LLVM 2.6 (DONE in llvm26 branch, blocked by LLVM  
regressions)

[ ] multithreaded JIT
[ ] debugger interface


We identified some bugs that cause ERB to not work properly and they  
will be fixed for 0.5, however the work on the webserver didn't  
start. Stuff like CGI and openssl would first need to work.
If you want to help, the best thing you could do is to work on the  
specs with Eloy. (flag/tag the specs that fail so we know what libs  
are working, which are not) if you find bugs,replorting them in a  
simple/reproducible example is also super useful.


- Matt


On Tue, Sep 15, 2009 at 4:20 PM, Conrad Taylor   
wrote:
Is there a page where can locate what's not working?  Or open  
projects that need help?  I would be interested in both erb and the  
webserver (i.e. webrick, mongrel, and/or thin)?


Thanks in advance,

-Conrad

On Tue, Sep 15, 2009 at 4:02 PM, Matt Aimonetti > wrote:

You should always use macgem when working with macruby.
However, Sinatra isn't running yet as erb isn't fully working  
neither rack and we don't have a compatible webserver ;)


You will have to wait a little before that works, but as we are  
going through the std libs, things should start looking better.


- Matt



On Tue, Sep 15, 2009 at 2:13 PM, Conrad Taylor   
wrote:
On Thu, Sep 10, 2009 at 11:24 AM, Matt Aimonetti > wrote:

Latest trunk code available as an unofficial pkg ready to install: 
http://rubyurl.com/5K3W

Lots of bug fixes, improved macgem (not finished yet but you can  
install gems and load them using `gem 'gem_name'; require  
'whatever'`).

Things are looking pretty good on trunk :)

Hi, should one use 'macgem' instead of 'gem'?  In any case, I wanted  
to give it a try by installing sinatra:


sudo macgem install sinatra

and I received the following error message:

ERROR:  While executing gem ... (ArgumentError)
wrong number of arguments (1 for 2)

In a clean installation, the following directory doesn't exist but  
attempting to install something creates the directory and the  
installation of the gem fails:


/Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/ruby/Gems/ 
1.9.0


Now, when I tried to install the gem again, everything worked as  
expected.  For example,


$ sudo macgem install sinatra
Password:
Successfully installed rack-1.0.0
Successfully installed sinatra-0.9.4
2 gems installed

-Conrad


- Matt

___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel



___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby

Re: [MacRuby-devel] macruby nightly build 2009-09-10

[Conrad Taylor]

Hi, is this the complete application?  If not, could you generate subset of
your application that can be ran which produces the error message?
-Conrad

On Wed, Sep 23, 2009 at 2:46 PM, Robert Rice  wrote:

> Hi Laurent:
>
> Thanks for your quick reply. I have attached another file that causes a
> similar crash without a call to autorelease.
>
> Bob Rice
>
>
>
>
> On Sep 23, 2009, at 3:24 PM, Laurent Sansonetti wrote:
>
>  Hi Robert,
>>
>> The problem is line 68, the call to autorelease. If you remove it it
>> should load again. The reason is that autorelease (like release and retain)
>> are ignored selectors of the runtime. Clearly we should not crash this way,
>> I will fix that.
>>
>> Also, keep in mind that retain, release and autorelease should not be used
>> in MacRuby. We run under GC mode which makes these calls no-ops.
>>
>> Laurent
>>
>> On Sep 23, 2009, at 12:18 PM, Robert Rice wrote:
>>
>>  Hi Laurent:
>>>
>>> Thanks for your offer to help. Sorry I was busy with another project but
>>> now I get back to MacRuby.
>>>
>>> I have attached a file that causes the assertion error when loaded by the
>>> require command. Probably there is something else I need to change when
>>> porting from Ruby-Cocoa.
>>>
>>> Thanks,
>>> Bob Rice
>>> 
>>>
>>> On Sep 12, 2009, at 3:08 PM, Laurent Sansonetti wrote:
>>>
>>>  Hi Robert,

 Unless you found what was wrong, feel free to contact me off-list with a
 copy of your app and I will investigate the problem.

 Laurent

 On Sep 12, 2009, at 9:48 AM, Robert Rice wrote:

  Hi Laurent:
>
> It's a relatively large application that I ported from a RubyCocoa
> environment.
> I need the threading support hook that was removed from Ruby in the
> Snow Leopard release.
>
> I'll try to track it down better by porting and testing modules a
> little at a time.
>
> Thanks,
> Bob Rice
>
> On Sep 11, 2009, at 12:53 PM, Laurent Sansonetti wrote:
>
>  Looks like we are hitting an assertion in the symbol generator...
>> Could you send us what you are trying to execute here?
>>
>> Laurent
>>
>> Sent from my iPhone
>>
>> On Sep 11, 2009, at 9:48 AM, Robert Rice 
>> wrote:
>>
>>  How would I track down the following error from the nightly build?
>>>
>>> [Session started at 2009-09-11 12:43:22 -0400.]
>>> GNU gdb 6.3.50-20050815 (Apple version gdb-1344) (Fri Jul  3 01:19:56
>>> UTC 2009)
>>> Copyright 2004 Free Software Foundation, Inc.
>>> GDB is free software, covered by the GNU General Public License, and
>>> you are
>>> welcome to change it and/or distribute copies of it under certain
>>> conditions.
>>> Type "show copying" to see the conditions.
>>> There is absolutely no warranty for GDB.  Type "show warranty" for
>>> details.
>>> This GDB was configured as "x86_64-apple-darwin".tty /dev/ttys000
>>> Loading program into debugger…
>>> Program loaded.
>>> run
>>> [Switching to process 326]
>>> Running…
>>> Assertion failed: (1==0), function rb_intern3, file parse.y, line
>>> 9596.
>>> Program received signal:  “SIGABRT”.
>>> sharedlibrary apply-load-rules all
>>> warning: Could not find object file
>>> "/Users/mattetti/src/macruby-gitsvn/trunk/array.o" - no debug 
>>> information
>>> available for "array.c".
>>>
>>> warning: Could not find object file
>>> "/Users/mattetti/src/macruby-gitsvn/trunk/bignum.o" - no debug 
>>> information
>>> available for "bignum.c".
>>>
>>> ...
>>> Thanks,
>>> Bob Rice
>>>
>>> On Sep 10, 2009, at 2:24 PM, Matt Aimonetti wrote:
>>>
>>>  Latest trunk code available as an unofficial pkg ready to install:
 http://rubyurl.com/5K3W

 Lots of bug fixes, improved macgem (not finished yet but you can
 install gems and load them using `gem 'gem_name'; require 'whatever'`).
 Things are looking pretty good on trunk :)

 - Matt
 ___
 MacRuby-devel mailing list
 MacRuby-devel@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

>>>
>>> ___
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>

 ___
>>>

Re: [MacRuby-devel] macruby nightly build 2009-09-10

[Conrad Taylor]

Laurent, I understand that one should use the GC for MacRuby but why do we
have such a restriction?  Just curious about the history here.
Thanks in advance,

-Conrad

On Wed, Sep 23, 2009 at 3:49 PM, Laurent Sansonetti
wrote:

> Hi Robert,
>
> The problem here is dealloc. Same reason, dealloc is ignored by the
> runtime, and you should not use it in MacRuby, it will never be called.
>
> I just fixed macruby to not crash in case autorelease or dealloc is used,
> but keep in mind that using these selectors won't do anything.
>
> Laurent
>
>
> On Sep 23, 2009, at 2:46 PM, Robert Rice wrote:
>
>  Hi Laurent:
>>
>> Thanks for your quick reply. I have attached another file that causes a
>> similar crash without a call to autorelease.
>>
>> Bob Rice
>> 
>>
>>
>> On Sep 23, 2009, at 3:24 PM, Laurent Sansonetti wrote:
>>
>>  Hi Robert,
>>>
>>> The problem is line 68, the call to autorelease. If you remove it it
>>> should load again. The reason is that autorelease (like release and retain)
>>> are ignored selectors of the runtime. Clearly we should not crash this way,
>>> I will fix that.
>>>
>>> Also, keep in mind that retain, release and autorelease should not be
>>> used in MacRuby. We run under GC mode which makes these calls no-ops.
>>>
>>> Laurent
>>>
>>> On Sep 23, 2009, at 12:18 PM, Robert Rice wrote:
>>>
>>>  Hi Laurent:

 Thanks for your offer to help. Sorry I was busy with another project but
 now I get back to MacRuby.

 I have attached a file that causes the assertion error when loaded by
 the require command. Probably there is something else I need to change when
 porting from Ruby-Cocoa.

 Thanks,
 Bob Rice
 

 On Sep 12, 2009, at 3:08 PM, Laurent Sansonetti wrote:

  Hi Robert,
>
> Unless you found what was wrong, feel free to contact me off-list with
> a copy of your app and I will investigate the problem.
>
> Laurent
>
> On Sep 12, 2009, at 9:48 AM, Robert Rice wrote:
>
>  Hi Laurent:
>>
>> It's a relatively large application that I ported from a RubyCocoa
>> environment.
>> I need the threading support hook that was removed from Ruby in the
>> Snow Leopard release.
>>
>> I'll try to track it down better by porting and testing modules a
>> little at a time.
>>
>> Thanks,
>> Bob Rice
>>
>> On Sep 11, 2009, at 12:53 PM, Laurent Sansonetti wrote:
>>
>>  Looks like we are hitting an assertion in the symbol generator...
>>> Could you send us what you are trying to execute here?
>>>
>>> Laurent
>>>
>>> Sent from my iPhone
>>>
>>> On Sep 11, 2009, at 9:48 AM, Robert Rice 
>>> wrote:
>>>
>>>  How would I track down the following error from the nightly build?

 [Session started at 2009-09-11 12:43:22 -0400.]
 GNU gdb 6.3.50-20050815 (Apple version gdb-1344) (Fri Jul  3
 01:19:56 UTC 2009)
 Copyright 2004 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and
 you are
 welcome to change it and/or distribute copies of it under certain
 conditions.
 Type "show copying" to see the conditions.
 There is absolutely no warranty for GDB.  Type "show warranty" for
 details.
 This GDB was configured as "x86_64-apple-darwin".tty /dev/ttys000
 Loading program into debugger…
 Program loaded.
 run
 [Switching to process 326]
 Running…
 Assertion failed: (1==0), function rb_intern3, file parse.y, line
 9596.
 Program received signal:  “SIGABRT”.
 sharedlibrary apply-load-rules all
 warning: Could not find object file
 "/Users/mattetti/src/macruby-gitsvn/trunk/array.o" - no debug 
 information
 available for "array.c".

 warning: Could not find object file
 "/Users/mattetti/src/macruby-gitsvn/trunk/bignum.o" - no debug 
 information
 available for "bignum.c".

 ...
 Thanks,
 Bob Rice

 On Sep 10, 2009, at 2:24 PM, Matt Aimonetti wrote:

  Latest trunk code available as an unofficial pkg ready to install:
> http://rubyurl.com/5K3W
>
> Lots of bug fixes, improved macgem (not finished yet but you can
> install gems and load them using `gem 'gem_name'; require 
> 'whatever'`).
> Things are looking pretty good on trunk :)
>
> - Matt
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>

 ___
 MacRuby-devel mailing list
 MacRuby-devel@lists.macosforge.org
 http://lists.maco

Re: [MacRuby-devel] macruby nightly build 2009-09-10

[Conrad Taylor]

Hi, Objective-C could use GC and non-GC for memory management on the
desktop.
-Conrad

On Wed, Sep 23, 2009 at 4:51 PM, Jordan Breeding wrote:

> So in that case Ruby would be garbage collected, but ObjC code it uses will
> be ref counted?
>
> Sent from my iPhone
>
>
> On Sep 23, 2009, at 18:00, Laurent Sansonetti 
> wrote:
>
>  Hi Conrad,
>>
>> The thing is, MacRuby is built on top of the ObjC GC, so there is
>> currently no way you can not use it :)
>>
>> In the future we might introduce a mode where MacRuby doesn't use this GC,
>> but it's all tentative.
>>
>> Laurent
>>
>> On Sep 23, 2009, at 3:58 PM, Conrad Taylor wrote:
>>
>>  Laurent, I understand that one should use the GC for MacRuby but why do
>>> we have such a restriction?  Just curious about the history here.
>>>
>>> Thanks in advance,
>>>
>>> -Conrad
>>>
>>> On Wed, Sep 23, 2009 at 3:49 PM, Laurent Sansonetti <
>>> lsansone...@apple.com> wrote:
>>> Hi Robert,
>>>
>>> The problem here is dealloc. Same reason, dealloc is ignored by the
>>> runtime, and you should not use it in MacRuby, it will never be called.
>>>
>>> I just fixed macruby to not crash in case autorelease or dealloc is used,
>>> but keep in mind that using these selectors won't do anything.
>>>
>>> Laurent
>>>
>>>
>>> On Sep 23, 2009, at 2:46 PM, Robert Rice wrote:
>>>
>>> Hi Laurent:
>>>
>>> Thanks for your quick reply. I have attached another file that causes a
>>> similar crash without a call to autorelease.
>>>
>>> Bob Rice
>>> 
>>>
>>>
>>>
>>> On Sep 23, 2009, at 3:24 PM, Laurent Sansonetti wrote:
>>>
>>> Hi Robert,
>>>
>>> The problem is line 68, the call to autorelease. If you remove it it
>>> should load again. The reason is that autorelease (like release and retain)
>>> are ignored selectors of the runtime. Clearly we should not crash this way,
>>> I will fix that.
>>>
>>> Also, keep in mind that retain, release and autorelease should not be
>>> used in MacRuby. We run under GC mode which makes these calls no-ops.
>>>
>>> Laurent
>>>
>>> On Sep 23, 2009, at 12:18 PM, Robert Rice wrote:
>>>
>>> Hi Laurent:
>>>
>>> Thanks for your offer to help. Sorry I was busy with another project but
>>> now I get back to MacRuby.
>>>
>>> I have attached a file that causes the assertion error when loaded by the
>>> require command. Probably there is something else I need to change when
>>> porting from Ruby-Cocoa.
>>>
>>> Thanks,
>>> Bob Rice
>>> 
>>>
>>> On Sep 12, 2009, at 3:08 PM, Laurent Sansonetti wrote:
>>>
>>> Hi Robert,
>>>
>>> Unless you found what was wrong, feel free to contact me off-list with a
>>> copy of your app and I will investigate the problem.
>>>
>>> Laurent
>>>
>>> On Sep 12, 2009, at 9:48 AM, Robert Rice wrote:
>>>
>>> Hi Laurent:
>>>
>>> It's a relatively large application that I ported from a RubyCocoa
>>> environment.
>>> I need the threading support hook that was removed from Ruby in the Snow
>>> Leopard release.
>>>
>>> I'll try to track it down better by porting and testing modules a little
>>> at a time.
>>>
>>> Thanks,
>>> Bob Rice
>>>
>>> On Sep 11, 2009, at 12:53 PM, Laurent Sansonetti wrote:
>>>
>>> Looks like we are hitting an assertion in the symbol generator... Could
>>> you send us what you are trying to execute here?
>>>
>>> Laurent
>>>
>>> Sent from my iPhone
>>>
>>> On Sep 11, 2009, at 9:48 AM, Robert Rice  wrote:
>>>
>>> How would I track down the following error from the nightly build?
>>>
>>> [Session started at 2009-09-11 12:43:22 -0400.]
>>> GNU gdb 6.3.50-20050815 (Apple version gdb-1344) (Fri Jul  3 01:19:56 UTC
>>> 2009)
>>> Copyright 2004 Free Software Foundation, Inc.
>>> GDB is free software, covered by the GNU General Public License, and you
>>> are
>>> welcome to change it and/or distribute copies of it under certain
>>> conditions.
>>> Type "show copying" to see the conditions.
>>> There is absolut

Re: [MacRuby-devel] macruby nightly build 2009-09-10

[Conrad Taylor]

In regards to a MacRuby application, you would need to use GC for
Objective-C.

-Conrad

On Wed, Sep 23, 2009 at 5:00 PM, Jordan Breeding wrote:

> But would the new MacRuby interpreter be smart enough to switch between
> them and prefer GC Objc-C code, or would it be locked to one or the other?
>
> Sent from my iPhone
>
> On Sep 23, 2009, at 18:56, Conrad Taylor  wrote:
>
> Hi, Objective-C could use GC and non-GC for memory management on the
> desktop.
> -Conrad
>
> On Wed, Sep 23, 2009 at 4:51 PM, Jordan Breeding <
> jordan.breed...@me.com> wrote:
>
>> So in that case Ruby would be garbage collected, but ObjC code it uses
>> will be ref counted?
>>
>> Sent from my iPhone
>>
>>
>> On Sep 23, 2009, at 18:00, Laurent Sansonetti < 
>> lsansone...@apple.com> wrote:
>>
>>  Hi Conrad,
>>>
>>> The thing is, MacRuby is built on top of the ObjC GC, so there is
>>> currently no way you can not use it :)
>>>
>>> In the future we might introduce a mode where MacRuby doesn't use this
>>> GC, but it's all tentative.
>>>
>>> Laurent
>>>
>>> On Sep 23, 2009, at 3:58 PM, Conrad Taylor wrote:
>>>
>>>  Laurent, I understand that one should use the GC for MacRuby but why do
>>>> we have such a restriction?  Just curious about the history here.
>>>>
>>>> Thanks in advance,
>>>>
>>>> -Conrad
>>>>
>>>> On Wed, Sep 23, 2009 at 3:49 PM, Laurent Sansonetti 
>>>> <
>>>> lsansone...@apple.com> wrote:
>>>> Hi Robert,
>>>>
>>>> The problem here is dealloc. Same reason, dealloc is ignored by the
>>>> runtime, and you should not use it in MacRuby, it will never be called.
>>>>
>>>> I just fixed macruby to not crash in case autorelease or dealloc is
>>>> used, but keep in mind that using these selectors won't do anything.
>>>>
>>>> Laurent
>>>>
>>>>
>>>> On Sep 23, 2009, at 2:46 PM, Robert Rice wrote:
>>>>
>>>> Hi Laurent:
>>>>
>>>> Thanks for your quick reply. I have attached another file that causes a
>>>> similar crash without a call to autorelease.
>>>>
>>>> Bob Rice
>>>> 
>>>>
>>>>
>>>>
>>>> On Sep 23, 2009, at 3:24 PM, Laurent Sansonetti wrote:
>>>>
>>>> Hi Robert,
>>>>
>>>> The problem is line 68, the call to autorelease. If you remove it it
>>>> should load again. The reason is that autorelease (like release and retain)
>>>> are ignored selectors of the runtime. Clearly we should not crash this way,
>>>> I will fix that.
>>>>
>>>> Also, keep in mind that retain, release and autorelease should not be
>>>> used in MacRuby. We run under GC mode which makes these calls no-ops.
>>>>
>>>> Laurent
>>>>
>>>> On Sep 23, 2009, at 12:18 PM, Robert Rice wrote:
>>>>
>>>> Hi Laurent:
>>>>
>>>> Thanks for your offer to help. Sorry I was busy with another project but
>>>> now I get back to MacRuby.
>>>>
>>>> I have attached a file that causes the assertion error when loaded by
>>>> the require command. Probably there is something else I need to change when
>>>> porting from Ruby-Cocoa.
>>>>
>>>> Thanks,
>>>> Bob Rice
>>>> 
>>>>
>>>> On Sep 12, 2009, at 3:08 PM, Laurent Sansonetti wrote:
>>>>
>>>> Hi Robert,
>>>>
>>>> Unless you found what was wrong, feel free to contact me off-list with a
>>>> copy of your app and I will investigate the problem.
>>>>
>>>> Laurent
>>>>
>>>> On Sep 12, 2009, at 9:48 AM, Robert Rice wrote:
>>>>
>>>> Hi Laurent:
>>>>
>>>> It's a relatively large application that I ported from a RubyCocoa
>>>> environment.
>>>> I need the threading support hook that was removed from Ruby in the Snow
>>>> Leopard release.
>>>>
>>>> I'll try to track it down better by porting and testing modules a little
>>>> at a time.
>>>>
>>>> Thanks,
>>>> Bob Rice
>>>>
>>>> On Sep 11, 2009, at 12:53 PM, Laurent Sansonetti wrote:
>>>>
>>>> Looks like we are 

Re: [MacRuby-devel] problem with build macruby 0.5

[Conrad Taylor]

Hi, I just did an svn update of the source and build problems do exist on
Snow Leopard.  Did LLVM change ?  Is there any way to add this dependency to
the overall build because I only had LLVM issues prior to my initial install
of it?  Now, if LLVM revision starts changing without our knowledge, this
will cause issues going forward for building MacRuby.  BTW, I have been
building successfully for the last 6 months or so.
-Conrad

On Sat, Sep 26, 2009 at 5:24 PM, Laurent Sansonetti
wrote:

> Hi Sergei,
>
> It looks like trunk has build issues on both Leopard and SnowLeopard. This
> is related to the Ruby compiler (rubyc).
>
> Vincent (who runs Leopard) told me yesterday about that and it looks like
> you're hitting the same problem.
>
> Also, a few persons (including Claudio who runs the nighty build server)
> had problems on Snow Leopard. I can't reproduce the problem on my
> environment yet so it will take some time for me to fix it.
>
> If any of you running Snow Leopard was able to build trunk, let me know.
>
> Laurent
>
>
> On Sep 26, 2009, at 3:36 PM, sergei homjakov wrote:
>
>   Hello! I have problem with build macruby 0.5 (command rake)
>>
>> $ rake
>>
>> /opt/local/bin/ruby tool/compile_prelude.rb prelude.rb miniprelude.c.new
>> rm miniprelude.c.new /usr/bin/gcc -I. -I./include -I./onig
>> -I/usr/include/libxml2 -arch i386 -arch x86_64 -fno-common -pipe -O3 -g
>> -Wall -fexceptions -Wno-parentheses -Wno-deprecated-declarations -Werror
>> -std=c99 -c prelude.c -o prelude.o cp miniprelude.c prelude.c /usr/bin/g++
>> -I. -I./include -I./onig -I/usr/include/libxml2 -arch i386 -arch x86_64
>> -fno-common -pipe -O3 -g -Wall -fexceptions -Wno-parentheses
>> -Wno-deprecated-declarations -Werror -std=c99 array.o bignum.o class.o
>> compar.o complex.o enum.o enumerator.o error.o eval.o file.o load.o proc.o
>> gc.o hash.o inits.o io.o math.o numeric.o object.o pack.o parse.o prec.o
>> dir.o process.o random.o range.o rational.o re.o onig/regcomp.o
>> onig/regext.o onig/regposix.o onig/regenc.o onig/reggnu.o onig/regsyntax.o
>> onig/regerror.o onig/regparse.o onig/regtrav.o onig/regexec.o
>> onig/regposerr.o onig/regversion.o onig/enc/ascii.o onig/enc/unicode.o
>> onig/enc/utf8.o onig/enc/euc_jp.o onig/enc/sjis.o onig/enc/iso8859_1.o
>> onig/enc/utf16_be.o onig/enc/utf16_le.o onig/enc/utf32_be.o
>> onig/enc/utf32_le.o ruby.o set.o signal.o sprintf.o st.o string.o struct.o
>> time.o transcode.o util.o variable.o version.o thread.o id.o objc.o bs.o
>> encoding.o dln.o dmyext.o marshal.o gcd.o vm_eval.o prelude.o
>> bridgesupport.o compiler.o vm.o MacRuby.o -L/usr/local/lib -lpthread -lffi
>> -lm -lLLVMBitWriter -lLLVMX86CodeGen -lLLVMX86Info -lLLVMSelectionDAG
>> -lLLVMAsmPrinter -lLLVMJIT -lLLVMExecutionEngine -lLLVMCodeGen
>> -lLLVMScalarOpts -lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis -lLLVMTarget
>> -lLLVMMC -lLLVMCore -lLLVMSupport -lLLVMSystem -lpthread -ldl -lxml2 -lobjc
>> -lauto -framework Foundation -dynamiclib -undefined suppress -flat_namespace
>> -install_name
>> /Library/Frameworks/MacRuby.framework/Versions/0.5/usr/lib/libmacruby.dylib
>> -current_version 0.5 -compatibility_version 0.5 -o libmacruby.1.9.0.dylib
>> ./miniruby -I. -I./lib bin/rubyc --internal -C "lib/net/imap.rb" -o
>> "lib/net/imap.rbo" lib/net/imap.rb:1131: premature end of char-class:
>> /[\x80-\xff\r\n]/ lib/net/imap.rb:1882: end pattern in group: /\G(?:(?# 1:
>> SPACE )( +)|(?# 2: NIL )(NIL)(?=[\x80-\xff(){ \x00-\x1f\x7f%*"\\\[\]+])|(?#
>> 3: NUMBER )(\d+)(?=[\x80-\xff(){ \x00-\x1f\x7f%*"\\\[\]+])|(?# 4: ATOM
>> )([\x80-\xff(){ \x00-\x1f\x7f%*"\\\[\]+]+)|(?# 5: QUOTED
>> )"((?:[\x00\r\n"\\]|\\["\\])*)"|(?# 6: LPAR )(\()|(?# 7: RPAR )(\))|(?# 8:
>> BSLASH )(\\)|(?# 9: STAR )(\*)|(?# 10: LBRA )(\[)|(?# 11: RBRA )(\])|(?# 12:
>> LITERAL )\{(\d+)\}\r\n|(?# 13: PLUS )(\+)|(?# 14: PERCENT )(%)|(?# 15: CRLF
>> )(\r\n)|(?# 16: EOF )(\z))/i lib/net/imap.rb:2436: premature end of
>> char-class: /[\x80-\xff\r\n]/ lib/net/imap.rb:2767: end pattern with
>> unmatched parenthesis: /\G(?# 1: NAME
>> )(?:NIL|"((?:[\x80-\xff\x00\r\n"\\]|\\["\\])*)") (?# 2: ROUTE
>> )(?:NIL|"((?:[\x80-\xff\x00\r\n"\\]|\\["\\])*)") (?# 3: MAILBOX
>> )(?:NIL|"((?:[\x80-\xff\x00\r\n"\\]|\\["\\])*)") (?# 4: HOST
>> )(?:NIL|"((?:[\x80-\xff\x00\r\n"\\]|\\["\\])*)")\)/i lib/net/imap.rb:2831:
>> premature end of char-class: /(?# FLAG )\\([\x80-\xff(){
>> \x00-\x1f\x7f%"\\]+)|(?# ATOM )([\x80-\xff(){ \x00-\x1f\x7f%*"\\]+)/
>> unknown: [BUG] Segmentation fault MacRuby version 0.5 (ruby 1.9.0)
>> [universal-darwin9.0, x86_64]
>>
>> Error when executing `./miniruby --emit-llvm
>> "/var/folders/OU/OUarP1IfGbW42ZIf+RRW8E+++TI/-Tmp-/imap.bc"
>> MREP_12163095864224378147 "lib/net/imap.rb"' rake aborted! Command failed
>> with status (1): -I. -I./lib bin/rubyc --interna...
>>
>> /opt/local/bin/ruby -v
>>
>>ruby 1.8.7 (2009-06-12 patchlevel 174) [i686-darwin9]
>>
>> /opt/local/bin/rake --version
>>rake, version 0.8.7
>>
>>
>> Sergei.
>> Thanks.
>> ___

Re: [MacRuby-devel] problem with build macruby 0.5

[Conrad Taylor]

Hi Laurent, after rebuilding LLVM and MacRuby on Snow Leopard, I'm seeing
the following when I run 'macrake spec:ci':
$ macrake spec:ci
(in /Users/conradwt/macruby.dir/projects/macruby-trunk)
unknown: warning: already initialized constant MACRUBY_VERSION
./mspec/bin/mspec ci -B ./spec/macruby.mspec  :full
MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
.[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-trunk/spec/macruby/fixtures/method.m'
.[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-trunk/spec/macruby/fixtures/constant.m'
.[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-trunk/spec/macruby/fixtures/exception.m'
[!] Compiling fixture
`/Users/conradwt/macruby.dir/projects/macruby-trunk/spec/macruby/fixtures/object.m'
.cat:
stdin: Bad file descriptor
cat: stdin: Bad file descriptor
..cat: stdin: Bad file descriptor
cat: stdin: Bad file descriptor
.F.macruby(42621,0x7fff70286be0)
malloc: reference count underflow for 0x2000864e0, break on
auto_refcount_underflow_error to debug.
F.F.

1)
self.send(:block_given?) returns true if and only if a block is supplied
FAILED
Expected false not to equal false
core:in `raise:'
core:in `each'
core:in `all?'
core:in `each'

2)
Kernel#eval includes file and line information in syntax error FAILED
Expected SyntaxError
but got NoMethodError (undefined method `coerce' for
##-)
core:in `raise:'

3)
Socket::IPSocket#getaddress raises an error on unknown hostnames FAILED
Expected SocketError but no exception was raised
core:in `raise:'

Finished in 120.582898 seconds

1825 files, 8035 examples, 22067 expectations, 3 failures, 0 errors
rake aborted!
Command failed with status (1): [./mspec/bin/mspec ci -B
./spec/macruby.msp...]


On Sun, Sep 27, 2009 at 3:04 PM, Laurent Sansonetti
wrote:

> Hi Conrad
>
> Yes the llvm revision changed. I generaly advertise it on the list but I
> forgot this time. Sorry.
>
> Check the README file for more info.
>
> Laurent
>
> Sent from my iPhone
>
> On Sep 27, 2009, at 2:55 PM, Conrad Taylor  wrote:
>
> Hi, I just did an svn update of the source and build problems do exist on
> Snow Leopard.  Did LLVM change ?  Is there any way to add this dependency to
> the overall build because I only had LLVM issues prior to my initial install
> of it?  Now, if LLVM revision starts changing without our knowledge, this
> will cause issues going forward for building MacRuby.  BTW, I have been
> building successfully for the last 6 months or so.
> -Conrad
>
> On Sat, Sep 26, 2009 at 5:24 PM, Laurent Sansonetti <
> lsansone...@apple.com> wrote:
>
>> Hi Sergei,
>>
>> It looks like trunk has build issues on both Leopard and SnowLeopard. This
>> is related to the Ruby compiler (rubyc).
>>
>> Vincent (who runs Leopard) told me yesterday about that and it looks like
>> you're hitting the same problem.
>>
>> Also, a few persons (including Claudio who runs the nighty build server)
>> had problems on Snow Leo

Re: [MacRuby-devel] problem with build macruby 0.5

[Conrad Taylor]

Laurent, thanks for the update.  I just wanted to make sure that I'm in sync
with the current revision.
-Conrad

On Sun, Sep 27, 2009 at 4:43 PM, Laurent Sansonetti
wrote:

> Hi Conrad,
>
> This is well known, Matt worked on the specs yesterday night, untagging
> specs that now pass, and apparently some of them should be re-tagged :)
>
> Stay tuned,
>
> Laurent
>
>
> On Sep 27, 2009, at 4:17 PM, Conrad Taylor wrote:
>
>  Hi Laurent, after rebuilding LLVM and MacRuby on Snow Leopard, I'm seeing
>> the following when I run 'macrake spec:ci':
>>
>> $ macrake spec:ci
>> (in /Users/conradwt/macruby.dir/projects/macruby-trunk)
>> unknown: warning: already initialized constant MACRUBY_VERSION
>> ./mspec/bin/mspec ci -B ./spec/macruby.mspec  :full
>> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
>> .[!] Compiling fixture
>> `/Users/conradwt/macruby.dir/projects/macruby-trunk/spec/macruby/fixtures/method.m'
>> .[!] Compiling fixture
>> `/Users/conradwt/macruby.dir/projects/macruby-trunk/spec/macruby/fixtures/constant.m'
>> .[!] Compiling fixture
>> `/Users/conradwt/macruby.dir/projects/macruby-trunk/spec/macruby/fixtures/exception.m'
>> [!] Compiling fixture
>> `/Users/conradwt/macruby.dir/projects/macruby-trunk/spec/macruby/fixtures/object.m'
>> .cat:
>> stdin: Bad file descriptor
>> cat: stdin: Bad file descriptor
>> ..cat: stdin: Bad file descriptor
>> cat: stdin: Bad file descriptor
>> .F.macruby(42621,0x7fff70286be0)
>> malloc: reference count underflow for 0x2000864e0, break on
>> auto_refcount_underflow_error to debug.
>>
>> F.F.
>>
>> 1)
>> self.send(:block_given?) returns true if and only if a block is supplied
>> FAILED
>> Expected false not to equal false
>> core:in `raise:'
>> core:in `each'
>> core:in `all?'
>> core:in `each'
>>
>> 2)
>> Kernel#eval includes file and line information in syntax error FAILED
>> Expected SyntaxError
>> but got NoMethodError (undefined method `coerce' for
>> ##-)
>> core:in `raise:'
>>
>> 3)
>> Socket::IPSocket#getaddress raises an error on unknown hostnames FAILED
>> Expected SocketError but no exception was raised
>> core:in `raise:'
>>
>> Finished in 120.582898 seconds
>>
>> 1825 files, 8035 examples, 22067 expectations, 3 failures, 0 errors
>> rake aborted!
>> Command failed with status (1): [./mspec/bin/mspec ci -B
>> ./spec/macruby.msp...]
>>
>>
>> On Sun, Sep 27, 2009 at 3:04 PM, Laurent Sansonetti <
>> lsansone...@apple.com> wrote:
>> Hi Conrad
>>
>> Yes the llvm revision changed. I generaly advertise it on the list but I
>> forgot this time. Sorry.
>>
>> Check the README file for more info.
>>
>> Laurent
>>
>> Sent from my iPhone
>>
>> On Sep 

Re: [MacRuby-devel] Super not passing init: through to NSObject correctly?

[Conrad Taylor]

What should be the exact output?  In Ruby 1.9.1, I see the following output:
$ ruby test.rb
"A"
"B"
"C"
"D"

Note:  When .new is called allocate method is called.  Then the
object's initialize method is called and the
  instance is returned to the caller.

$ macruby test.rb
"HasInit"
"A"
"HasInit"
"B"
"C"
Segmentation fault

Now, changing the init methods to initialize, the following output is
generated:

$ ruby test.rb
"HasInit"
"A"
"HasInit"
"B"
"C"
"D"

$ macruby test.rb
"HasInit"
"A"
"HasInit"
"B"
"C"
"D"

Next, will there be an implementation of BasicObject in MacRuby as it is in
Ruby 1.9.x?

-Conrad

On Mon, Oct 5, 2009 at 7:45 PM, Laurent Sansonetti wrote:

> Thanks for the report, I added your snippet in our test suite.
>
> At a glance it looks like an infinite loop in the dispatcher. Definitely a
> bug :)
>
> Laurent
>
>
> On Oct 5, 2009, at 6:37 PM, Michael Shapiro wrote:
>
>  Hi all,
>> I searched a few months of the list archives and trac, but wasn't able to
>> find reference to this.
>>
>> Calling `super` inside of an overridden #init function where no ruby
>> ancestors define #init causes a segmentation fault. If I'm not mistaken,
>> shouldn't the init: message be passed to NSObject?
>>
>> -
>> class HasInit
>> def init
>>  super
>>  p 'HasInit'
>>  self
>> end
>> end
>>
>> class A < HasInit; end
>>
>> class B < A; end
>>
>> A.new
>> p 'A'
>> B.new
>> p 'B'
>>
>> class HasNoInit; end
>>
>> class C < HasNoInit; end
>>
>> class D < C
>> def init
>>  super
>>  self
>> end
>> end
>>
>> C.new
>> p 'C'
>> D.new
>> p 'D'
>> -
>>
>> You should see the segfault happen when trying to init D, but HasInit
>> passes the message through to NSObject just fine, it seems.
>>
>> Tested with the 2009-10-05-1158 nightly.
>>
>> Thanks!
>> --Mike
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] MacRuby 0.5 beta 1

[Conrad Taylor]

Hi Laurent, in the compatibility section, you might want to change

We want MacRuby to be as compatible as possible with existing Ruby programs.
We have been working hard on MacRuby to make sure it behaves like MRI 1.9.×.

to

We want MacRuby to be as compatible as possible with existing Ruby programs.
We have been working hard on MacRuby to make sure it behaves like Koichi's
Ruby Interpreter (KRI) or the more commonly used name, *Yet
another Ruby
VM (YARV), for Ruby *1.9.×.

In any case, great work and I'll start playing with this release.

-Conrad

On Wed, Oct 7, 2009 at 9:13 PM, Laurent Sansonetti 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
>
> The goal is to go through a few beta releases before releasing the final
> 0.5.
>
> Please give it a try and report us bugs & feedback :)
>
> Laurent
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] [0.5 beta 1] issues running ruby specs with macrake and rake

[Conrad Taylor]

a)  running spec:ci using macrake segmentation fault

$ macrake spec:ci
unknown: warning: already initialized constant TOPDIR
unknown: warning: already initialized constant CONFIG
unknown: warning: already initialized constant MAKEFILE_CONFIG
Segmentation fault

b)  running spec:ci using rake aborts

$ rake spec:ci
(in /Users/conradwt/macruby.dir/projects/macruby-trunk)
./mspec/bin/mspec ci -B ./spec/macruby.mspec  :full
MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
.2009-10-07
23:02:23.167 macruby[11134:1b07] *** Terminating app due to uncaught
exception 'NameError', reason: 'undefined method `pwd' for module
`RbConfig''
*** Call stack at first throw:
(
0   CoreFoundation  0x7fff82a995a4
__exceptionPreprocess + 180
1   libobjc.A.dylib 0x7fff86ae3313
objc_exception_throw + 45
2   libmacruby.dylib0x00010017a185 rb_vm_raise + 197
3   libmacruby.dylib0x00010003f8c9 rb_exc_raise + 9
4   libmacruby.dylib0x00010003c3d4 rb_name_error +
260
5   libmacruby.dylib0x000100040154 rb_print_undef +
196
6   libmacruby.dylib0x00010012065d rb_export_method
+ 157
7   libmacruby.dylib0x000100120d09 rb_mod_modfunc +
441
8   libmacruby.dylib0x00010016d02f rb_vm_dispatch +
5679
9   fileutils.rbo   0x0001011bdea5 __ruby_scope1 +
197
)
terminate called after throwing an instance of 'NSException'
rake aborted!
Command failed with status (): [./mspec/bin/mspec ci -B
./spec/macruby.msp...]
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [0.5 beta 1] issues running ruby specs with macrake and rake

[Conrad Taylor]

Laurent, I was interested in putting the RBO through their paces by running
the Ruby Rspecs.  Thus, is this something that's planned for a future
release?
-Conrad

On Thu, Oct 8, 2009 at 1:55 AM, Laurent Sansonetti wrote:

> This regression was introduced by r2762 (which was committed *after* the
> beta :)) and it has been reverted.
>
> Laurent
>
>
> On Oct 7, 2009, at 11:20 PM, Conrad Taylor wrote:
>
>  a)  running spec:ci using macrake segmentation fault
>>
>> $ macrake spec:ci
>> unknown: warning: already initialized constant TOPDIR
>> unknown: warning: already initialized constant CONFIG
>> unknown: warning: already initialized constant MAKEFILE_CONFIG
>> Segmentation fault
>>
>> b)  running spec:ci using rake aborts
>>
>> $ rake spec:ci
>> (in /Users/conradwt/macruby.dir/projects/macruby-trunk)
>> ./mspec/bin/mspec ci -B ./spec/macruby.mspec  :full
>> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
>> .2009-10-07
>> 23:02:23.167 macruby[11134:1b07] *** Terminating app due to uncaught
>> exception 'NameError', reason: 'undefined method `pwd' for module
>> `RbConfig''
>> *** Call stack at first throw:
>> (
>>0   CoreFoundation  0x7fff82a995a4
>> __exceptionPreprocess + 180
>>1   libobjc.A.dylib 0x7fff86ae3313
>> objc_exception_throw + 45
>>2   libmacruby.dylib0x00010017a185
>> rb_vm_raise + 197
>>3   libmacruby.dylib0x00010003f8c9
>> rb_exc_raise + 9
>>4   libmacruby.dylib0x00010003c3d4
>> rb_name_error + 260
>>5   libmacruby.dylib0x000100040154
>> rb_print_undef + 196
>>6   libmacruby.dylib0x00010012065d
>> rb_export_method + 157
>>7   libmacruby.dylib0x000100120d09
>> rb_mod_modfunc + 441
>>8   libmacruby.dylib0x00010016d02f
>> rb_vm_dispatch + 5679
>>9   fileutils.rbo   0x0001011bdea5
>> __ruby_scope1 + 197
>> )
>> terminate called after throwing an instance of 'NSException'
>> rake aborted!
>> Command failed with status (): [./mspec/bin/mspec ci -B
>> ./spec/macruby.msp...]
>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] MacRuby gem only

[Conrad Taylor]

Hi, I was thinking that it may time to update the GemSpec to support another
variable called required_ruby_implementation.  Thus, I filled an enhancement
request
https://rubyforge.org/tracker/?func=detail&aid=27269&group_id=126&atid=578

At this time, the GemSpec supports required_ruby_version but says nothing
about the implementation.  Also, it may be a good time to start upgrading
RubyGems as new Ruby implementation are currently in development or has been
released like JRuby.

On Fri, Oct 9, 2009 at 3:03 PM, Keith Gautreaux
wrote:

> Presumably Macruby gems will be installed with macgem?  Certainly, we
> would not want to fork RubyGems, but since the Gem::Platform spec
> exists shouldn't macgem only install gems whose Gem::Platform::RUBY is
> MacRuby?
>
>
The platform here seems to refer more to the type of OS.  Thus,
Gem::Platform::Ruby means
any OS which is a bit misleading.  Are we talking about the OS or the Ruby
implementation?


> For projects like JRuby and Rubinius it makes sense to always have
> Gem::Platform::RUBY == 'ruby', but isn't MacRuby a superset of Ruby
> the way Objective-C is a superset of C?
>
>
Yes, MacRuby would be considered a superset because Ruby has been
implemented on top
of the Objective-C runtime.  This is similar to JRuby, IronRuby, and so on.
 Furthermore, it
might be wise to consider that both Rubinius and JRuby may create gems that
are specific
to their respective implementations.


> As long as RubyGems prevents installation of gems whose
> Gem::Platform::RUBY == 'MacRuby' on stock YARV installations I think
> this approach is reasonable, but IANEH (I Am Not Eric Hodel).


'macgem list -r' to retrieve all the gems that are compatible with MacRuby.
 I have dealt with
this issue with Ruby 1.8.6 and 1.9.1 and it was a nightmare because
required_ruby_version
wasn't added to the GemSpec for the gem in question.  Now, the complexity
grows with new
implementations of Ruby.

Just my 2 cents,

-Conrad


> On Fri, Oct 9, 2009 at 1:55 PM, Matt Aimonetti 
> wrote:
> > Any idea how we should flag gems that are MacRuby only like textorize-mr?
> I
> > don't think the platform flag is legit so I'm not sure what to use.
> > Any ideas?
> >
> > - Matt
> >
> > ___
> > MacRuby-devel mailing list
> > MacRuby-devel@lists.macosforge.org
> > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> >
> >
>
>
>
> --
> Keith
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Using Gems in MacRuby

[Conrad Taylor]

Hi, could someone tell me the state of the iconv coding?

Thanks,

-Conrad
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] iconv coding status

[Conrad Taylor]

Hi, could someone tell me the state of the iconv coding?

Thanks,

-Conrad
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Using Gems in MacRuby

[Conrad Taylor]

On Thu, Oct 15, 2009 at 5:03 PM, s.ross  wrote:

>
> On Oct 15, 2009, at 1:43 PM, Laurent Sansonetti wrote:
>
>  Hi Craig,
>>
>> On Oct 14, 2009, at 7:07 PM, Craig Williams wrote:
>>
>>  Hi Everyone,
>>>
>>> I have searched the web but have not found a good explanation on how to
>>> use
>>> gems in a MacRuby project. Is there a tutorial I am missing?
>>>
>>
>> We should definitely write a tutorial about that. The RubyGems support is
>> pretty new so I don't think anybody tried yet to embed gems in a MacRuby
>> app. At a glance I believe it would be a matter of installing the gem inside
>> MacRuby.framework, embed it in the app then change the GEM_HOME environment
>> variable.
>>
>> Laurent
>>
>
> Oof. Changing the framework? Maybe I'm not understanding what you're
> suggesting. Why would it not be enough to install all gems in a vendor/
> directory and change GEM_HOME to there? Or something that would not involve
> embedding (eventually) all gems in use in all apps you're developing inside
> the MacRuby.framework...
>
> Steve
>
>
Steve, you should be able to install the gem(s) and require them in the
relevant file(s).  You shouldn't have to unpack the gem(s) into a vendor
directory because they should be visible to the Ruby environment after you
require it.

-Conrad


> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Using Gems in MacRuby

[Conrad Taylor]

  On Fri, Oct 16, 2009 at 12:16 AM, B. Ohr  wrote:

>
> Am 16.10.2009 um 04:55 schrieb s.ross:
>
> On Oct 15, 2009, at 6:10 PM, Conrad Taylor wrote:
>
> On Thu, Oct 15, 2009 at 5:03 PM, s.ross  wrote:
>
>>
>> On Oct 15, 2009, at 1:43 PM, Laurent Sansonetti wrote:
>>
>>  Hi Craig,
>>>
>>> On Oct 14, 2009, at 7:07 PM, Craig Williams wrote:
>>>
>>>  Hi Everyone,
>>>>
>>>> I have searched the web but have not found a good explanation on how to
>>>> use
>>>> gems in a MacRuby project. Is there a tutorial I am missing?
>>>>
>>>
>>> We should definitely write a tutorial about that. The RubyGems support is
>>> pretty new so I don't think anybody tried yet to embed gems in a MacRuby
>>> app. At a glance I believe it would be a matter of installing the gem inside
>>> MacRuby.framework, embed it in the app then change the GEM_HOME environment
>>> variable.
>>>
>>> Laurent
>>>
>>
>> Oof. Changing the framework? Maybe I'm not understanding what you're
>> suggesting. Why would it not be enough to install all gems in a vendor/
>> directory and change GEM_HOME to there? Or something that would not involve
>> embedding (eventually) all gems in use in all apps you're developing inside
>> the MacRuby.framework...
>>
>> Steve
>>
>>
> Steve, you should be able to install the gem(s) and require them in the
> relevant file(s).  You shouldn't have to unpack the gem(s) into a vendor
> directory because they should be visible to the Ruby environment after you
> require it.
>
> -Conrad
>
>
> Conrad--
>
> I guess I'm thinking of a case where you didn't want to rely on a
> particular gem being present on a target machine -- say for an app you were
> distributing. Naturally, the GEM_HOME built into MacRuby is just fine on
> *my* machine. But, if I give the app to someone else who may not have a
> particular gem installed, boom!
>
> Steve
>
>
> Steve,
>
> another solution would be, that somebody writes a gem-helper, which loads
> the required gems interactively into macgem when they are missing. This
> helper should have a Cocoa-UI for the unexperienced user outside and is
> called at program startup. Upgrading gems and testing a required version are
> possible features of such a helper.
>
> Bernd
>
>
>
Hi, you can actually find something like this in Rails as a rake task, 'rake
gems:install'.  Thus, you can take a look at the boot.rb within the config
directory.  Now, one can simply adapt the environment.rb file from rails for
loading gems and other components:

# Be sure to restart your server when you modify this file

# Specifies gem version of Rails to use when vendor/rails is not present
RAILS_GEM_VERSION = '2.3.4' unless defined? RAILS_GEM_VERSION

# Bootstrap the Rails environment, frameworks, and default configuration
require File.join(File.dirname(__FILE__), 'boot')

Rails::Initializer.run do |config|
  # Settings in config/environments/* take precedence over those specified
here.
  # Application configuration should go into files in config/initializers
  # -- all .rb files in that directory are automatically loaded.

  # Add additional load paths for your own custom dirs
  # config.load_paths += %W( #{RAILS_ROOT}/extras )

  # Specify gems that this application depends on and have them installed
with rake gems:install
  config.gem "hpricot", :version => '0.6', :source => "
http://code.whytheluckystiff.net";
  config.gem "sqlite3-ruby", :lib => "sqlite3"
  config.gem "aws-s3", :lib => "aws/s3"

  # Only load the plugins named here, in the order given (default is
alphabetical).
  # :all can be used as a placeholder for all plugins not explicitly named
  # config.plugins = [ :exception_notification, :ssl_requirement, :all ]

  # Skip frameworks you're not going to use. To use Rails without a
database,
  # you must remove the Active Record framework.
  # config.frameworks -= [ :active_record, :active_resource, :action_mailer
]

  # Activate observers that should always be running
  # config.active_record.observers = :cacher, :garbage_collector,
:forum_observer

  # Set Time.zone default to the specified zone and make Active Record
auto-convert to this zone.
  # Run "rake -D time" for a list of tasks for finding time zone names.
  config.time_zone = 'UTC'

  # The default locale is :en and all translations from
config/locales/*.rb,yml are auto loaded.
  # config.i18n.load_path += Dir[Rails.root.join('my', 'locales',
'*.{rb,yml}')]
  # config.i18n.defau

Re: [MacRuby-devel] Gem Bundler is the Future

[Conrad Taylor]

Mike, this sounds like a very interesting option for packaging gems with a
MacRuby application.  Also, one might be able to ship dynamically linked
libraries with the
application.

-Conrad

On Sat, Oct 17, 2009 at 2:50 PM, Michael Shapiro wrote:

> If the AOT compiler's being used, I wonder if there's the possibility of
> statically compiling gems into the executable itself?
>
> --Mike
>
>
> On Oct 16, 2009, at 5:01 PM, Ernest N. Prabhakar, Ph.D. wrote:
>
>   I wonder if this will help MacRuby applications:
>>
>> http://litanyagainstfear.com/blog/2009/10/14/gem-bundler-is-the-future/
>>
>>
>> Sounds like it is tied to Rails, but might be possible to extend it
>> slightly to serve our needs...
>>
>> -enp
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] rake spec:ci

[Conrad Taylor]

Hi, the 'macrake spec:ci'  is failing using r2848.

BEGIN OUTPUT:

$ macrake spec:ci
(in /Users/conradwt/macruby.dir/projects/macruby-trunk)
unknown: warning: already initialized constant MACRUBY_VERSION
./mspec/bin/mspec ci -B ./spec/macruby.mspec  :full
MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
..2009-10-18 04:25:27.098 macruby[16464:1b07] *** Terminating app due to
uncaught exception 'TypeError', reason: '42 is not a symbol'
*** Call stack at first throw:
(
0   CoreFoundation  0x7fff82a995a4
__exceptionPreprocess + 180
1   libobjc.A.dylib 0x7fff86ae3313
objc_exception_throw + 45
2   libmacruby.dylib0x000100179285 rb_vm_raise + 437
3   libmacruby.dylib0x00010003ff69 rb_exc_raise + 9
4   libmacruby.dylib0x00010003e286 rb_raise + 310
5   libmacruby.dylib0x0001000eddc0 rb_str_dump + 0
6   libmacruby.dylib0x00010011c6fe
rb_queue_get_concurrent + 46
7   libmacruby.dylib0x0001001667cd rb_vm_dispatch +
6269
8   ??? 0x00010117ff98 0x0 + 4313317272
9   libmacruby.dylib0x0001001667cd rb_vm_dispatch +
6269
10  ??? 0x000101171e55 0x0 + 4313259605
11  ??? 0x00010116d2b5 0x0 + 4313240245
)
terminate called after throwing an instance of 'NSException'
rake aborted!
Command failed with status (): [./mspec/bin/mspec ci -B
./spec/macruby.msp...]

END OUTPUT:
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Another meaningless benchmark

[Conrad Taylor]

On Thu, Oct 29, 2009 at 3:18 PM, Ernest N. Prabhakar, Ph.D. <
prabh...@apple.com> wrote:

> But what the heck, they're fun. :-)
>
> http://www.timestretch.com/FractalBenchmark.html
>
> prabhaka$ ruby --version
> ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0]
> Ruby Elapsed 4.885692
>
> prabhaka$ macruby --version
> MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, x86_64]
> Ruby Elapsed 0.251436
>
> Roughly 20x faster!  That would make us comparable to Lua for this
> benchmark -- about 30x slower than C.
>
> -- Ernie P.
>
>
Ernie, what are the units of measure here?

-Conrad


> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] call for help!

[Conrad Taylor]

On Sun, Nov 1, 2009 at 12:36 PM, Laurent Sansonetti
wrote:

> Hi guys,
>
> Things are shaping pretty nicely in trunk and we expect to release the
> second beta in a few days. We receive bug reports every day, it's great that
> people are testing it, and the final release will be awesome :-)
>
> If you are interested in contributing to the project and you do not have
> the time or expertise to learn the source code & contribute patches, there
> are still crucial things that you could do:
>

I have the following questions in regards to submitting code/patches:

1)  Is there an Xcode project file for operating on the source?

2)  How does properly create a patch file for submittal and should this be
filed as a ticket?


> 1) Test as many Ruby code (gems, libraries) as possible with MacRuby and
> report us feedback, if the code crashes, runs slowly or leaks all your
> memory. If you report a runtime crash, it would be even better if you could
> take the time to reduce the problem into a few lines of Ruby, this saves us
> (well, me :)) time. Things we don't run yet (but should): rspec, mocha,
> activesupport (that's a big one!), etc.
>

Yes, activesupport is keeping from playing with activemodel at the moment.
 Also, RSpec, at the absolute minimum, would be a great addition to the
MacRuby project.  Is anyone working on activesupport at the moment?


>

2) Write Cocoa samples! MacRuby ships with a few samples but we desperately
> need more & better ones. If you play with MacRuby to do Cocoa development
> and use a specific framework/feature, it would be awesome if you could
> contribute it back as a sample application. Things we do not cover in
> samples: core data, bindings, opengl, many Cocoa classes, etc.
>
> 3) Document your experience as part of a website tutorial or recipe. We are
> trying to build a "documentation center" for MacRuby resources at
> http://www.macruby.org/documentation.html and we desperately need more
> content. Contributing new or enhancing existing content would be greatly
> appreciated.
>
> Thanks!
>
> Laurent
>

Thanks in advance for any input in regards to the above.

-Conrad


> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] call for help!

[Conrad Taylor]

On Sun, Nov 1, 2009 at 5:19 PM, Laurent Sansonetti wrote:

> Hi,
>
>
> On Nov 1, 2009, at 5:04 PM, Conrad Taylor wrote:
>
>  On Sun, Nov 1, 2009 at 12:36 PM, Laurent Sansonetti <
>> lsansone...@apple.com> wrote:
>> Hi guys,
>>
>> Things are shaping pretty nicely in trunk and we expect to release the
>> second beta in a few days. We receive bug reports every day, it's great that
>> people are testing it, and the final release will be awesome :-)
>>
>> If you are interested in contributing to the project and you do not have
>> the time or expertise to learn the source code & contribute patches, there
>> are still crucial things that you could do:
>>
>> I have the following questions in regards to submitting code/patches:
>>
>> 1)  Is there an Xcode project file for operating on the source?
>>
>
> No, there isn't.
>
>
So, you tend to do something similar the following:

1)  [ create and ] execute the appropriate spec

2)  edit the code

3)  rake

4)  if spec_passes? go to (5).  Otherwise go to (2)

5)  move to the next issue


>
>  2)  How does properly create a patch file for submittal and should this be
>> filed as a ticket?
>>
>
> I recommend using the patch functionality of the SCM you're using. If you
> work with SVN, you can simply change files, then:
>
> $ svn diff > patch.diff
>
> And you can enclose the .diff file to a Trac ticket.
>
> .
>
>> 1) Test as many Ruby code (gems, libraries) as possible with MacRuby and
>> report us feedback, if the code crashes, runs slowly or leaks all your
>> memory. If you report a runtime crash, it would be even better if you could
>> take the time to reduce the problem into a few lines of Ruby, this saves us
>> (well, me :)) time. Things we don't run yet (but should): rspec, mocha,
>> activesupport (that's a big one!), etc.
>>
>> Yes, activesupport is keeping from playing with activemodel at the moment.
>>  Also, RSpec, at the absolute minimum, would be a great addition to the
>> MacRuby project.  Is anyone working on activesupport at the moment?
>>
>
> I looked a few weeks ago and noted a few bugs, that have been fixed since.
> It's a perpetual approach, trying to run something, hitting a bug, reducing
> it, fixing it, etc.
>
> I would prefer to have rspec working first, though :-)
>

Laurent, I will take a look at RSpec this week.

-Conrad


>
> AFAIK nobody is working on this yet.
>
> Laurent
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] rSpec for MacRuby

[Conrad Taylor]

Hi ALL, it's not too much of an issue if one is using the Ruby Version
Manager (RVM) because it creates separate executable and gem directories for
each Ruby implementation.  I haven't used MacRuby under RVM but it seems to
do an excellent job of adding the appropriate executables to the path based
on the current Ruby implementation.

-Conrad

On Mon, Nov 2, 2009 at 12:06 AM, Eloy Duran  wrote:

> 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 this, by all means :)
>
> Eloy
>
> On 2 nov 2009, at 08:40, Matt Aimonetti wrote:
>
> Unfortunately this is not an issue with MacRuby, you would have many issues
> with ruby1.9 or any other implementations.
>
> - Matt
>
> On Sun, Nov 1, 2009 at 10:52 PM, s.ross  wrote:
>
>> When installing the gem using macgem, a shebang line is written pointing
>> to macruby. The "spec" binary copied into /usr/bin forever after (or until
>> manually edited or reinstalled) contains that shebang. Until MacRuby is
>> close to parity with MRI (say... when MRI can run Rails), this may make less
>> difference. Now, however, the single-location binary can cause a problem.
>>
>> I'm not sure what a sensible solution is to this, but thought since rSpec
>> is getting some attention, I'd bring this up.
>>
>> -s
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] rSpec for MacRuby

[Conrad Taylor]

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

  Note:  I didn't like running the 'rvm-install' because it created
several different shell files:

  ~/.bash_profile, ~/.bashrc, ~/.zshrc

  where each file contained similar content.

3)  rvm list --all

 Note:  The above gets a listing of all the available interpreters.
 Also, I remember seeing macruby in the list and I'll query
 the rvm list to see if this can be reinstated.

4)  install some interpreters

 rvm install 1.9.1 1.9.2

 Note:  The above install ruby 1.9.1 and 1.9.2

5)  set the default ruby interpreter

rvm 1.9.2 --default
 or

...

Rubygems is great but the RVM team was able to get something working in a
short amount of time. Also, the gemcutter is a very good example of
extending the gem command. For example, after installing the gemcutter gem,
it inherits the 'tumble' option. Thus,one can do the following:

gem tumble

-Conrad

On Mon, Nov 2, 2009 at 1:34 AM, Eloy Duran  wrote:

> Hey Conrad,
>
> I agree that you don't notice the issue if you use RVM. But the fact
> remains that the issue still exists…
>
> So as an interim solution you can indeed use RVM or, like Laurent does, use
> a separate gem home, but on the long run, imo, RubyGems should be enhanced
> to take care of this. I, for instance, haven't been able to get RVM to work
> (disclaimer: I haven't spent a lot of time trying to get it to work).
>
> Eloy
>
> On Nov 2, 2009, at 9:26 AM, Conrad Taylor wrote:
>
> Hi ALL, it's not too much of an issue if one is using the Ruby Version
> Manager (RVM) because it creates separate executable and gem directories for
> each Ruby implementation.  I haven't used MacRuby under RVM but it seems to
> do an excellent job of adding the appropriate executables to the path based
> on the current Ruby implementation.
>
> -Conrad
>
> On Mon, Nov 2, 2009 at 12:06 AM, Eloy Duran wrote:
>
>> 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 this, by all means :)
>>
>> Eloy
>>
>> On 2 nov 2009, at 08:40, Matt Aimonetti wrote:
>>
>> Unfortunately this is not an issue with MacRuby, you would have many
>> issues with ruby1.9 or any other implementations.
>>
>> - Matt
>>
>> On Sun, Nov 1, 2009 at 10:52 PM, s.ross  wrote:
>>
>>> When installing the gem using macgem, a shebang line is written pointing
>>> to macruby. The "spec" binary copied into /usr/bin forever after (or until
>>> manually edited or reinstalled) contains that shebang. Until MacRuby is
>>> close to parity with MRI (say... when MRI can run Rails), this may make less
>>> difference. Now, however, the single-location binary can cause a problem.
>>>
>>> I'm not sure what a sensible solution is to this, but thought since rSpec
>>> is getting some attention, I'd bring this up.
>>>
>>> -s
>>> ___
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] rSpec for MacRuby

[Conrad Taylor]

On Mon, Nov 2, 2009 at 2:46 AM, Eloy Duran  wrote:

> 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
>
>   Note:  I didn't like running the 'rvm-install' because it created
> several different shell files:
>
>   ~/.bash_profile, ~/.bashrc, ~/.zshrc
>
>   where each file contained similar content.
>
>
> Yeah this is I think where it went wrong for me. Thanks! I'll give that a
> try tonight.
>
> Rubygems is great but the RVM team was able to get something working in a
> short amount of time.
>
>
> Yeah, but the point is that this is a problem of RubyGems, nobody else's
> even though others provide workarounds. Ruby allows one to specify the
> prefix/suffix, so RubyGems should inherit this transparently imo. But I
> think that in the end we agree on how the user should experience this, ie
> transparent :)
>
> Eloy
>
>
Eloy, I agree with 100%.

-Conrad


> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] rSpec for MacRuby

[Conrad Taylor]

Matt, you are correct because I'm seeing 9 failures at this time.

-Conrad

On Mon, Nov 2, 2009 at 12:55 PM, Matt Aimonetti wrote:

> Just FYI, I found one of the major issue with macruby + rspec, the problem
> being that rspec relies on Kernel.caller and MacRuby's version isn't fully
> compatible with C Ruby's.
> Anyone knows of rspec matchers for bacon?
>
> - Matt
>
>
> On Mon, Nov 2, 2009 at 11:37 AM, John Barnette wrote:
>
>> Hey,
>>
>> On Mon, Nov 2, 2009 at 12:06 AM, Eloy Duran 
>> wrote:
>> > 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 this, by all means :)
>>
>> We have some existing RubyGems bugs around this issue:
>>
>>
>> http://rubyforge.org/tracker/index.php?func=detail&aid=26754&group_id=126&atid=577
>>
>> http://rubyforge.org/tracker/index.php?func=detail&aid=25826&group_id=126&atid=575
>>
>> There's been a certain amount of discussion about this on
>> rubygems-developers, might be worth a grep of the mailing list.
>>
>>
>> ~ j.
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Speed

[Conrad Taylor]

On Sun, Nov 22, 2009 at 1:25 AM, Uliano Guerrini
wrote:

> I'm new to Ruby BECAUSE of MacRuby
>
> While learning I run this simple exercise (the sum of even fibonacci less
> than 4 million) on both MacRuby 0.5.2 and ruby 1.9.1.
>
> the recursive version runs about 5 times faster on MacRuby and that was
> expected but the iterative runs about 1000!!! times slower, and that is
> *frankly* unacceptable.
>
> What's going on?
>
> uliano
>
> def fib_rec(n)
>  n < 2 ? n : fib_rec(n-1) + fib_rec(n-2)
> end
>
>
> def fib_iter(limit)
>  yield 0
>  yield 1
>  lastbut=0
>  last=1
>  while true
>a=lastbut+last
>if a<=limit
>  yield a
>else
>  return
>end
>lastbut=last
>last=a
>  end
> end
>
>
> sum=0
> i=0
> start=Time.now
> while (f=fib_rec(i))<=4_000_000
>  sum += f if f%2==0
>  i+=1
> end
> time=Time.now-start
>
> puts 'recursive'
> puts 'sum = ',sum
> puts 'time = ',time
>
> sum=0
> start=Time.now
> fib_iter(4_000_000) { |f| sum+=f if f%2==0}
> time=Time.now-start
>
> puts 'iterative'
> puts 'sum = ',sum
> puts 'time = ',time
>
>
Uliano, what were you actual benchmarks and your system configuration?

-Conrad

___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] How far away is Cucumber and RSpec support?

[Conrad Taylor]

On Sun, Nov 22, 2009 at 10:08 PM, Joshua Ballanco  wrote:

> I've been playing with Cucumber, but so far there are still a few issues.
> It doesn't seem like anything quite so hard to deal with as RSpec, but it's
> still early days.
>
> - Josh
>
>
Josh, do you mean you're seeing issues with Cucumber on MacRuby?  In any
case, the one good thing good about gemcutter.org
is that they display the runtime dependencies if any for a given gem.  At
this time, the cucumber gem has the following runtime
dependencies:

*erm-ansicolor * =
1.0.4
*treetop* =
1.4.2
*polyglot* =
0.2.9
*builder* =
2.1.2
*diff-lcs* =
1.1.2

In addition to the above list, a lot of people tend to use the webrat gem as
well when using cucumber.  Anyway, I looked the RSpec and it was out of my
level of expertise.  RSpec team also said that they were in the process of
cleaning up things to make it easier to run on the various VMs.  In the
meantime, I'll see what happens with RSpec 2.0 alpha and MacRuby.

-Conrad


> On Nov 22, 2009, at 8:15 PM, Laurent Sansonetti wrote:
>
> > Hi Giampiero,
> >
> > The latest 0.5 beta doesn't run rspec, AFAIK. The rspec code is using too
> much dark magic that MacRuby can actually handle. Last time we check, we
> fail to run it because our #caller returns something different than the
> original Ruby.
> >
> > We might eventually run rspec in the next beta. I heard they are cleaning
> the code at the moment so maybe we will run it, indirectly.
> >
> > I know nothing about Cucumber support, yet. As usual, if you want to
> help, please try it, if it doesn't work, investigate why, reduce the problem
> and file a Trac report :-)
> >
> > Laurent
> >
> > On Nov 21, 2009, at 12:17 PM, Giampiero De Ciantis wrote:
> >
> >> I know the topic of RSpec support has come up before, specifically about
> why it doesn't function. Does anyone know if the fixes in the 0.5 release
> will cover those issues? Or is this something of 0.6?
> >>
> >> Cheers,
> >>
> >> -Gp
> >> ___
> >> MacRuby-devel mailing list
> >> MacRuby-devel@lists.macosforge.org
> >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> >
> > ___
> > MacRuby-devel mailing list
> > MacRuby-devel@lists.macosforge.org
> > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] String methods missing in MacRuby

[Conrad Taylor]

Hi, String#each is not supported in Ruby 1.9.  Also, MacRuby is based  
on Ruby 1.9 specification and not 1.8.


-Conrd

Sent from my iPhone

On Nov 28, 2009, at 4:20 PM, Jordan Breeding   
wrote:


Also, just so you know this really is a 1.8 vs 1.9 problem and not  
an MRI vs. MacRuby problem:


76 jor...@thetourist ~ > ruby test.rb
"hello, world!"
77 jor...@thetourist ~ > /opt/homebrew/bin/ruby test.rb
test.rb:3:in `': undefined method `each' for "hello,  
world!":String (NoMethodError)

78 jor...@thetourist ~ > macruby test.rb
test.rb:3:in `': undefined method `each' for "hello,  
world!":NSMutableString (NoMethodError)


test.rb:

#!/usr/bin/eval ruby

"hello, world!".each { |item| p item }

my homebrew is 1.9

On Nov 28, 2009, at 18:09, Robert Rice wrote:


Hi Jordon:

each is a documented method for the the string class so it should  
be provided. It is useful.


How would I go about filing a bug report?

Bob Rice


On Nov 28, 2009, at 3:35 PM, Jordan Breeding wrote:

I think that String.each was mixed in from Enumerable, which 1.9  
no longer does.


each is not a method on String in 1.9 either, so I don't think  
this is a MacRuby problem.


You should file a bug for the problem with split().

On Nov 28, 2009, at 14:30, Robert Rice wrote:


Hi Group:

The string.each method is undefined in MacRuby.
I can work around it by using string.each_byte then convert the  
fixnum back to a character using the i.chr method.


Also string.split( "" ) does not convert the string to an array  
as it did before.


Bob Rice
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] String methods missing in MacRuby

[Conrad Taylor]

On Sun, Nov 29, 2009 at 10:14 AM, Robert Rice  wrote:

> Thanks Jordon:
>
> I didn't realize that some core Ruby class methods changed for 1.9. I will
> update my documentation.
>
> Bob Rice
>
>
Bob, this has been well documented many months ago in both "Programming Ruby
1.9" by Dave Thomas et al and "The Programming Ruby Programming Language" by
Yukihiro Matsumoto aka Matz (i.e. the creator of the Ruby programming
language).

-Conrad


> On Nov 28, 2009, at 7:18 PM, Jordan Breeding wrote:
>
> > each is not documented for Ruby 1.9 that I know of, only for Ruby 1.8, do
> you have the Pragmatic books? They don't like each as valid for String in
> 1.9.
> >
> > If you need to file a bug though (especially for your split problem) try
> https://www.macruby.org/trac/report
> >
> > Jordan
> >
> > On Nov 28, 2009, at 18:09, Robert Rice wrote:
> >
> >> Hi Jordon:
> >>
> >> each is a documented method for the the string class so it should be
> provided. It is useful.
> >>
> >> How would I go about filing a bug report?
> >>
> >> Bob Rice
> >>
> >>
> >> On Nov 28, 2009, at 3:35 PM, Jordan Breeding wrote:
> >>
> >>> I think that String.each was mixed in from Enumerable, which 1.9 no
> longer does.
> >>>
> >>> each is not a method on String in 1.9 either, so I don't think this is
> a MacRuby problem.
> >>>
> >>> You should file a bug for the problem with split().
> >>>
> >>> On Nov 28, 2009, at 14:30, Robert Rice wrote:
> >>>
>  Hi Group:
> 
>  The string.each method is undefined in MacRuby.
>  I can work around it by using string.each_byte then convert the fixnum
> back to a character using the i.chr method.
> 
>  Also string.split( "" ) does not convert the string to an array as it
> did before.
> 
>  Bob Rice
>  ___
>  MacRuby-devel mailing list
>  MacRuby-devel@lists.macosforge.org
>  http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> >>>
> >>> ___
> >>> MacRuby-devel mailing list
> >>> MacRuby-devel@lists.macosforge.org
> >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> >>
> >> ___
> >> MacRuby-devel mailing list
> >> MacRuby-devel@lists.macosforge.org
> >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> >
> > ___
> > MacRuby-devel mailing list
> > MacRuby-devel@lists.macosforge.org
> > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] String methods missing in MacRuby

[Conrad Taylor]

On Sun, Nov 29, 2009 at 12:37 PM, Conrad Taylor  wrote:

> On Sun, Nov 29, 2009 at 10:14 AM, Robert Rice wrote:
>
>> Thanks Jordon:
>>
>> I didn't realize that some core Ruby class methods changed for 1.9. I will
>> update my documentation.
>>
>> Bob Rice
>>
>>
> Bob, this has been well documented many months ago in both "Programming
> Ruby 1.9" by Dave Thomas et al and "The Ruby Programming Language" by
> Yukihiro Matsumoto aka Matz (i.e. the creator of the Ruby programming
> language).
>

> -Conrad
>
>
>> On Nov 28, 2009, at 7:18 PM, Jordan Breeding wrote:
>>
>> > each is not documented for Ruby 1.9 that I know of, only for Ruby 1.8,
>> do you have the Pragmatic books? They don't like each as valid for String in
>> 1.9.
>> >
>> > If you need to file a bug though (especially for your split problem) try
>> https://www.macruby.org/trac/report
>> >
>> > Jordan
>> >
>> > On Nov 28, 2009, at 18:09, Robert Rice wrote:
>> >
>> >> Hi Jordon:
>> >>
>> >> each is a documented method for the the string class so it should be
>> provided. It is useful.
>> >>
>> >> How would I go about filing a bug report?
>> >>
>> >> Bob Rice
>> >>
>> >>
>> >> On Nov 28, 2009, at 3:35 PM, Jordan Breeding wrote:
>> >>
>> >>> I think that String.each was mixed in from Enumerable, which 1.9 no
>> longer does.
>> >>>
>> >>> each is not a method on String in 1.9 either, so I don't think this is
>> a MacRuby problem.
>> >>>
>> >>> You should file a bug for the problem with split().
>> >>>
>> >>> On Nov 28, 2009, at 14:30, Robert Rice wrote:
>> >>>
>> >>>> Hi Group:
>> >>>>
>> >>>> The string.each method is undefined in MacRuby.
>> >>>> I can work around it by using string.each_byte then convert the
>> fixnum back to a character using the i.chr method.
>> >>>>
>> >>>> Also string.split( "" ) does not convert the string to an array as it
>> did before.
>> >>>>
>> >>>> Bob Rice
>> >>>> ___
>> >>>> MacRuby-devel mailing list
>> >>>> MacRuby-devel@lists.macosforge.org
>> >>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>> >>>
>> >>> ___
>> >>> MacRuby-devel mailing list
>> >>> MacRuby-devel@lists.macosforge.org
>> >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>> >>
>> >> ___
>> >> MacRuby-devel mailing list
>> >> MacRuby-devel@lists.macosforge.org
>> >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>> >
>> > ___
>> > MacRuby-devel mailing list
>> > MacRuby-devel@lists.macosforge.org
>> > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] mac & ruby question

[Conrad Taylor]

TIm, does gems install correctly with Ruby 1.8.7 which is the default  
in Snow Leopard?  This should be the case.  Next, x86_64 is the  
default under Snow Leopard and your bundles are being correctly.   
Thus, I would recommend sticking with default compilation settings.
For example, the following is all you need:


gem install hpricot

Thus, I would recommend going through the process again of reinstalling.

Good luck,

-Conrad

Sent from my iPhone

On Dec 6, 2009, at 8:43 PM, Tim Rand  wrote:

I am sorry. This is not a macruby question per se, just a question  
about plain old ruby on mac (specifically snow leopard) question.  
But you guys for sure will know the answer, so I must ask. Why is it  
that after upgrading to snow leopard (10.6.2) a long list of gems no  
longer run on ruby 1.9.1?


Using Matt Aimonetti's sl_gems_update.rb file, I get:
Please reinstall:
eventmachine versions: 0.12.0, 0.12.0
fastthread versions: 1.0.1, 1.0.1
hpricot versions: 0.6.161, 0.6.161, 0.8.2, 0.8.2, 0.8.2, 0.8.2
hpricot-0.6.161/lib/universal versions: darwin9.0, darwin9.0
mongrel versions: 1.1.5, 1.1.5
rb-appscript versions: 0.5.1, 0.5.1
rmagick versions: 2.2.0, 2.2.0
rsruby versions: 0.4.5, 0.4.5
ruby-debug-base versions: 0.10.3, 0.10.3
sqlite3-ruby versions: 1.2.1, 1.2.1
tioga versions: 1.8, 1.8, 1.8, 1.8, 1.8, 1.8, 1.8, 1.8, 1.8, 1.8
tmail versions: 1.2.3.1, 1.2.3.1

Indeed, I had noticed already that hpricot, rsruby, and sqlite3 were  
no longer working.

Reinstalling eventmachine and fastthread worked.
But many of the others appear to install, but don't function:

Tim:~/Desktop/RubyClub> sudo env ARCHFLAGS="-arch i386" gem install  
why-hpricot --source http://gems.github.com

Building native extensions.  This could take a while...
Successfully installed why-hpricot-0.7.229
1 gem installed
Installing ri documentation for why-hpricot-0.7.229...
Installing RDoc documentation for why-hpricot-0.7.229...
Tim:~/Desktop/RubyClub> gem which hpricot
(checking gem why-hpricot-0.7.229 for hpricot)
/usr/local/lib/ruby19/gems/1.9.1/gems/why-hpricot-0.7.229/lib/ 
hpricot.rb

Tim:~/Desktop/RubyClub> ruby -e 'require "hpricot"'
/usr/local/lib/ruby19/gems/1.9.1/gems/why-hpricot-0.7.229/lib/ 
hpricot.rb:20:in `require': dlopen(/usr/local/lib/ruby19/gems/1.9.1/ 
gems/why-hpricot-0.7.229/lib/hpricot_scan.bundle, 9): no suitable  
image found.  Did find: (LoadError)
	/usr/local/lib/ruby19/gems/1.9.1/gems/why-hpricot-0.7.229/lib/ 
hpricot_scan.bundle: mach-o, but wrong architecture - /usr/local/lib/ 
ruby19/gems/1.9.1/gems/why-hpricot-0.7.229/lib/hpricot_scan.bundle
	from /usr/local/lib/ruby19/gems/1.9.1/gems/why-hpricot-0.7.229/lib/ 
hpricot.rb:20:in `'

from -e:1:in `require'
from -e:1:in `'

And file on that path gives:
file /usr/local/lib/ruby19/gems/1.9.1/gems/why-hpricot-0.7.229/lib/ 
hpricot_scan.bundle

Mach-O 64-bit bundle x86_64

I am pretty sure that the problem is with .bundle files being  
compiled for x86_64 architecture, but I explicitly told the os to use

env ARCHFLAGS="-arch i386"
and it ignored it and put the bundle files in the x86_64  
architecture anyhow.


I am stuck. Why am I getting the mach-o but wrong architecture error?

It seems to be a problem with gems that have .bundle files.
If anyone can explain how I should be installing gems in snow  
leopard so that they actually work, I would really like that person.  
Seriously.

Tim
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] Ruby Draft Specification

[Conrad Taylor]

Hi ALL, you may find the following link of interest:

http://ruby-std.netlab.jp

-Conrad
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] mechanize and macgems

[Conrad Taylor]

MacRuby's macgem doesn't support native gems (i.e. Nokogiri and  
Mechanize) at this time.  Thus, the same problem will occur usually  
earlier versions of the gem.


Good luck,

-Conrad

Sent from my iPhone

On Dec 26, 2009, at 7:00 PM, Jarrad Hope  wrote:


Hey Guys

First off, Id like to say im loving macruby, its awesome.

The story starts after having some issues with webkit and cookie
sharing ive decided to roll back to good ole trusty mechanize.
and thus my journey with macgem begins.

terminate called without an active exception
Abort trap

The end.

I read somewhere that its not possible due to dependancies (nokogiri)
so i thought maybe i could roll back to the pure ruby version of it...
i think was 0.8.5 - 0.8.3 ??

$sudo macgem install mechanize --version 1.8.5
Password:
ERROR:  could not find gem mechanize locally or in a repository

...

$ sudo macgem install --local mechanize-0.8.5.gem
terminate called without an active exception
Abort trap

I tried with 1.8.3, no cigar...
little help?
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] mechanize and macgems

[Conrad Taylor]

Jarred, after further analysis in regards to installing an earlier version
of the Mechanize gem (i.e. 0.8.5), it has a couple of runtime dependencies:

hpricot >= 0.5.0, Note:  This gem contains C Ruby native extensions.

hoe  >= 1.8.2, Note:  This gem contains pure Ruby code.

Thus, you'll still have issues installing earlier version of Mechanize gem
like version 0.8.5 because if depends on a gem which has C Ruby native
extensions.  I have been reading many threads on moving away from using C
Ruby extensions to using FFI which allows any client that supports FFI to
easily connect to connect to native librarie(s).  The benefit would be to
allow one to do the following:

For example, using Nokogiri as an example:

a)  build a Nokogiri interface and push the sources to github.com
b)  push the Nokogiri library sources to MacPorts, Linux distros, and so
 1)  to MacPorts, Linux distros, and so
 2)  to github.com

BTW, this is very similar to what we need to do today to interact with
MySQL, PostgreSQL, and SQLite3 relational databases from Ruby.  However,
Ruby FFI makes this process much easier.  Lastly, you can read more about
FFI here:

http://mwrc2009.confreaks.com/13-mar-2009-16-10-ffi-jeremy-hinegardner.html
http://wiki.github.com/ffi/ffi
http://www.igvita.com/2009/01/15/bridging-mri-jruby-rubinius-with-ffi/
http://blog.headius.com/2008/10/ffi-for-ruby-now-available.html
http://www.rubyinside.com/ruby-ffi-library-calling-external-libraries-now-easier-1293.html

Good luck,

-Conrad

On Sat, Dec 26, 2009 at 8:04 PM, Conrad Taylor  wrote:

> MacRuby's macgem doesn't support native gems (i.e. Nokogiri and Mechanize)
> at this time.  Thus, the same problem will occur usually earlier versions of
> the gem.
>
> Good luck,
>
> -Conrad
>
> Sent from my iPhone
>
>
> On Dec 26, 2009, at 7:00 PM, Jarrad Hope  wrote:
>
>  Hey Guys
>>
>> First off, Id like to say im loving macruby, its awesome.
>>
>> The story starts after having some issues with webkit and cookie
>> sharing ive decided to roll back to good ole trusty mechanize.
>> and thus my journey with macgem begins.
>>
>> terminate called without an active exception
>> Abort trap
>>
>> The end.
>>
>> I read somewhere that its not possible due to dependancies (nokogiri)
>> so i thought maybe i could roll back to the pure ruby version of it...
>> i think was 0.8.5 - 0.8.3 ??
>>
>> $sudo macgem install mechanize --version 1.8.5
>> Password:
>> ERROR:  could not find gem mechanize locally or in a repository
>>
>> ...
>>
>> $ sudo macgem install --local mechanize-0.8.5.gem
>> terminate called without an active exception
>> Abort trap
>>
>> I tried with 1.8.3, no cigar...
>> little help?
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] mechanize and macgems

[Conrad Taylor]

Jarred, after further analysis in regards to installing an earlier version
of the Mechanize gem (i.e. 0.8.5), it has a couple of runtime dependencies:

hpricot >= 0.5.0, Note:  This gem contains C Ruby native extensions.

hoe  >= 1.8.2, Note:  This gem contains pure Ruby code.

Thus, you'll still have issues installing earlier version of Mechanize gem
like version 0.8.5 because it depends on a gem which has C Ruby native
extensions.  I have been reading many threads on moving away from using C
Ruby extensions to using FFI which allows any client that supports FFI to
easily connect to native librarie(s).  The benefit would be to allow one to
do the following:

For example, using Nokogiri as an example:

a)  build a Nokogiri interface and push the sources to github.com
b)  push the Nokogiri library sources to
 1)  to MacPorts, Linux distros, and so
 2)  to github.com

BTW, this is very similar to what we need to do today to interact with
MySQL, PostgreSQL, and SQLite3 relational databases from Ruby.  However,
Ruby FFI makes this process much easier.  Lastly, you can read more about
FFI here:

http://mwrc2009.confreaks.com/13-mar-2009-16-10-ffi-jeremy-hinegardner.html
http://wiki.github.com/ffi/ffi
http://www.igvita.com/2009/01/15/bridging-mri-jruby-rubinius-with-ffi/
http://blog.headius.com/2008/10/ffi-for-ruby-now-available.html
http://www.rubyinside.com/ruby-ffi-library-calling-external-libraries-now-easier-1293.html

Good luck,

-Conrad
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] mechanize and macgems

[Conrad Taylor]

Eloy, I have noticed that JRuby interfaces with Nokogiri gem via FFI today
and works as expected.  Now, it would be great to have a single version of
Nokogiri that works with all Ruby VMs that support FFI interface.

-Conrad

On Mon, Dec 28, 2009 at 3:26 AM, Eloy Duran  wrote:

> 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 in regards to installing an earlier version
> of the Mechanize gem (i.e. 0.8.5), it has a couple of runtime dependencies:
>
> hpricot >= 0.5.0, Note:  This gem contains C Ruby native extensions.
>
> hoe  >= 1.8.2, Note:  This gem contains pure Ruby code.
>
> Thus, you'll still have issues installing earlier version of Mechanize gem
> like version 0.8.5 because it depends on a gem which has C Ruby native
> extensions.  I have been reading many threads on moving away from using C
> Ruby extensions to using FFI which allows any client that supports FFI to
> easily connect to native librarie(s).  The benefit would be to allow one to
> do the following:
>
> For example, using Nokogiri as an example:
>
> a)  build a Nokogiri interface and push the sources to github.com
> b)  push the Nokogiri library sources to
>  1)  to MacPorts, Linux distros, and so
>  2)  to github.com
>
> BTW, this is very similar to what we need to do today to interact with
> MySQL, PostgreSQL, and SQLite3 relational databases from Ruby.  However,
> Ruby FFI makes this process much easier.  Lastly, you can read more about
> FFI here:
>
> http://mwrc2009.confreaks.com/13-mar-2009-16-10-ffi-jeremy-hinegardner.html
> http://wiki.github.com/ffi/ffi
> http://www.igvita.com/2009/01/15/bridging-mri-jruby-rubinius-with-ffi/
> http://blog.headius.com/2008/10/ffi-for-ruby-now-available.html
>
> http://www.rubyinside.com/ruby-ffi-library-calling-external-libraries-now-easier-1293.html
>
> Good luck,
>
> -Conrad
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] detect the language of a string

[Conrad Taylor]

On Tue, Dec 29, 2009 at 10:20 PM, Matt Aimonetti wrote:

> Curious of seeing if I could use a Cocoa framework to detect the language
> of a string, I ended up finding a surprisingly clean and easy solution.
> I decided to post my findings online since I couldn't find anything when I
> googled the topic:
>
> http://merbist.com/2009/12/29/fun-with-macruby/
>
> In less than 10LOC, here is how to implement this feature:
>
> framework 'Foundation'
> class String
>
>
>   def language
> CFStringTokenizerCopyBestStringLanguage(self, CFRangeMake(0, self.size))
>
>
>   end
> end
>
> "bonne année!".language # => "fr"
>
> - Matt
>
>
Matt, this is very cool and thanks for the post.

-Conrad


> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #528: Improve Tail Call Elimination

[Conrad Taylor]

Jordan, I agree that this architectural discussion doesn't need to be a part
of the enhancement request.

-Conrad

On Thu, Dec 31, 2009 at 8:39 PM, Jordan K. Hubbard  wrote:

> I have to say - Trac seems to be a rather bad way of having architectural
> discussions.  I've been having a hard time even understanding who says what
> for the last 2-3 rounds of comments.  Wouldn't this be a better sort of
> discussion to have on the -devel mailing list, then distilling the action
> items (if any) into the Trac bug?
>
> Just a thought...  Happy New Year everyone!
>
> - Jordan
>
> On Dec 31, 2009, at 8:23 PM, MacRuby wrote:
>
> > #528: Improve Tail Call Elimination
> >
> -+--
> > Reporter:  haruki.zae...@…  |   Owner:  lsansone...@…
> > Type:  enhancement  |  Status:  new
> > Priority:  minor|   Milestone:
> > Component:  MacRuby  |Keywords:  tail call
> elimination optimisation tco
> >
> -+--
> >
> > Comment(by haruki.zae...@…):
> >
> > Replying to [comment:7 conra...@…]:
> >> If you need tail call optimization, then you're definitely concerned
> > about the wasteful calls because the goal of tail call optimization is to
> > transform
> >> recursive alogithm into iterative algorithm.
> >
> > The aim of TCO is to allow recursive algorithms to perform within a
> > constrained stack frame. Whether you choose to implement this as re-
> > writing the algorithm iteratively or instead throwing away the stack
> frame
> > is a choice.
> >
> >> I guess that you're looking for something  automatically done with
> > MacRuby VM.
> >
> > I don't mind if it's explicit :)
> >
> >> It's still your requirement to implement the appropriate traversal
> > algorithm for the data set that you're operating on.  In short, one
> should
> > use the best algorithm for the job and not rely so heavily on what's
> > happening within the language's internals.
> >
> > And I have, twice: once recursively; then again iteratively actually make
> > it perform. The former being MUCH simpler, the latter being horribly
> > complex.
> >
> > I I'm not accusing MacRuby of being flawed, I'm merely suggesting that,
> as
> > per the links posted, OO algorithms and data structures can be greatly
> > improved by languages that support TCO. Yes, it's possible to write
> > complex algorithms without TCO; it's also much easier to write them with
> > it.
> >
> > --
> > Ticket URL: 
> > MacRuby 
> >
> > ___
> > MacRuby-devel mailing list
> > MacRuby-devel@lists.macosforge.org
> > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] BirdWatch: Twitter search client written in MacRuby

[Conrad Taylor]

Issac, very nice application Issac.

-Conrad

On Sun, Jan 3, 2010 at 4:51 PM, isaac kearse  wrote:

> Hey Everyone,
>
> I just released a MacRuby app that has been sitting on my hard drive for
> too long.
> You can read about it here:
> http://isaac.kearse.co.nz/2010/01/01/birdwatch/
> and get the source here: http://github.com/isaac/BirdWatch
>
> Let me know what you think.
>
> Cheers,
> Isaac
>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #528: Improve Tail Call Elimination

[Conrad Taylor]

On Sun, Jan 3, 2010 at 8:34 PM, MacRuby  wrote:

> #528: Improve Tail Call Elimination
>
> -+--
>  Reporter:  haruki.zae...@…  |   Owner:  lsansone...@…
> Type:  enhancement  |  Status:  new
>  Priority:  minor|   Milestone:
> Component:  MacRuby  |Keywords:  tail call elimination
> optimisation tco
>
> -+--
>
> Comment(by haruki.zae...@…):
>
>  I dug a little deeper and apparently LLVM already supports quite
>  sophisticated TCO, including mutual recursion. Not sure why that doesn't
>  take effect in MacRuby but I assume it's due to the way calls are
>  constructed. Anyway, it's now well and truly outside my abilities.
>
>  Thanks,
>  Simon
>
>
Simon, after reading you blog post on the subject, I feel that you're well
versed on the subject matter of TCO.  Yes, LLVM supports TCO very
well and building languages in general.  I would recommend learning a bit
about LLVM and llvm.org has some excellent documentation.  Also, they
have several resources to receive assistance.  After you feel comfortable
with LLVM, then looking at the problem within the MacRuby would  should
become much easier.

Good luck,

-Conrad


> --
> Ticket URL: 
> MacRuby 
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] String methods missing in MacRuby

[Conrad Taylor]

Bob, I really don't have any information about the Ruby.pdf.  In any case, I
would recommend consulting an update to date reference like the ones that I
mentioned below.

Good luck,

-Conrad

On Sun, Nov 29, 2009 at 2:36 PM, Robert Rice  wrote:

> Hi Conrad:
>
> I don't remember where I downloaded my Ruby.pdf file from - it has no
> credit information.
>
> I suspect you will have lots of other users upgrading directly from Ruby
> 1.8.7 to the new MacRuby.
>
> Bob Rice
>
>
> On Nov 29, 2009, at 3:38 PM, Conrad Taylor wrote:
>
>
>
> On Sun, Nov 29, 2009 at 12:37 PM, Conrad Taylor wrote:
>
>> On Sun, Nov 29, 2009 at 10:14 AM, Robert Rice wrote:
>>
>>> Thanks Jordon:
>>>
>>> I didn't realize that some core Ruby class methods changed for 1.9. I
>>> will update my documentation.
>>>
>>> Bob Rice
>>>
>>>
>> Bob, this has been well documented many months ago in both "Programming
>> Ruby 1.9" by Dave Thomas et al and "The Ruby Programming Language" by
>> Yukihiro Matsumoto aka Matz (i.e. the creator of the Ruby programming
>> language).
>>
>
>> -Conrad
>>
>>
>>> On Nov 28, 2009, at 7:18 PM, Jordan Breeding wrote:
>>>
>>> > each is not documented for Ruby 1.9 that I know of, only for Ruby 1.8,
>>> do you have the Pragmatic books? They don't like each as valid for String in
>>> 1.9.
>>> >
>>> > If you need to file a bug though (especially for your split problem)
>>> try https://www.macruby.org/trac/report
>>> >
>>> > Jordan
>>> >
>>> > On Nov 28, 2009, at 18:09, Robert Rice wrote:
>>> >
>>> >> Hi Jordon:
>>> >>
>>> >> each is a documented method for the the string class so it should be
>>> provided. It is useful.
>>> >>
>>> >> How would I go about filing a bug report?
>>> >>
>>> >> Bob Rice
>>> >>
>>> >>
>>> >> On Nov 28, 2009, at 3:35 PM, Jordan Breeding wrote:
>>> >>
>>> >>> I think that String.each was mixed in from Enumerable, which 1.9 no
>>> longer does.
>>> >>>
>>> >>> each is not a method on String in 1.9 either, so I don't think this
>>> is a MacRuby problem.
>>> >>>
>>> >>> You should file a bug for the problem with split().
>>> >>>
>>> >>> On Nov 28, 2009, at 14:30, Robert Rice wrote:
>>> >>>
>>> >>>> Hi Group:
>>> >>>>
>>> >>>> The string.each method is undefined in MacRuby.
>>> >>>> I can work around it by using string.each_byte then convert the
>>> fixnum back to a character using the i.chr method.
>>> >>>>
>>> >>>> Also string.split( "" ) does not convert the string to an array as
>>> it did before.
>>> >>>>
>>> >>>> Bob Rice
>>> >>>> ___
>>> >>>> MacRuby-devel mailing list
>>> >>>> MacRuby-devel@lists.macosforge.org
>>> >>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>> >>>
>>> >>> ___
>>> >>> MacRuby-devel mailing list
>>> >>> MacRuby-devel@lists.macosforge.org
>>> >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>> >>
>>> >> ___
>>> >> MacRuby-devel mailing list
>>> >> MacRuby-devel@lists.macosforge.org
>>> >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>> >
>>> > ___
>>> > MacRuby-devel mailing list
>>> > MacRuby-devel@lists.macosforge.org
>>> > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>> ___
>>> MacRuby-devel mailing list
>>> MacRuby-devel@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>
>>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] MacRuby System Requirements?

[Conrad Taylor]

Hi, could someone add the MacRuby system requirements (i.e. OS version) to
the MacRuby.com website so that it clear to new users and developers?

Thanks,

-Conrad
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] MacRuby System Requirements?

[Conrad Taylor]

On Thu, Feb 4, 2010 at 3:50 PM, Matt Aimonetti wrote:

> It's not that simple, it depends how you build MacRuby. For instance, the
> installer for the latest version explicitly tells you that it will only
> install MacRuby on SnowLeopard, however you can build your own Leopard
> installer.
>
> - Matt
>
>
Matt/Laurent would this work for the requirements section for MacRuby:

Officially, MacRuby requires Mac OS 10.5 or higher using an Intel processor.
 However, Leopard isn't being supported much anymore and all of the core
MacRuby developers are currently using Snow Leopard.  Thus, the MacRuby team
recommends using Snow Leopard with a 64-bit Intel processor.  The options
for installing MacRuby are as follows:

Snow Leopard Users:

- install the nightly build
- install from the sources

Leopard Users:

- install from the sources


> On Thu, Feb 4, 2010 at 12:38 PM, Conrad Taylor  wrote:
>
>> Hi, could someone add the MacRuby system requirements (i.e. OS version) to
>> the MacRuby.com website so that it clear to new users and developers?
>>
>> Thanks,
>>
>> -Conrad
>>
>>
>>
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] macruby does not compile for me on Lion with xcode 4.1

[Conrad Taylor]

Hi, is it necessary to the install llvm-config or llvm if you're using Mac
OS 10.7 and Xcode 4.1?

Thanks in advance,

-Conrad
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] macruby does not compile for me on Lion with xcode 4.1

[Conrad Taylor]

On Sat, Jul 23, 2011 at 7:00 PM, Watson  wrote:

> Hi,
>
> According to the README, please install the LLVM if you will compile
> the MacRuby.
> https://github.com/MacRuby/MacRuby/blob/master/README.rdoc
>
> Thanks,
>
>
Thanks for the information but this doesn't answer my initial question.  I
just don't want my Xcode builds to break now that I have things set up
properly.

-Conrad


> 2011/7/24 Conrad Taylor :
> > Hi, is it necessary to the install llvm-config or llvm if you're using
> Mac
> > OS 10.7 and Xcode 4.1?
> > Thanks in advance,
> > -Conrad
> >
> > ___
> > MacRuby-devel mailing list
> > MacRuby-devel@lists.macosforge.org
> > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> >
> >
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] MacRuby and ARC was: Advice for Total Tyro

[Conrad Taylor]

Sent from my iPhone

On Oct 17, 2011, at 2:26 PM, Igor Evsukov  wrote:

> Hi Henry,
> 
>> This doesn't explain why MacRuby can't be implemented with ARC rather than 
>> relying on the OBJ-C 2 garbage collector.
> Do You know what the difference between Garbage Collection and Reference 
> Counting?
> 

Igor, ARC happens at compile time not runtime.  This feature is implemented in 
the Objective-C runtime.

-Conrad

> Current MacRuby VM implementation heavily depends on presence of GC. 
> Potentially You could modify it to use ARC instead. The question is how much 
> time do you need to spent on it and how you plan to support C extensions? 
> 
> Again, please, watch the end of Joshua Ballanco talk at BostonRB ( 
> http://bostonrb.org/presentations/macruby-what-is-it-and-why-should-i-care-part-1
>  ) when he talk about issues of porting MacRuby to iOS. It isn't an issue to 
> move MacRuby to it's own GC, there even was some efforts to do it 
> https://github.com/takuma104/iphone-macruby 
> 
> On 17 окт. 2011, at 23:28, Henry Maddocks wrote:
> 
>> 
>> On 17/10/2011, at 7:11 PM, Igor Evsukov wrote:
>> 
>>> Hi Henry,
>>> 
> And it's impossible to make Ruby to use ARC.
 
 Why?
>>> For memory management Objective-C uses a paradigm called "reference 
>>> counting". 
>> 
>> ...
>> 
>>> In Ruby we have garbage collector which is acts in whole different way 
>> 
>> I understand all this. But I'm not asking about _Ruby_, I'm asking about the 
>> MacRuby OBJ-C implementation of the Ruby language.
>> 
>>> So, basically, ARC and GC are two conceptually different things which are 
>>> even not replaceable by each other(circular references).
>> 
>> This doesn't explain why MacRuby can't be implemented with ARC rather than 
>> relying on the OBJ-C 2 garbage collector.
>> 
>> Henry
>> 
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> 
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] MacRuby and ARC was: Advice for Total Tyro

[Conrad Taylor]

Sent from my iPhone

On Oct 17, 2011, at 2:26 PM, Igor Evsukov  wrote:

> Hi Henry,
> 
>> This doesn't explain why MacRuby can't be implemented with ARC rather than 
>> relying on the OBJ-C 2 garbage collector.
> Do You know what the difference between Garbage Collection and Reference 
> Counting?
> 

Igor, I forgot to point out that ARC and GC are not the same thing.  They have 
very different functions.  Again, ARC happens at compile time and GC happens at 
runtime.  Thus, I would highly recommend taking a look at the WWDC 2011 videos 
which go into further depth on this subject. Finally, ARC is supported in Xcode 
4.2. 

Good luck,

-Conrad

> Current MacRuby VM implementation heavily depends on presence of GC. 
> Potentially You could modify it to use ARC instead. The question is how much 
> time do you need to spent on it and how you plan to support C extensions? 
> 
> Again, please, watch the end of Joshua Ballanco talk at BostonRB ( 
> http://bostonrb.org/presentations/macruby-what-is-it-and-why-should-i-care-part-1
>  ) when he talk about issues of porting MacRuby to iOS. It isn't an issue to 
> move MacRuby to it's own GC, there even was some efforts to do it 
> https://github.com/takuma104/iphone-macruby 
> 
> On 17 окт. 2011, at 23:28, Henry Maddocks wrote:
> 
>> 
>> On 17/10/2011, at 7:11 PM, Igor Evsukov wrote:
>> 
>>> Hi Henry,
>>> 
> And it's impossible to make Ruby to use ARC.
 
 Why?
>>> For memory management Objective-C uses a paradigm called "reference 
>>> counting". 
>> 
>> ...
>> 
>>> In Ruby we have garbage collector which is acts in whole different way 
>> 
>> I understand all this. But I'm not asking about _Ruby_, I'm asking about the 
>> MacRuby OBJ-C implementation of the Ruby language.
>> 
>>> So, basically, ARC and GC are two conceptually different things which are 
>>> even not replaceable by each other(circular references).
>> 
>> This doesn't explain why MacRuby can't be implemented with ARC rather than 
>> relying on the OBJ-C 2 garbage collector.
>> 
>> Henry
>> 
>> ___
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> 
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] MacRuby: The Definitive Guide

[Conrad Taylor]

On Thu, Nov 3, 2011 at 3:48 AM, Takao Kouji  wrote:

> +1
> I bought the iBooks, so I bring it everyday :) Thanks.
>
> On 2011/11/02, at 19:46, Matt Aimonetti wrote:
>
> > Hey guys, if you pre ordered the hard copy of my book, it should arrive
> in a few days (just got mine).
> > Otherwise you can buy from O'Reilly:
> http://shop.oreilly.com/product/063692723.do or Amazon:
> http://amzn.to/tVx4ng (cheaper)
> > Digital versions are available on the iBooks and Kindle marketplaces and
> available in a all included format package on the O'Reilly website.
> >
> > I would sincerely appreciate if some of you could leave reviews on
> Amazon or O'Reilly, especially if my writing managed to help you out in the
> past.
> > 
> >
> > Thanks,
> >
> > - Matt
>

Matt, it's great to hear that you have written a book and I look forward to
reading it.

-Conrad


> > ___
> > MacRuby-devel mailing list
> > MacRuby-devel@lists.macosforge.org
> > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> ---
> TAKAO Kouji 
> blog: http://d.hatena.ne.jp/kouji0625/
> twitter: takaokouji / projects: ruby, s7-seven
>
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] A Future for MacRuby

[Conrad Taylor]

On Wed, Dec 21, 2011 at 2:45 PM, Dan Farrand
wrote:

> It's been great to read everyones thoughts on this subject.  It's helped
> me get a better perspective on what MacRuby is.
>
> I am a Ruby newbie but have been working on Mac for a long time, mostly in
> the "business applications" space.
>
> Here is my 2 cents.  I am very much a Mac fanboy and consequently an Apple
> advocate.  However, I think Apple's weak spot going into the future is
> Objective-C.  I view this issue as somewhat separate from Cocoa, but maybe
> folks who know more than I do will tell me that they are fused together.
>
> I don't actually find it pleasurable to code in Objective-C.  There just
> seems to be too much abstraction, syntax and long rambling class/method
> names cluttering up the the editor window.  I do find Ruby enjoyable to
> code in.
>
> I view Ruby as a way for Apple to provide more accessible pathways for
> would-be Mac and iOS developers.  I had thought this might even have been
> Apple's idea in supporting MacRuby,   But after hearing from everyone,  I'm
> guessing it's more of a "lets keep our options open" attitude and Apples
> support is real but speculative.
>
> There is certainly no indication that Apple sees a problem with it's
> dependence on Objective-C.  The Steve Jobs Apple probably sees it as a big
> plus because they effectively control the language.
>
>
Objective-C isn't controlled by Apple.  However, the Cocoa and iOS APIs are
because it's specific to their underlying operating systems.  BTW, Apple
has also open sourced all of the Objective-C specific features so that
other Objective-C implementation like GNU can evolve as well.  Next, Tim
Budd, the original creator of Objective-C, who comes from a Smalltalk
background wanted something similar to Smalltalk which allowed one to
easily interface with both C/C++ libraries.  This is how Objective-C was
born.  Now, if we go back even further in time, Steve Jobs also received a
demonstration of a Smalltalk environment.  It would have been nice to write
applications in Smalltalk for the Mac OS back then but Apple in the past,
present, and future has the following operating objectives:

a)  understands that their core expertise is designing, implementing, and
deploying awesome products.
b)  enhanced existing language features to meet the needs of the project
and support the developer community
c)  if a language's feature set is truly awesome and it's a step above what
we are currently using, then let's do some prototypes
 and evaluate its potential.
d)  a plethora of other things to consider

As you can see, running a business is not the same as running an open
source project.  You need to look at something like a language
change/addition from business perspective as well as the overall investment
of resources and still be able to fulfill the goals of (a).  Please don't
get me wrong but I truly enjoy MacRuby but you cannot always expect Apple
to fully support every open source project that comes there way.  It must
be in the best interest of the company to do so.  If you want to build Mac
OS X and iOS applications today, you'll need to get comfortable at some
level with Objective-C.  Xcode is great and it beats a Makefile any day.

Think different and code well

-Conrad



> If nothing else, it looks like MacRuby is a fun way to poke around inside
> Cocoa so it's worth pushing into.
>
> thanks everyone for taking the time to respond to my original query.
> ___
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel