From: George Michaelson <ggm@apnic.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] code complexity
Date: Wed, 6 Feb 2002 10:29:50 +1000 [thread overview]
Message-ID: <16689.1012955390@apnic.net> (raw)
In-Reply-To: Your message of "Tue, 05 Feb 2002 16:10:00 -0800." <20020206001339.2FBC619981@mail.cse.psu.edu>
I've been told DLLs include some smarts about code introspection so
you can find out whats in the damn things sensibly, runtime and know
how to interact with them.
I would have thought there were simple ways to do that, and Its not
such a bad idea to include a call which tells you what to pass in, to
talk to the external bindings made visible inside the package.
-George
--
George Michaelson | APNIC
Email: ggm@apnic.net | PO Box 2131 Milton QLD 4064
Phone: +61 7 3367 0490 | Australia
Fax: +61 7 3367 0482 | http://www.apnic.net
next prev parent reply other threads:[~2002-02-06 0:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 0:10 [9fans] XP (was: code complexity) geoff
2002-02-06 0:29 ` George Michaelson [this message]
2002-02-06 10:47 ` [9fans] code complexity Boyd Roberts
2002-02-06 20:49 ` Andrew Simmons
2002-02-06 0:47 ` [9fans] OT XP (was: code complexity) Matt H
2002-02-07 10:33 ` [9fans] OT pair programming Boyd Roberts
2002-02-06 10:42 ` [9fans] XP (was: code complexity) Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2002-02-05 16:41 [9fans] code complexity Russ Cox
2002-02-05 16:34 Russ Cox
2002-02-05 16:39 ` Boyd Roberts
2002-02-05 16:42 ` Ronald G Minnich
2002-02-05 17:20 ` david presotto
2002-02-05 23:06 ` Steve Kilbane
2002-02-05 20:24 ` philw
2002-02-06 1:01 ` ozan s yigit
2002-02-05 22:28 ` Dan Cross
2002-02-05 14:24 Richard Uhtenwoldt
2002-02-05 14:47 ` Matt H
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=16689.1012955390@apnic.net \
--to=ggm@apnic.net \
--cc=9fans@cse.psu.edu \
/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).