2026/04/18
Jump to navigation
Jump to search
|
Saturday, April 18, 2026 (#108)
|
|
References |
transcribed retroactively from a Signal chat
- 16:07 I think I might have figured out a CLI way to do step-through debugging... crude, even if it works, but perhaps sufficient.
- 16:28 YES. Shows location of current execution line, then waits for ENTER.
- 16:29 I should be able to have it give me a lot more information than that; the trick is how to do it in a minimally-hard-coded kind of way...
- 16:58 The trick, I think, is how to get the value of local variables from the execution context. Maybe the Reflection classes can do that...
- 17:34 I don't see any obvious way to do it. There's also the possibility that if I run phpdbg from the command line, it might give me that information -- but the docs don't really make it clear.
- 17:37 Kinda annoying that the Reflection classes will go from {code entity} to {filespec and line#}, but there's no way (as far as I can tell) to get any information about what's in a particular file, much less by line #.
- 17:51 ...and phpdbg seems to execute in a web context (not CLI), and I don't see how to change that except by forcing it in code (which still leaves CLI arguments inaccessible).
- 17:52 You can watch a variable in phpdbg-the-app, but there's no equivalent function in the library.