Mikael Høilund
Mikael Høilund
When you call a Function, `self` appears not to be the same as in the declaring scope: ``` snow> Object().object_eval { puts(self.inspect()); { puts(self.inspect()) }() } nil ```
Snow needs a way to check against what version of Snow the code is running. I don't think `SNOW_VERSION: '0.1.5'` is the optimal solution. How about something like `Snow.version: [0,...
`-1.foo()` is parsed as calling foo() on 1, then negating that result. That's not what I'd expect. The same thing happens in the case of floats. Mac OS X 10.5.7,...
If you write an if statement or similar containing a newline, isn considers this a syntax error, even if this is done in a function definition (so isn correctly prompts...
The following lines are all syntax errors. ``` yo! #yo! Object.new().yo! yo!: 60 Object.new().yo!: 60 ``` `#"yo!"` works, though, and [gs]et_member have no qualms using that as the key for...
It's that time again! Here's the segfaulting code (also available at http://gist.github.com/141260): ``` #!/usr/bin/env snow Array.merge_sort: { if .length > 1 // Split. left: @() right: @() midpoint: .length /...
The following, rather simple, script gives unexpected results: ``` MyClass: Object.new() MyClass.object_eval { .new: { instance: Object.new(self) instance.subs: @() instance } .count_it: [level] { puts("${level} Calculating count") wrapper: Object.new() wrapper.count:...
This is useful in the case of `snow some_file.sn`, not so much in the case of `./some_script bla bla`, where some_script has Snow in the shebang line.
Snow needs a way to dynamically refer to the current file, directory, line, and preferably function name (currently problematic). I think **FILE** et al works fine, albeit slightly un-Snowy.
The following happens when trying to use `Function.call_with_self`: ``` snow> {}.call_with_self(@()) Assertion failed: (current != current->m_Previous), function remove, file Handle.cpp, line 73. ``` Stack trace: ``` #0 0x00007fff8288bf16 in __kill...