unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: tomas@fabula.de
Cc: guile-user@gnu.org, Rob Browning <rlb@defaultvalue.org>, tomas@fabula.de
Subject: Re: Some introductory docs about C level threading
Date: Wed, 2 Feb 2005 14:47:40 +0100	[thread overview]
Message-ID: <20050202134740.GA19682@www> (raw)
In-Reply-To: <ljlla714o9.fsf@troy.dt.e-technik.uni-dortmund.de>


[-- Attachment #1.1: Type: text/plain, Size: 1068 bytes --]

On Wed, Feb 02, 2005 at 02:18:14PM +0100, Marius Vollmer wrote:
> tomas@fabula.de writes:
> 
> > Yes. I think this looks very nice. Some might argue for something more
> > abstract than an integer (a signal_t or whatnot) -- I wouldn't oppose,
> > but I'm very happy with what you propose.
> 
> Yes, I started with scm_t_signal_token, but the OS signal identifiers
> are already ints and when we want to mix them, we need to use ints as
> well.

...unless you let scm_create_new_os_signal () take an integer parameter
(the OS signal identifier) or a magic constant (NEW_OS_SIGNAL or something
like that, to return a `new' signal token).

As I said, to me this is very reasonable. I too lean towards the
``int'' side. To me integers seem quite abstract already ;-)

> I am not starting to work on this immediately, tho.  Anyone?  Tomas?
> The file to look at would be scmsigs.c

I'll have a look at it on Fryday/weekend. At the moment I'm at a customer's
place and I bet they don't even *know* I have Internet connectivity ;-)

Thanks
-- tomás

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user

  reply	other threads:[~2005-02-02 13:47 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21 18:29 Some introductory docs about C level threading Marius Vollmer
2005-01-21 21:20 ` Neil Jerram
2005-01-24 19:23   ` Marius Vollmer
2005-02-15  4:11     ` Robert Uhl
2005-01-22 12:37 ` tomas
2005-01-24 19:28   ` Marius Vollmer
2005-01-25  9:06     ` tomas
2005-01-25 15:58       ` Rob Browning
2005-01-25 16:01         ` Rob Browning
2005-01-26  9:05         ` tomas
2005-02-01 16:01           ` Marius Vollmer
2005-02-02  9:31             ` tomas
2005-02-02 13:18               ` Marius Vollmer
2005-02-02 13:47                 ` tomas [this message]
2005-01-23 23:34 ` Kevin Ryde
2005-01-24 19:31 ` Some new reference docs about initialization Marius Vollmer
2005-01-24 20:27   ` Andreas Rottmann
2005-01-24 22:00     ` Marius Vollmer
2005-02-01 17:37 ` Some introductory docs about C level threading Ken Raeburn
2005-02-01 23:40   ` Kevin Ryde
2005-02-02  0:38     ` Ken Raeburn
2005-02-07  0:48       ` Kevin Ryde
2005-02-08 21:45         ` Ken Raeburn
2005-02-09 12:17         ` Marius Vollmer
2005-02-09 20:26           ` Kevin Ryde
2005-02-10 11:36             ` Marius Vollmer
2005-02-09 12:13       ` Marius Vollmer
2005-02-09 18:10         ` Ken Raeburn
2005-02-10 12:05           ` Marius Vollmer
2005-02-10 19:59             ` Ken Raeburn
2005-02-09 12:08     ` Marius Vollmer
2005-02-09 16:33       ` Doug Evans
2005-02-10 11:15         ` Marius Vollmer
2005-02-09 20:19       ` Kevin Ryde
2005-02-09 12:04   ` Marius Vollmer

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/guile/

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

  git send-email \
    --in-reply-to=20050202134740.GA19682@www \
    --to=tomas@fabula.de \
    --cc=guile-user@gnu.org \
    --cc=rlb@defaultvalue.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.
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).