emacs-devel
[Top][All Lists]
Advanced

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

Re: Carbon port and multi-tty


From: YAMAMOTO Mitsuharu
Subject: Re: Carbon port and multi-tty
Date: Thu, 08 May 2008 10:25:31 +0900
User-agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (Shijō) APEL/10.6 Emacs/23.0.50 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)

>>>>> On Wed, 07 May 2008 18:03:40 -0700, Dan Nicolaescu <address@hidden> said:

>> Again, I'm saying about mixing unrelated changes, not this
>> particular single-line bug.  Please don't understate the problem.

> You keep repeating the same thing over and over.  We heard you the
> first time, and nobody agreed.

Maybe.  Of course I can't force you not to mix the unrelated changes.
I just hope that doesn't happen again.

Let's go to non-waste part.

>> And about this ChangeLog entry:
>> 
>> 2008-05-07 Dan Nicolaescu <address@hidden>
>> 
>> * macfns.c (Fx_create_frame): Make a copy of frame parameters
>> because the original parameters are in pure storage now.
>> 
>> The primary purpose of the copying is not for the parameters
>> allocated in the pure storage, but to prepare for frame parameter
>> clearing in x_get_arg.

> This is the same ChangeLog used by Martin Rudalics to fix a similar
> problem that was discovered by Juanma Barranquero that manifested
> itself by trying to write to pure storage.

It was I who found the cause of this problem.
http://lists.gnu.org/archive/html/emacs-devel/2007-12/msg01069.html

And for the W32 port, it is true that the only purpose of the copying
is to avoid writing to the pure storage.  But notice that some part of
the x_get_arg code I showed in the previous mail was enclosed with
"#ifndef WINDOWSNT", and the copying code in xfns.c and macfns.c had
existed before some frame parameter got allocated in the pure storage.

So, the primary purpose of copying is different between W32 and
X11/Mac.

                                     YAMAMOTO Mitsuharu
                                address@hidden




reply via email to

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