From 0c6b7a1fa3c4c42f8d9a77a01d58380c2394cd44 Mon Sep 17 00:00:00 2001 From: Luc Teirlinck Date: Thu, 23 Oct 2003 20:47:07 +0000 Subject: [PATCH] (Function Safety): Use inforef instead of pxref for SES. --- lispref/ChangeLog | 8 ++++++++ lispref/functions.texi | 12 ++++++------ 2 files changed, 14 insertions(+), 6 deletions(-) diff --git a/lispref/ChangeLog b/lispref/ChangeLog index 5c2f7398aca..fa271dcf506 100644 --- a/lispref/ChangeLog +++ b/lispref/ChangeLog @@ -1,3 +1,11 @@ +2003-10-23 Luc Teirlinck + + * display.texi (Temporary Displays): Add xref to `Documentation + Tips'. + + * functions.texi (Function Safety): Use inforef instead of pxref + for SES. + 2003-10-23 Andreas Schwab * Makefile.in (TEX, texinputdir): Don't define. diff --git a/lispref/functions.texi b/lispref/functions.texi index 14279d4dab2..4ee101ca871 100644 --- a/lispref/functions.texi +++ b/lispref/functions.texi @@ -1187,12 +1187,12 @@ following the definition, just like macros. @cindex function safety @cindex safety of functions -Some major modes such as SES (@pxref{Top,,,ses}) call functions that -are stored in user files. User files sometimes have poor -pedigrees---you can get a spreadsheet from someone you've just met, or -you can get one through email from someone you've never met. So it is -risky to call a function whose source code is stored in a user file -until you have determined that it is safe. +Some major modes such as SES call functions that are stored in user +files. (@inforef{Top, ,ses}, for more information on SES.) User +files sometimes have poor pedigrees---you can get a spreadsheet from +someone you've just met, or you can get one through email from someone +you've never met. So it is risky to call a function whose source code +is stored in a user file until you have determined that it is safe. @defun unsafep form &optional unsafep-vars Returns @code{nil} if @var{form} is a @dfn{safe} Lisp expression, or -- 2.39.2