<GitHub195>
rubinius/ffi-io 3a5b7be Chuck Remes: remove some commented out and dead code
GitHub195 has left #rubinius [#rubinius]
_whitelogger__ has joined #rubinius
<cremes>
didn’t make very good coding progress on the ffi-io branch the last few days, but my understanding of rubinius’ bootstrapping process has grown immensely.
<cremes>
that was a necessary step for what i want to do next anyway.
<cremes>
i’m going to push hard this weekend to have everything cleaned up and in a usable state.
<cremes>
once the current code is clean, i’ll start poking at the mmap logic for file i/o. promises to be fun.
halorgium_ has joined #rubinius
max96at has quit [*.net *.split]
halorgium has quit [*.net *.split]
_whitelogger_ has quit [*.net *.split]
halorgium_ is now known as halorgium
max96at_ is now known as max96at
GitHub29 has joined #rubinius
<GitHub29>
[rubinius] chuckremes pushed 2 new commits to ffi-io: http://git.io/FWMs
<GitHub29>
rubinius/ffi-io 1c6b39f Chuck Remes: mark rubinius as non-compliant for buffering writes; impl detail anyway
<GitHub29>
rubinius/ffi-io 6565d19 Chuck Remes: include sync as part of fields to move to new IO obj
GitHub29 has left #rubinius [#rubinius]
elia has quit [Quit: Computer has gone to sleep.]
pietr0 has joined #rubinius
slaught has quit [Quit: slaught]
<brixen>
cremes: awesome
<brixen>
cremes: all that new knowledge will be a great use in authoring the rubinius book section on bootstrapping :)
<cremes>
haha, yes. happy to help.
slaught has joined #rubinius
djellemah has joined #rubinius
nirvdrum has joined #rubinius
havenwood has quit []
max96at is now known as max96at|off
sferik has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<cremes>
maybe since rbx isn’t chasing perfect MRI compatibility anymore we can be more sane about this.
<|jemc|>
@cremes in myco, I flipped the stack traces rightside up again - it's great :D
<cremes>
|jemc|: you are a gentleman and a scholar. i salute you!
<|jemc|>
also, I hate hate hate the rbx stack trace printer right now
<|jemc|>
the so-called "awesome_backtrace"
<|jemc|>
I can't copy paths from it
<cremes>
i think you can turn that awesomeness off… check the cli switches
<|jemc|>
yeah in most of my projects I end up looking at project-styled backtraces and rspec-styled backtraces anyway, so it's not a huge deal - it just pops up in 'bare' projects
<|jemc|>
the visual aesthetics of the awesome_backtrace aren't too far off - but I really need copy-ability when debugging
<yorickpeterse>
oh yeah, the backtrace pisses me off
<yorickpeterse>
I tried hacking it at some point to fix the wrapping at least
<yorickpeterse>
but I gave up, don't think I have the branch around either
nirvdrum_ has joined #rubinius
bakkdoor has quit [Ping timeout: 245 seconds]
bakkdoor has joined #rubinius
nirvdrum__ has quit [Ping timeout: 240 seconds]
DireFog has quit [Remote host closed the connection]
DireFog has joined #rubinius
nirvdrum_ is now known as nirvdrum
<brixen>
|jemc|: totally fixing that soon
<brixen>
in Console, I want interaction to give you only the problem and the first line, hit <Enter> and get more context, etc
diegoviola has quit [Read error: Connection reset by peer]
<brixen>
I'm totally open to improving Console, terminal, etc UX on backtraces
<brixen>
gotta run
diegoviola has joined #rubinius
GitHub76 has joined #rubinius
<GitHub76>
[rubinius] sshao pushed 1 new commit to master: http://git.io/FlaN
<GitHub76>
rubinius/master 4ae051b sshao: Fixed HAMT Hash#select to work on frozen hashes
GitHub76 has left #rubinius [#rubinius]
<brixen>
|jemc|: yay, no more invalid reads in valgrind :)
<brixen>
looking at this uninitialized read and then revisiting joining system threads to see if I can eliminate that hang that's been showing up in the spec runs recently
* brixen
really runs now
sferik has joined #rubinius
Bwild has joined #rubinius
GitHub127 has joined #rubinius
<GitHub127>
[rubinius] sshao pushed 1 new commit to 1.8.7: http://git.io/FlPG
<GitHub127>
rubinius/1.8.7 a26e1fa sshao: Fixed HAMT Hash#select to work on frozen hashes...