Options passed by argument, no global 'options'

19 views
Skip to first unread message

johnjbarton johnjbarton

unread,
Jan 26, 2015, 8:55:44 PM1/26/15
to traceur-comp...@googlegroups.com
From a time long ago we had a global options object to set the compiler options, eg which features would be enabled. 
When we got modules to work we passed the global as a module property.
 As we got to more complex usage scenarios we started having functions that took options as arguments. 

Well, the combination wasn't easy to understand so now we removed the global option and the module-property option, leaving only options passed by argument. 

Let me know if something is no longer possible. I'm guessing that browsers that load traceur and use our script tag processing may have an issue but rather than guess I'd like to see a specific report.

jjb

Si

unread,
Feb 13, 2015, 5:40:12 PM2/13/15
to traceur-comp...@googlegroups.com

Hi John,

Would this explain the problem I'm having enabling experimental features, described here https://groups.google.com/forum/#!topic/traceur-compiler-discuss/7HT3t9rrQkw  ?

If so, how/where should I pass the desired options as an argument when doing in-browser on-the-fly compilation as shown in the example here: 

Thanks - Si
Reply all
Reply to author
Forward
0 new messages