rfc:error-optimizations
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:error-optimizations [2010/08/24 03:37] – kalle | rfc:error-optimizations [2011/04/06 10:59] – external edit 127.0.0.1 | ||
---|---|---|---|
Line 74: | Line 74: | ||
<code c> | <code c> | ||
if (EG(error_stack_enabled) && EG(error_stack_size)) { | if (EG(error_stack_enabled) && EG(error_stack_size)) { | ||
- | char *error; | + | char *error |
+ | int error_length; | ||
/* dispatch to formatting function, and copy it into, the " | /* dispatch to formatting function, and copy it into, the " | ||
+ | /* NOTE: This is just a pseudo function name for formatting */ | ||
+ | zend_format_error_arguments(& | ||
- | | + | |
} else { | } else { | ||
/* BC code */ | /* BC code */ | ||
Line 94: | Line 97: | ||
Obvious the memory usage here can grow quite rapidly, but people who would use this feature already takes great care of their code to not assume the opposite. | Obvious the memory usage here can grow quite rapidly, but people who would use this feature already takes great care of their code to not assume the opposite. | ||
- | ===== Additional notes ===== | + | ==== ZTS performance |
- | * While altering | + | Since the error stack is hooked into the executor globals, which requires tsrm_ls |
rfc/error-optimizations.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1