Index

Show enters and exits. Hide enters and exits.

01:44:00postmoderni compiled rubinius 1.0.0-rc3, but bin/rbx -v just exits
01:44:43brixenpostmodern: what's your platform
01:44:43evanit doesn't print out the version then exit?
01:44:52postmodernbrixen, gentoo linux amd64
01:45:07brixenneeds to install gentoo
01:45:09postmodernevan, it doesn't seem to respond to any arguments
01:45:21evani'd suggest a rake clean && rake
02:01:06postmodernevan, ah that did the trick
02:01:56postmodernholy cow, im running irb ontop of rubinius
02:02:01postmodernit's really that easy
02:05:10postmodernso i see that MRI is still faster than rubinius for some things
02:05:25postmodernwhich areas is rubinius still lacking in?
02:05:30postmodernor types of operations
02:06:11brixendepends
02:06:24brixentry running your code
02:06:43brixenyou can see tagged specs (ie, ones that do not pass) with bin/mspec tag --list-all
02:07:07brixenbut we can't say how complete rubyspec is, so that's just a guess for "what is missing?"
02:09:39manveruanybody looked at my ticket yet?
02:09:46brixenmanveru: what #?
02:10:17manveruhttp://github.com/evanphx/rubinius/issues#issue/198
02:11:19manverui talked with yui naruse at the tokyo ruby kaigi, he said he's gonna try getting it into MRI
02:11:56brixencool
02:12:08brixenI'll remind evan about it, he needs to make the final decision
02:12:18manveruthanks
02:12:27brixenn/p, thanks for making the patch
02:12:56manverunow i just need 1.9 syntax :)
02:13:11brixencoming soon!
02:13:24manveruanything i can help with?
02:13:49brixenbasic approach, diff 1.8 and 1.9 MRI grammar
02:14:03brixenmanually apply that to rbx grammar.y in the one_nine branch
02:14:05manveruwhere is all the 1.9 stuff?
02:14:10manveruoh
02:14:25brixenthen fix the compiler
02:14:41brixenand the VM where it needs to understand different arg semantics
02:20:43brixenmanveru: what 1.9 syntax do you use?
02:20:56manveruhmm
02:21:02brixenI personally find this horrible: ruby1.9 -v -e 'def foo(a) p a end; foo a: :b, c: :d'
02:21:14manverumissing end?
02:21:29brixena: :b <- my eyes see this and stumble all over themselves
02:21:36manverulol
02:21:44manverui cannot stand => anymore
02:21:57brixenwhat is missing end?
02:22:10manveruoh, nm
02:22:15brixen:a => :b is much better than a: :b IMO
02:22:27brixenwhat is an a: in ruby? nothing
02:22:28manverui even patched pretty inspect to output : when suitable
02:22:32brixenwhat is an :a, a symbol
02:22:43brixenhorrid I say
02:22:51brixenwhere can you use a: ?
02:23:01manverulol
02:23:10brixenseriously, it's really bad
02:23:10manveruyou probably don't use -> either
02:23:28brixencognitively you have to maintain this concept for "symbol in a method call"
02:23:28manveruor def foo(*a, b)
02:23:34brixenthat looks nothing like a symbol
02:23:40brixenthat's cognitive load for nothing
02:23:44brixenno gain all pain
02:24:05manveruit's easier to write
02:24:09manveruit reads nicer
02:24:11brixenbah
02:24:13brixenno
02:24:17manverui find it very useful
02:24:32brixenthat's like: def foo(a) ... end; oof(1)
02:24:38brixena: is just plain backwards
02:24:54brixen:a => :b .... ooh soo hard to type :'(
02:24:58brixenhaha
02:25:09manveruso you stare at %() for half an hour to figure out that it's a string?
02:25:21manveruand, omg, %r() might be a regex
02:25:24brixenno, it's an interpolated string
02:25:41brixenI would stare at (blah)% for quite a while though
02:25:56brixenespecially if it were (blah)% %foo
02:26:19brixen%r is a regexp, btw, no might about it
02:26:20manveruhttp://github.com/manveru/ver/blob/refactor/lib/ver/buffer.rb#L11-45
02:26:48brixenthat's not any more clear to me than =>
02:27:06manverui don't say it's "more" clear
02:27:09brixenthe : following the identifier is a special concept in a call or hash that isn't anywhere else
02:27:12brixenI dislike it
02:27:30manveruok
02:28:02manveruanw, i use it :)
02:28:11brixenand I won't :)
02:28:19brixenwhat else do you use from 1.9?
02:28:50brixenbtw, you should ask github to add syntax highlighting for foo: :
02:28:53manveruhttp://github.com/manveru/ffi-tk/blob/master/lib/ffi-tk/widget/text.rb#L198
02:28:53brixener :)
02:29:23brixenok, 1.9 arg passing
02:29:29brixenanything else?
02:29:40manverustabby proc?
02:29:45brixenok
02:29:47manverubut not in any library code
02:29:52brixenall the really ugly stuff, great :P
02:29:54brixenhahah
02:29:57manveruthat's just for my personal amusement :)
02:30:01brixenheh
02:30:21brixenwell, the big thing with one_nine atm is that we need to merge in the recent changes from master
02:30:21manverufoo a: ->{ bar}, b: ->{ duh }
02:30:29brixensince we're still fixing a lot of bugs
02:30:38manveruyeah
02:30:41brixenthe only advantage you will have on rbx from 1.9 is the syntax
02:30:55brixenwe will have all the speed and goodness on 1.8
02:30:59brixenthe same as 1.9
02:31:07manverubut it's like 13k LoC
02:31:17manverui really don't wanna translate all that
02:31:29brixenwhat is 13kloc?
02:31:34manveruffi-tk/ver
02:31:38brixenoh yeah
02:31:47manveruand i use lots of encoding stuff
02:31:50brixenwell, just saying, we are close to getting 1.9 support
02:31:57brixenthat's the huge thing, encoding stuff
02:32:10manveruyeah
02:32:19brixenbut that doesn't require syntax support
02:32:20manverua huge part of the old ruby-tk was about encoding
02:32:31brixenevan already hacked in magic comments iirc
02:32:39manverunice :)
02:33:41manveruok...
02:33:52manveruso you plan to do encoding in ruby too?
02:34:25manverui really have no idea how most of it works...
02:34:39brixengit show d0f736008
02:35:07brixenencoding support will mostly be figuring out how to back String and making the methods aware of that
02:35:38brixenone idea is to add a CharArray that uses a different immediate type rather than a ByteArray (which uses bytes)
02:35:48manveruyeah
02:36:14manveruyou said that before... but that part is in C, so i can't really help you there
02:37:30manveruif we cover ascii and utf-8 first, we'll be running like 99% of apps out there without problems
02:37:43manveruwell, and binary, but that's the current string already
02:38:16brixencool
02:38:50brixenwe could also just build it on ByteArray
02:39:20brixenperhaps make ByteArray encoding aware, so you could index by characters instead of bytes
02:39:25brixenthat would be mostly in Ruby :)
02:40:14brixenmost of String methods should just be agnostic (ie do things with "characters")
02:40:44evanpostmodern: --enable-llvm is redundent, it's the default.
02:40:49evanok, shower time.
05:14:01manveruthinking of giving Module#prepend implementation a try...