>
LispWorks IDE User Guide>
24 The Profiler 24.7 Profiling pitfallsIt is generally only worth profiling code which has been compiled. If you profile interpreted code, the interpreter itself is profiled, and this skews the results for the actual Lisp program.
Macros cannot be profiled because they are expanded during the compilation process.
24.7.1 Effects of random sampling 24.7.2 Recursive functions 24.7.3 Structure accessors 24.7.4 Consequences of restricted profiling 24.7.5 Effect of compiler optimizations 24.7.6 Effect of compiler transformsLispWorks IDE User Guide (Windows version) - 25 Nov 2011
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4