As Matt writes, the standard library only contains extra classes.
Everything accessible without a #require is part of the core, which
cannot be stripped down during the deployment phase (yet).
As of trunk (0.6), the stdlib files are in /Library/Frameworks/
MacRuby.framework/Versions/0.6/usr/lib/ruby. It's a mix of Ruby and C
extension bundles. These are the files that will be removed.
HTH,
Laurent
On Feb 4, 2010, at 9:59 AM, Matt Aimonetti wrote:
std libs are all the "extra" classes that you need to require in
your code like rexml, yaml, CGI etc...
- Matt
On Thu, Feb 4, 2010 at 8:39 AM, Anthony Buck <r...@arbia.co.uk> wrote:
Thank you for such prompt response! I am surprised that the standard
lib can be left out though! Is there any formal/informal list of what
ruby considers "standard library"? Can we safely assume that most
container classes are available for instance? Array, Hash etc? Am I
right in assuming that what is left out is anything that warrants a
"require" statement?
Again, Thanks!
Anthony
On 4 February 2010 01:36, Anthony Buck <r...@arbia.co.uk> wrote:
> Hi all,
> I have a couple of questions which I have attempted to answer to
> no-avail. I was wondering if anyone could point me in the right
> direction (Quite new to OS X development so my apologies if it is
> mealy my incompetence that has lead me here.)
>
> 1) I am looking into using MacRuby and am interested in it's
ability
> to AOT compile ruby code down to an executable. I am wondering
though
> whether this places a restriction on the code in any way? Is there a
> subset of ruby which is supported or can i go ahead and perform all
> the meta-magic i want and still have the code AOT compiled?
>
> 2) I am also interested in targeting both 10.6 and 10.5 with any
> applications developed (at 50%+ OS X share it is imposable to ignore
> with any conscience.) I have looked at the deployment task shipped
> with Mac Ruby and love the fact that I can have a simple .app to
pass
> on to my users however, am i right in thinking that this .app will
> only operate on 10.6 machines? If so is there any way to develop
> either a combined or separate .app which is useful to users of 10.5?
> Is this possible when the development system is 10.6?
>
> 3) I also read an article about how the developer of Stopwatch*
> packaged said application without the "standard library." am I right
> in thinking that this is the ruby standard library which was left
> unpackaged? Wouldn't this render the application un-runnable?
>
> Any advice on any of the 3 questions is much appreciated.
>
> Regards,
>
> Anthony Buck
>
>
> * http://isaac.kearse.co.nz/2010/01/31/stopwatch/
>
_______________________________________________
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
