From 3a18f3ba38a817c17d11534a1681f3345df9e70f Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Thu, 2 Apr 1998 19:36:25 +0000 Subject: [PATCH] Hyphenate "built-in" for consistency. --- Doc/lib/libprofile.tex | 2 +- Doc/libprofile.tex | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/lib/libprofile.tex b/Doc/lib/libprofile.tex index b7a1c1e924..debb332940 100644 --- a/Doc/lib/libprofile.tex +++ b/Doc/lib/libprofile.tex @@ -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}, \dfn{return}, and \dfn{exception} events. Compiled \C{} code does not 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 to some native Python code, then those calls will be profiled properly. diff --git a/Doc/libprofile.tex b/Doc/libprofile.tex index b7a1c1e924..debb332940 100644 --- a/Doc/libprofile.tex +++ b/Doc/libprofile.tex @@ -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}, \dfn{return}, and \dfn{exception} events. Compiled \C{} code does not 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 to some native Python code, then those calls will be profiled properly. -- 2.50.0