1berry/cpython
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Hyphenate "built-in" for consistency.

Browse Source
This commit is contained in:
Fred Drake 1998-04-02 19:36:25 +00:00
parent 5204b4a984
commit 3a18f3ba38
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Doc/lib/libprofile.tex
View File

@ -520,7 +520,7 @@ There are two fundamental limitations on this profiler. The first is
that it relies on the Python interpreter to dispatch \dfn{call}, that it relies on the Python interpreter to dispatch \dfn{call},
\dfn{return}, and \dfn{exception} events. Compiled \C{} code does not \dfn{return}, and \dfn{exception} events. Compiled \C{} code does not
get interpreted, and hence is ``invisible'' to the profiler. All time get interpreted, and hence is ``invisible'' to the profiler. All time
spent in \C{} code (including builtin functions) will be charged to the spent in \C{} code (including built-in functions) will be charged to the
Python function that invoked the \C{} code. If the \C{} code calls out Python function that invoked the \C{} code. If the \C{} code calls out
to some native Python code, then those calls will be profiled to some native Python code, then those calls will be profiled
properly. properly.

2
Doc/libprofile.tex
View File

@ -520,7 +520,7 @@ There are two fundamental limitations on this profiler. The first is
that it relies on the Python interpreter to dispatch \dfn{call}, that it relies on the Python interpreter to dispatch \dfn{call},
\dfn{return}, and \dfn{exception} events. Compiled \C{} code does not \dfn{return}, and \dfn{exception} events. Compiled \C{} code does not
get interpreted, and hence is ``invisible'' to the profiler. All time get interpreted, and hence is ``invisible'' to the profiler. All time
spent in \C{} code (including builtin functions) will be charged to the spent in \C{} code (including built-in functions) will be charged to the
Python function that invoked the \C{} code. If the \C{} code calls out Python function that invoked the \C{} code. If the \C{} code calls out
to some native Python code, then those calls will be profiled to some native Python code, then those calls will be profiled
properly. properly.