[Top][All Lists]

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

Re: Multithreading, again and again

From: SAKURAI Masashi
Subject: Re: Multithreading, again and again
Date: Sat, 22 Oct 2011 12:40:39 +0900
User-agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/23.3 Mule/6.0 (HANACHIRUSATO)

Thanks for comments from Nix and Eli!
I will read them and study concurrency in Emacs.

Anyway, I think the single-thread event driven approach is better for
Emacs, like Node.js and other languages do.

Thank you.

At Fri, 21 Oct 2011 16:48:05 +0200,
Eli Zaretskii wrote:
> > From: Nix <address@hidden>
> > Date: Fri, 21 Oct 2011 15:18:07 +0100
> > Cc: address@hidden, address@hidden, address@hidden
> > 
> > 
> > one could consider the 'view' part to be the redisplay engine in
> > xdisp.c and dispnew.c
> You forget the terminal-specific back-ends: xterm.c, w32term.c,
> nsterm.m, term.c, and the *fns.c support functions.
> > dispnew.c (any thoughts on renaming that? It's not that 'new' anymore)
> What would be the purpose of such renaming, except confusing us
> old-timers?  There are many modules in Emacs whose names no longer
> reflect their code correctly -- xdisp.c is neither X only not
> "extended", cmds.c is not the only file with commands, editfns.c is
> not only about editing commands, etc. etc.
> > The only really solid part of this split is that nothing except
> > redisplay draws to the screen
> Also note that in some situations, the "controller" in Emacs directly
> calls the "view", without passing through the "model" and without
> affecting it in any way.  Example: mouse highlight.

SAKURAI, Masashi (family, given)

reply via email to

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