From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] a jmp_buf in APE question
Date: Mon, 7 Jan 2013 06:15:08 -0500 [thread overview]
Message-ID: <ffa1f863ed603ea4877115140f236c1c@kw.quanstro.net> (raw)
In-Reply-To: <1637616.FvtJCIHcLZ@krypton>
> Do you mean by this that it would be unwise to do something like
>
> "variable that needs to be = sp" = (jmp_buf) jb[0]
> "variable that needs to be = pc" = (jmp_buf) jb[1]
yes, i think it would be unwise. i think you mean
sp = ((uintptr*)jb)[0]
pc = ((uintptr*)jb)[1]
> this is how other similar ports of this package (GNU portable threads) have
> been made, for example for win32
it's just my opinion. i would see such code as peeking through
an deliberately-opaque interface. and to me that's almost always
a bad idea. even if it works, and even if other people do it.
others might have other thoughts.
- erik
next prev parent reply other threads:[~2013-01-07 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 5:45 Jens Staal
2013-01-07 10:31 ` erik quanstrom
2013-01-07 11:05 ` Jens Staal
2013-01-07 11:15 ` erik quanstrom [this message]
2013-01-07 16:43 ` Jens Staal
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ffa1f863ed603ea4877115140f236c1c@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).