July 2009 - MacRuby-devel - lists.macosforge.org

Porting Rational
by dan sinclair 30 Jul '09

30 Jul '09

Hello, I started to port the Rational code to the objc interfaces. There are currently 8 specs left for rational that I haven't been able to get to pass. As part of the rational I also did a bit of the Complex code but there are some specs in there that are segv'ing so I'm not sure how many of those pass at the moment. Patch is attached. Let me know if I need to fix anything up. Thanks, dan (I would have logged this into trac but I can't seem to login at the moment. Continuously redirects between http://www.macruby.org/auth/ login and https://www.macruby.org/auth/login)

2 2

Xcode Executable Arguments
by Edward Hynes 29 Jul '09

29 Jul '09

Hi, I'm working on localization for a MacRuby app and would like to be able to set the language in the Executable Info's Arguments tab in Xcode, but the arguments are being gobbled up by MacRuby. Is there a way to escape or quote executable arguments so that they are passed through to the application? I'm setting the arguments using the defaults command for now, but it would prefer doing so within Xcode if possible. Thanks, Ed -- Edward Hynes Dharma Gaia LLC "Software with the Earth in Mind" http://dharmagaia.com

1 0

assign value to identifier in runtime with objc codes
by Linan Wang 27 Jul '09

27 Jul '09

Hi everybody,I'm trying to migrate from FScript to MacRuby. The problem I'm facing now is how to assign values to variables in the macruby runtime with objc codes. In Fscript framework, it's fairly straightforward: setObject:forIdentifier call of FSInterpreter. I've tried rb_define_varible but it does not work. seems it requires rb_objc_ocval_to_rval function call to convert the objc object to ruby object first. Any help is appreciated. Thanks -- Best regards Linan Wang

2 4

Just Too Late (JTL) compilation
by Rich Morin 27 Jul '09

27 Jul '09

This seems like an interesting possibility for MacRuby... http://etoileos.com/news/archive/2009/07/23/2218/ -r -- http://www.cfcl.com/rdm Rich Morin http://www.cfcl.com/rdm/resume rdm(a)cfcl.com http://www.cfcl.com/rdm/weblog +1 650-873-7841 Technical editing and writing, programming, and web development

3 3

experimental branch: status update
by Laurent Sansonetti 27 Jul '09

27 Jul '09

