[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Unicode Lisp reader escapes

From: Kenichi Handa
Subject: Re: [PATCH] Unicode Lisp reader escapes
Date: Tue, 09 May 2006 09:36:34 +0900
User-agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI)

In article <address@hidden>, Stefan Monnier <address@hidden> writes:

>> For instance, Fread is called from Fcall_interactively as
>> below:

>> Lisp_Object tem;
>> [...]
>> tem = Fread_from_minibuffer (build_string (callint_message),
>> Qnil, Qnil, Qnil, Qnil, Qnil,
>> Qnil, Qnil);
>> if (! STRINGP (tem) || SCHARS (tem) == 0)
>> args[i] = Qnil;
>> else
>> args[i] = Fread (tem);

>> In the calling sequence of
>> Fread-> read_internal_start->read0->read1, I see no place
>> where the original `tem' is GCPROed.  Do I overlook
>> something?

> Why would it need to be protected? it's not used afterwards.

It's not used in Fcall_interactively afterwards.  So
Fcall_interactively doesn't have to protect it.  But, read1
or read_escape have to protect the argument READCHARFUN,
don't they?

Kenichi Handa

reply via email to

[Prev in Thread] Current Thread [Next in Thread]