From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Good sample GUI code (window creation, management,
Date: Wed, 19 Dec 2012 09:42:33 -0500 [thread overview]
Message-ID: <5f1ca74bc251e5f5ca9c80102edb31f2@kw.quanstro.net> (raw)
In-Reply-To: <CAOa-2Wzf+brAbs0XKw-P7GBRQfVrSe7-7-dbesnuK-ZwGqbkYA@mail.gmail.com>
On Wed Dec 19 09:36:41 EST 2012, ucasano@gmail.com wrote:
> Does it work in Plan9Port?
>
it's left as an exercize to the reader to add the missing
function parameters and USED(unused). but it does work.
- erik
next prev parent reply other threads:[~2012-12-19 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 11:14 Luke Evans
2012-12-19 12:59 ` Jacob Todd
2012-12-19 13:02 ` cinap_lenrek
2012-12-19 13:32 ` erik quanstrom
2012-12-19 14:35 ` Giovanni Casano
2012-12-19 14:42 ` erik quanstrom [this message]
2012-12-19 14:54 ` Giovanni Casano
2012-12-19 16:07 ` Stuart Morrow
2012-12-19 16:17 ` Dustin Fechner
2012-12-19 16:27 ` Stuart Morrow
2012-12-19 16:29 ` erik quanstrom
2012-12-20 9:45 ` dexen deVries
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=5f1ca74bc251e5f5ca9c80102edb31f2@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).