395
edits
Improving Nasal: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
Philosopher (talk | contribs) mNo edit summary |
||
| Line 355: | Line 355: | ||
** Working with it: provide Bytecode class: not started | ** Working with it: provide Bytecode class: not started | ||
* Inspect Context: not started, should be easy. | * Inspect Context: not started, should be easy. | ||
* Expose Tokens to Nasal: implemented by Hooray as argument to compile(). | * Expose Tokens to Nasal: implemented by Hooray as argument to compile(), should be extended to cover output from lex.c and after blocking in addition to the current after-prec-ing (and before freeing!) support. | ||
* Real function name support via assignment: | |||
** Option 1: look at the parse tree and check if the right side of the assignment is a function. If so, go ahead and parse the function with the left side as the "name" of the function instead of falling through to more recursions of genExpr(). | |||
** Option 2: recognize assignment in the VM and if there is a bindToContext event, set the name of the function based upon either the last LOCAL/MEMBER/HINSERT or the combination of them (i.e. complex lvalues like local.fn). This presents some obvious issues, however: | |||
*** The right-hand side of an assignment is done before the left-hand side, thus one would have to look ahead to see the assignment, which is clearly illegal for the VM to do. | |||
*** Or one could look behind to see a naCode constant being pushed, and give some indication to its naFunc that it now has a name. This I still somewhat illegal, but not dangerous and thus could be done. | |||
** Option 3: abandon <tt>var foo = func(){}</tt> for ECMAscript-like function declaration syntax <tt>function foo() {}</tt>. This would not affect the use of anonymous func expressions but would instead be applicable in cases where we want to say "this function is static (i.e. permanent) and should have a name" (as opposed the the case of temporary storage variables for functions). Regardless of the method used, a name member will have to be added to naFunc's and the VM and error handling procedures will have to be changed according. | |||