feat: support implicit evaluation #46

Merged
aleclarson merged 1 commit from implicit-eval into master 2018-04-28 04:44:31 +02:00
aleclarson commented 2018-04-28 04:36:13 +02:00 (Migrated from github.com)

Evaluate statements and print expressions without using the 'e' or 'p' commands.
To avoid cognitive stress, one-letter variables require the 'p' command to view.
But assigning to one-letter variables does not require the 'e' command. :)

Also included:

  • default to "h" for empty commands when no previous command exists
  • avoid overwriting previous command for specific commands not worth repeating
  • avoid overwriting previous command with an invalid command
  • avoid overwriting previous command with an implicit evaluation
Evaluate statements and print expressions without using the 'e' or 'p' commands. To avoid cognitive stress, one-letter variables require the 'p' command to view. But assigning to one-letter variables does *not* require the 'e' command. :) Also included: - default to "h" for empty commands when no previous command exists - avoid overwriting previous command for specific commands not worth repeating - avoid overwriting previous command with an invalid command - avoid overwriting previous command with an implicit evaluation
aleclarson commented 2018-04-28 04:37:19 +02:00 (Migrated from github.com)

@slembcke With this change, is the explicit e command even necessary? :)

Edit: nevermind, answered my own question. the explicit eval can be used to overwrite the previous command, which lets you repeat the evaluation by using an empty command immediately afterwards. Implicit evals are not repeatable, so you can do a quick evaluation and continue stepping with maximum efficiency!

@slembcke With this change, is the explicit `e` command even necessary? :) **Edit:** nevermind, answered my own question. the explicit eval can be used to overwrite the previous command, which lets you repeat the evaluation by using an empty command immediately afterwards. Implicit evals are not repeatable, so you can do a quick evaluation and continue stepping with maximum efficiency!
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
slembcke/debugger.lua!46
No description provided.