<e_dub>
adambeynon_, was running "rake dist" to build opal.js and opal-parser.js and it kept dying on me with "Broken pipe" but finally found it. It was dying because i didnt have uglifyjs installed. For some reason your rescue clause wasnt working and I didn't get the much more helpful error message there. It was only looking at the source that allowed me to find that and install uglify and get it building
<e_dub>
just thought i would mention
fkchang has quit [Ping timeout: 252 seconds]
barry_ has quit [Remote host closed the connection]
barry_ has joined #opal
barry_ has quit [Ping timeout: 272 seconds]
Liothen has quit [Remote host closed the connection]
Liothen has joined #opal
fkchang has joined #opal
barry_ has joined #opal
barry_ has quit [Ping timeout: 260 seconds]
unbracketed has joined #opal
<meh`>
fkchang, now the css block is aware of the component element class/id
<meh`>
adambeynon_, can opal-parser.js be included before opal.js?
<adambeynon_>
meh`: nope. The parser relies on the runtime
<adambeynon_>
meh`: why do you need the parser first?
<meh`>
adambeynon_, I don't like having opal-parser.rb in the stdlib
<meh`>
if opal-parser was requirable before opal I could do a check to define the eval and whatnot
<meh`>
I'm gonna add the opal-parser stuff in the corelib, and do a check on the eval
<meh`>
I'll keep it in its own file
<meh`>
so you can avoid requiring it in mopal
<adambeynon_>
meh`: wait, I don't follow
<elia>
me neither
<meh`>
adambeynon_, I want eval and various string evals to be available as soon as you add opal-parser.js
<adambeynon_>
meh`: they are now
<adambeynon_>
Well, eval is
<meh`>
don't you need to require opal-parser from the stdlib?
<meh`>
or is it included in the compilation?
<adambeynon_>
Yes. If the parser isn't added then all the eval methods should just work with blocks
<adambeynon_>
Then opal-parser redefines the methods with string support
<meh`>
adambeynon_, that's what I mean, I want the checks to be at runtime rather than having to include it by hand
<adambeynon_>
It's worth noting that the compiler doesn't currently support eval a string of code on a given object, it always evals on top level object
<adambeynon_>
I.e. Instance_eval can't currently work without fixing compiler
<meh`>
adambeynon_, for instance_eval
<meh`>
won't a proc { #{string} } work?
<meh`>
it returns the proc
<meh`>
so it's doable (testing with opal -c)
<meh`>
what I'm trying to convey is, I don't like core things to be separated, I'd rather have a runtime check if opal-parser has been required than having to require 'opal-parser'
<adambeynon_>
I still don't follow. Either way, you still have to manually require opal-parser before you can eval code
<travis-ci>
[travis-ci] opal/opal#1669 (master - 7451fb5 : Adam Beynon): The build passed.
travis-ci has left #opal [#opal]
dfranciosi has quit [Remote host closed the connection]
<meh`>
adambeynon_, ping
<adambeynon_>
meh`: hi
<meh`>
adambeynon_, I'm getting an error requiring opal-parser
<meh`>
Could not find asset: racc/parser.rb
<adambeynon_>
meh`: what's your setup? Sprockets?
<meh`>
adambeynon_, opal -e or opal-repl
<adambeynon_>
meh`: ah. They still use Builder, which is going to be removed very soon. I think it struggles because the parser requires racc with an extension
<meh`>
anything I can do?
e_dub has quit [Ping timeout: 245 seconds]
<adambeynon_>
meh`: well, Builder is going to go. I keep meaning to rewrite the repl using sprockets
<adambeynon_>
or just delegate it to opal-node
<meh`>
any other way I can test my changes?
e_dub has joined #opal
<adambeynon_>
well, the specs go through sprockets, so if there are testable changes, you could add specs for them
<adambeynon_>
meh`: what have you changed?
<adambeynon_>
instance_eval ?
<meh`>
yes
<meh`>
and module_eval
<adambeynon_>
some specs should do the trick
<adambeynon_>
the specs already use opal-parser
<adambeynon_>
so if they all pass then its safe to assume the parser still works
ryanstout has joined #opal
<meh`>
I still feel like eval is a better name
<meh`>
it's all *eval
<meh`>
I'll open a discussion pull reuqest
<meh`>
or opal/eval even
<meh`>
adambeynon_, anything against opal/eval.rb?
<adambeynon_>
meh`: I prefer just keeping it as opal-parser
<meh`>
adambeynon_, but -parser means absolutely nothing
<meh`>
what have Kernel#eval, Module#module_eval and BasicObject#instance_eval to do with a parser?
<adambeynon_>
it does match the resulting filename better: opal-parser.js
<meh`>
the resulting file name is going to change with it
<meh`>
adambeynon_, seriously, if you didn't know what opal-parser were, would you understand what it's for?
<meh`>
and even in the bundler world a-b means a/b