Mike Magruder
0d14e585fd
In general, a test which gets its input piped in is not really interacting with a terminal like it normally would. Thus, letting it think it has the same terminal as the environment is incorrect. More specifically, hphpd uses Readline, which inspects the TERM env var and based on that and a stunning array of other options will attempt to initialize the terminal with extra control characters on first use. It would be tough to try to control for all of the different options and ensure they're all the same, and honestly testing Readline is not the objective of our tests anyway. Thus, I'm forcing TERM to 'dumb' when a test has input to ensure a) a simple terminal which requires no control characters and b) consistency no matter what environment is present when the tests are run.
20 linhas
522 B
Plaintext
20 linhas
522 B
Plaintext
Program %s/break4.php loaded. Type '[r]un' or '[c]ontinue' to go.
|
|
break :fb:my:thing::doIt()
|
|
Breakpoint 1 set upon entering xhp_fb__my__thing::doIt()
|
|
But wont break until class xhp_fb__my__thing has been loaded.
|
|
continue
|
|
break4.php loaded
|
|
Program %s/break4.php exited normally.
|
|
@ :fb:my:thing::doIt()
|
|
Breakpoint 1 reached at xhp_fb__my__thing::doIt() on line 8 of %s/break4.php
|
|
7 function doIt() {
|
|
8 echo "doing my thing\n";
|
|
9 }
|
|
|
|
break clear all
|
|
All breakpoints are cleared.
|
|
continue
|
|
doing my thing
|
|
|
|
quit
|