Here is another status update on the experimental branch. I forgot to send this one earlier, sorry. Highlights: - Unicode strings! You can now create strings containing multibyte characters in your MacRuby programs and apply the String methods on them (even regular expressions!). - Digest extensions (bubblebabble, md5, rmd160, sha1, sha2) are now available. - The readline extension is also available. It means macirb has history and editing features again! Unfortunately the bugs are still there, though :) - The strscan C extension was rewritten in pure Ruby and imported into the repository. All the specs but one pass and new specs have been written too. Changes: - Fixed a regression in the instance variable lookup. - IO#gets now returns tainted strings. - Implemented Fixnum#popcnt, a MacRuby extension to Fixnum that counts the number of set bits in a number. - Fixed a bug in rb_str_each_byte. - Implemented ByteString#getbyte, ByteString#setbyte, ByteString#bytesize. - Fixed a bug in the super dispatcher: now ignoring all call stack items before the receiver's implementation, to work around false positives in our stack check. - Fixed the compilation of return from a higher level block (ex: 1.times { 1.times { return } }). - Fixed 2 compilation bugs in NODE_OP_ASGN1 (ex: a[1]||=1+1). - Fixed a compilation problem where the LLVM sret attribute was applied to the return value of the C stub, and not the 1st argument as it should be. - Fixed a lot of broken methods in Process and implemented a preliminary fork(). - Local variables used as dynamic variables should now be saved correctly even if an exception is raised. - Implemented Kernel#select and ensured that all the specs pass. - Re-enabled File#path, File#atime, made their specs pass. - Re-enabled File#ctime and File#mtime, wrote File#chmod, fixed File.chmod, and made them all pass the specs. - Implemented String#ascii_only? using CFCharacterSets. - Re-enabled File#truncate and made sure it passes its specs. - Fixed a pretty severe bug in IO#ioctl. (But if you're actually using ioctl, you're insane.) - Delay the require of -r libs until the compiler is available. - IO#lineno= now calls to_int on its inputs. - Made the STDIN, STDOUT, and STDERR constants have a nice printable path. - Lots of changes to make mkmf.rb work again. - Fixed a bunch of serious IO bugs (especially in IO.copy_stream). - Fixed a bug in the way we implemented break inside a block: now cleaning the broken_with VM value at the end of the dispatcher to avoid side-effects of pure Ruby calls of blocks vs C calls of blocks. - Unlocked mutexes are now automatically unlocked once the thread that locked them dies (rubyspec conformance). - Now raising an exception when trying to unlock a mutex that is locked by another thread (rubyspec conformance). - Fixed bugs in Mutex#synchronize and thread's unlock all mutexes logic: do not raise exceptions (rubyspec conformance). - Fixed the return value of attribute assignments. - Fixed String#[] to work if the given range is larger than the string's length. - Implemented Kernel#warn. - Fixed +[MacRuby sharedRuntime] to initialize the shared compiler. - IO#write: if the receiver isn't an IO object, dispatches the write: selector on it instead. - Our rubyspec suite now includes library specs. spec:library will only run them, and spec:ci will also include them. Very important change: these rake tasks are now using the macruby executable (setting DYLD_LIBRARY_PATH to use the local libmacruby.dylib) and not miniruby anymore. It means you must build macruby before starting these tasks. If you hack on MacRuby, make sure to build the macruby:dylib task before starting the specs, otherwise your changes might not be taken into account by mspec! - The digest C extensions (bubblebabble, md5, rmd160, sha1, sha2) have been ported to the new runtime APIs and are now compiled and installed. All their specs pass. - Unicode work: All strings coming from the parser are now compiled as unicode character arrays, then we generate CFString objects at runtime based on them. The final encoding of these strings is picked by CoreFoundation for us. The String#encoding method returns the fastest encoding of the receiver, which is generally MacRoman for ASCII strings and UTF16 for strings containing multibyte characters. It is now possible to apply regular expressions on strings containing multibyte characters, but it is not yet possible to create a regular expression containing multibyte characters yet. This work is still under development and it is not yet compatible with the upstream 1.9 semantics of unicode strings. But at least you can create unicode strings in your MacRuby programs and use the String methods on them. Report us bugs please :) Laurent

2 1

roadmap for 0.5
by Laurent Sansonetti 27 Jul '09

27 Jul '09

