unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Davin Pearson <davin.pearson@gmail.com>
To: Davin Pearson <davin.pearson@gmail.com>, emacs-devel@gnu.org
Subject: Re: A completely pre-emptive time sharing system for GNU Emacs
Date: Sun, 10 Feb 2019 03:47:04 +1300	[thread overview]
Message-ID: <CAG9ihEsKAOyJinoMPiKYVfi4S__J7W-z-AhfvZOa6GG2MvV3hQ@mail.gmail.com> (raw)
In-Reply-To: <m28sytfnjb.fsf@newartisans.com>

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

On Wed, 6 Feb 2019 at 19:18, John Wiegley <johnw@gnu.org> wrote:

> >>>>> "DP" == Davin Pearson <davin.pearson@gmail.com> writes:
>
> DP> I am about to write a completely pre-emptive time-sharing system but
> first
> DP> I need to know if I will be re-inventing the wheel.
>
> Hi Davin,
>
> Will this be a C extension of Emacs core?
>
>
I plan to write the extension in Elisp.


> What are your intentions for the project? What needs do you see it
> fulfilling?
>
>
Anyone who wants Java style threads in their Elisp programs.

Basically, my idea is this:  Suppose you have the following Elisp code:

(defun code ()
   (setq abc 'def)
   (setq def 'ghi))

My mult-threader then generates the following code.

(defun foo-1 ()
   (setq abc 'def)
)

(defun foo-2 ()
  (setq def 'ghi))

Obviously the code gets difficult when you have if/while  constructs.

-- 
Sincerely and kindest regards, Davin.
Davin Pearson    http://davin.50webs.com

[-- Attachment #2: Type: text/html, Size: 1957 bytes --]

  reply	other threads:[~2019-02-09 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 14:33 A completely pre-emptive time sharing system for GNU Emacs Davin Pearson
2019-02-06  6:18 ` John Wiegley
2019-02-09 14:47   ` Davin Pearson [this message]
2019-02-06  8:48 ` Tom Tromey
2019-02-06 15:35 ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAG9ihEsKAOyJinoMPiKYVfi4S__J7W-z-AhfvZOa6GG2MvV3hQ@mail.gmail.com \
    --to=davin.pearson@gmail.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).