- Nov 25, 2015
-
-
Thomas Wood authored
-
Thomas Wood authored
-
Thomas Wood authored
This reverts commit 0f46d81bbb28ea4706d6f3a4e1ce5f69684cf4da.
-
Thomas Wood authored
This reverts commit 33f5d61a65b5bef23ae85254393833c62f6f6215.
-
Thomas Wood authored
-
- Oct 14, 2015
-
-
Cesar Roux Dit Buisson authored
-
Cesar Roux Dit Buisson authored
-
Cesar Roux Dit Buisson authored
-
- Oct 09, 2015
-
-
Cesar Roux Dit Buisson authored
-
- Oct 04, 2015
-
-
Cesar Roux Dit Buisson authored
Return wrap and proper exit for switch statement type functions. Also remove no longer used old wrap functions.
-
Cesar Roux Dit Buisson authored
-
- Oct 03, 2015
-
-
Cesar Roux Dit Buisson authored
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.
-
- Oct 02, 2015
-
-
Thomas Wood authored
-
- Oct 01, 2015
-
-
Cesar Roux Dit Buisson authored
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.
-
Cesar Roux Dit Buisson authored
-
Thomas Wood authored
-
Thomas Wood authored
-
Thomas Wood authored
-
Thomas Wood authored
-
Thomas Wood authored
-
Thomas Wood authored
-
Thomas Wood authored
-
Cesar Roux Dit Buisson authored
-
Thomas Wood authored
-
Thomas Wood authored
-
Thomas Wood authored
-
Alan Schmitt authored
-
- Sep 30, 2015
-
-
Cesar Roux Dit Buisson authored
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.
-
Cesar Roux Dit Buisson authored
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.
-
- Sep 29, 2015
-
-
Cesar Roux Dit Buisson authored
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.
-
Cesar Roux Dit Buisson authored
Pre step before function calls get wrapped.
-
- Sep 28, 2015
-
-
Thomas Wood authored
-
Thomas Wood authored
-
Thomas Wood authored
-
Thomas Wood authored
-
Thomas Wood authored
-
Thomas Wood authored
Combined module compilation and linking was not fully correct, modules would only be output when opened, but not referenced. All output now wrapped in the appropriate module object. Still todo is a process of linking the dependencies together and addition of module or file name to the logged output.
-
- Sep 25, 2015
-
-
Cesar Roux Dit Buisson authored
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.
-
- Sep 24, 2015
-
-
Cesar Roux Dit Buisson authored
Remebered ctx creation also needs to be added after each function entry, so .log.js versions not currently working with interpreter example.
-
Cesar Roux Dit Buisson authored
-