So, we are progressing well, but there are still many things to do before reaching the major goal: the 0.5 release. Here is a roadmap I cooked. Let me know if you have any feedback (or if I forgot anything). First, we need to merge the experimental branch merge into trunk. I think we need 3 important things first: * irb should work. This mostly implies minor bug fixes around the Binding class. * rake should work. Also, minor bug fixes. * hotcocoa should work. Most of the hotcocoa framework is already working except the part where it loads YAML expressions, because the yaml library doesn't exist yet. We need a yaml implementation and I personally don't want syck. I think we will go with a quick wrapper around the libyaml C library (http://pyyaml.org/wiki/LibYAML) which seems to be fast and stable. We expect to reach this goal within a few days. Then, we will merge experimental into trunk and we can finally start polishing the project to prepare the next release. Here is the list of things I think we must support for the release: * implement/port Marshal, Enumerable::Enumerator, Rational, Complex to the new runtime APIs. * 32-bit support should be back. This implies fixing the compilation of C stubs and backporting the floating point optimization to 32-bit floats. * Array/Hash subclasses for immediates. We need a new subclass that can hold immediates (fixnums, floats, true, false, nil) directly, for performance reasons. * Backtracing/symbolication. As you could surely experience, backtraces from MacRuby are mostly empty, because this part has not been implemented yet! * try/catch should use a C++ exception instead of SjLj. * rewrite of load.c. The current file is just too evil and it contains silly bugs. * FFI API should be fully implemented. The current implementation is super minimal (we only have #attach_function) and all the specs are in the repository, so we can start. * rubyspec: pass almost all language+core+library specs only with a very few and well controlled exceptions. * compiler should always generate valid code. To achieve this, we need to enable the module verifier (disabled by default because it's super slow) and try to run spec:ci. * the bigdecimal, stringio, json, zlib extensions should be implemented in pure Ruby (with FFI calls when needed). * socket APIs should be implemented, preferably using CFStreams, for performance reasons. * rubygems should fully work (except for C extensions gems). This means we need the socket APIs and most likely a few bug fixes. We will run the rubygems test suite. * merge stdlib with ruby 1.9.2 upstream. Now, here is a list of tentative items, things that are not necessarily critical for the release but nevertheless important. Some of them might be completed by then, some not. * rakefile-ize the instruby.rb script. Chance: low. * massign arrays elimination pass. Multiple assignments generate an array as the return value. Most of the time, this array is not needed. Chance: medium. * bignum vectorization. Use a bignum vectorization library to re- implement Bignum. Chance: medium. * Finish the AOT compiler. Chance: high. * multithreaded JIT. Compiling Ruby from different threads to improve startup time when loading large libraries. Requires the new LLVM trunk changes. Chance: low. * debugger interface. Chance: low. * work with LLVM trunk / future 2.6 release. LLVM trunk moves too fast, adds lots of API changes and sometimes doesn't build at all. Chance: low. Laurent

1 0

Building the Experimental Branch
by Steven Canfield 27 Jul '09

27 Jul '09

Hey All,This is my first post to this list so I should introduce myself. My name is Steven Canfield I've just graduated from a Master's program in Computer Science and am doing iPhone development as my day job. I've found the MacRuby project intriguing since it was announced (and helpful in my last semester) so I'm ready to start giving back. I've checked out the experimental branch and am trying to work through some of the spec tests from http://github.com/alloy/mr-experimental/blob/master/spec/README.rdoc However, I can't get MacRuby to actually build. Right now I am using revision 2088 of the experimental branch. When I try to build (using 'rake'), I get Assertion failed: (ee != NULL), function RoxorCore, file vm.cpp, line 208. rake aborted! Command failed with status (): [../../miniruby -I../.. -I../../lib -r rbco...] Looking into that it's clearly something with LLVM. I figure it's probably the specific LLVM version I am using, but I've tried both 72741 (mentioned in the Readme.rdoc file) and trunk (77106). I get the same error with each. I'm doing this on 10.6 so if there are special instructions for that you could reply to me off list. Thanks for any guidance, -Steve

2 2

compiling macruby
by Daniel 22 Jul '09

22 Jul '09

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

2 2

Re: [MacRuby-devel] web site nits (resend)
by Matt Aimonetti 15 Jul '09

15 Jul '09

applied, thanks. - Matt On Wed, Jul 15, 2009 at 12:45 PM, Rich Morin <rdm(a)cfcl.com> wrote: > At 11:41 -0700 7/15/09, Matt Aimonetti wrote: > > Mike is right, if you would send me a patch, I could get it > > fixed faster. > > See https://www.macruby.org/trac/ticket/296 > > -r > -- > http://www.cfcl.com/rdm Rich Morin > http://www.cfcl.com/rdm/resume rdm(a)cfcl.com > http://www.cfcl.com/rdm/weblog +1 650-873-7841 > > Technical editing and writing, programming, and web development > _______________________________________________ > MacRuby-devel mailing list > MacRuby-devel(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >

1 0

[MacRuby] #296: date wrong in two lines of "Talks" section in documentation.html
by MacRuby 15 Jul '09

15 Jul '09

#296: date wrong in two lines of "Talks" section in documentation.html --------------------------+------------------------------------------------- Reporter: rdm@… | Owner: lsansonetti@… Type: defect | Status: new Priority: trivial | Milestone: Component: MacRuby | Keywords: web nit --------------------------+------------------------------------------------- On http://www.macruby.org/documentation.html, all of the entries (under Screencasts, Tutorials, Talks, and Recipes) are listed as being in 2009. At least some of these (eg, the ones in November) should say 2008. -- Ticket URL: <http://www.macruby.org/trac/ticket/296> MacRuby <http://macruby.org/>

1 1