Return wrap and proper exit for switch statement type functions.
Also remove no longer used old wrap functions.

Cleaner enter and exit inside of function definition instead of around function calls. Needs exits before all returns by pulling out return value to other variable.
Context created on entry to a function. This mode of singly named context is incorrect (Discussed with Arthur) and will need changing eventually.

Correctly wraps function calls (that use brackets after the function name), and does so recursively.
Next step is infix.
Multiple calls to same function (ie a(b(), b()) type call) may not be handled properly, may be dependant of ordering of tokens.

First step is using new format (list of tokens in one line).
Very difficult: Keep information as to where on line insertion is happening, and keep all other tokens informed when string is modified/position of insertion changes due to larger string.

This changes format of tokens, so that more than one can appear in a line. Not moved into working code yet. Sort of a precommit.

Currently doesn't recognize context, and assumes it is in a return. ALso lops off anything that might have surrounded the call:
-logging of variables, which triggered on the line after, is ignored
-for similar reason, only one function on a line is "logged" and the other wiped.

The current log format in OCaml is incapable of detecting more than one log event on a line.

Pre step before function calls get wrapped.

The method of hooking on to previously marked log elements causes issues and unmarked entry points. I need to redo this properly from js_of_ast with marking of returns to log directly.

Remebered ctx creation also needs to be added after each function entry, so .log.js versions not currently working with interpreter example.

We don't actually make use of the env at all in the recursive js_of_ast
function. It's also present as part of the tree structure we're
recursing over, so completely superfluous anyway.

Oddly enough, field accesses weren't in scope. They're most definitely
required.

We can rely on the OCaml type system for consistency of type correctness
when we have a nameclash between modules (hopefully)

Unfortunately pretty formatting and indentation doesn't work correctly, though this doesn't stop it from working.

Still needs a polish in order to detect:
-Not an actual return line
-return line does not call function
-Proper padding and indentation (I gave up after trying 3 hours)

Manual rewrite of the log_source to see how to implement better logging generation. Beginning of function calls will report correct variable being analyzed. There seems to be something missing when calling another function, and still nothing in the top right box.