meh` changed the topic of #opal to: http://opalrb.org - Ruby runtime and library on top of Javascript | 1.0.0 is near | This channel is logged at https://botbot.me/freenode/opal/
e_dub has joined #opal
skofo has quit [Ping timeout: 240 seconds]
mieko has quit [Ping timeout: 240 seconds]
skofo has joined #opal
boberetezeke has joined #opal
[o__o] has left #opal [#opal]
[o__o] has joined #opal
[o__o] has left #opal [#opal]
[o__o] has joined #opal
[o__o] has left #opal [#opal]
[o__o] has joined #opal
ryanstout has quit [Quit: ryanstout]
boberetezeke has quit [Ping timeout: 245 seconds]
skofo has quit [Quit: Leaving]
dimaursu16 has joined #opal
ch007m has joined #opal
elia has joined #opal
tils has joined #opal
ch007m has quit [Read error: Connection reset by peer]
ch007m has joined #opal
dfranciosi has joined #opal
kludge` has quit [Ping timeout: 255 seconds]
kludge` has joined #opal
dfranciosi has quit [Remote host closed the connection]
dfranciosi has joined #opal
dfranciosi has quit [Remote host closed the connection]
dfranciosi has joined #opal
fkchang has joined #opal
boberetezeke has joined #opal
fkchang has quit [Read error: Connection reset by peer]
fkchang has joined #opal
dimaursu16 has quit [Ping timeout: 245 seconds]
skofo has joined #opal
dimaursu16 has joined #opal
ch007m has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
ryanstout has joined #opal
mieko has joined #opal
elia has quit [Ping timeout: 264 seconds]
mieko has quit [Ping timeout: 240 seconds]
dfranciosi has quit [Remote host closed the connection]
dfranciosi has joined #opal
skofo has quit [Ping timeout: 255 seconds]
boberetezeke has quit [Quit: boberetezeke]
dfrancio_ has joined #opal
dfranciosi has quit [*.net *.split]
boberetezeke has joined #opal
DrShoggoth has joined #opal
dfrancio_ has quit [Remote host closed the connection]
dfranciosi has joined #opal
e_dub has quit [Read error: Connection reset by peer]
e_dub has joined #opal
dfranciosi has quit [Remote host closed the connection]
dfranciosi has joined #opal
mieko has joined #opal
boberetezeke has quit [Ping timeout: 255 seconds]
<mieko> meh`: I was looking at https://github.com/opal/opal/issues/476 and your Numeric work: the comment I left there is the same issue at play, right?
boberetezeke has joined #opal
e_dub has quit [Ping timeout: 240 seconds]
e_dub has joined #opal
boberetezeke has quit [Ping timeout: 255 seconds]
fkchang has quit [Read error: Operation timed out]
<ryanstout> is .hash implemented in opal?
boberetezeke has joined #opal
boberetezeke has quit [Ping timeout: 240 seconds]
<adambeynon> mieko: hi. yeah, Exception subclasses dont get called properly, just like Numeric
<adambeynon> I need to work on fixing it
<adambeynon> it is feasible though - just need to find the time to fix it
<adambeynon> ryanstout: Hash doesnt use it (currently)
<ryanstout> ok
<ryanstout> thanks
<mieko> adambeynon: Thanks. Playing with it, it wasn't obvious to me what made Exception special where the .new or #initialize strategies of other bridged classes aren't effective.
<adambeynon> mieko: the reason Exception is so hacky for #new is that subclassing Error.prototype in javascript doesnt automatically allow you to get stacktraces on these subclasses instances
<adambeynon> different browsers need different tricks to get stacktracing to work properly
<mieko> Ah, got ya.
<adambeynon> chrome is actually the most strange
<ryanstout> adambeynon: if you need help on getting stacktraces, I built exceptionhub.com a while ago, so I know the depths of how to get stacktraces in browsers. :-)
<adambeynon> it needs every Error instance to have this inside a constructor: Error.captureStackTrace(this, MyError);
<adambeynon> ryanstout: I will definitely ping you in the next few weeks then ;)
<ryanstout> adambeynon: sounds good :-)
elia has joined #opal
<mieko> ryanstout: Re: exceptionhub.com; cool idea there.
<ryanstout> mieko: thanks. Its somewhat out of date now. It let you drop in a line of JS and track back client side exceptions+stack traces to the app (and it worked in all browsers, before onerror was in webkit :-)
<mieko> The shit I had to go through to track JS exceptions Android 2.3 browser would've made that awesome to know about.
<ryanstout> yea, I think it works on Androd 2.3, but its been a while, so I’m not 100% sure
<mieko> The devices I had my hands on when the reports came in didn't have a developer mode where I could get a console. Ended up having to setup the Android SDK to see a JS exception trace.
e_dub has quit [Read error: Connection reset by peer]
e_dub has joined #opal
DrShoggoth has quit [Quit: Leaving]
elia has quit [Quit: Computer has gone to sleep.]