From: Andrew Simmons <andrew@mbmnz.co.nz>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] code complexity
Date: Thu, 7 Feb 2002 09:49:17 +1300 [thread overview]
Message-ID: <3.0.6.32.20020207094917.0098a0b0@pop3.clear.net.nz> (raw)
In-Reply-To: <3C6109BC.8F7D964B@strakt.com>
>With a DLL all share its data; you do not get a copy.
I didn't think this had been true since the days of 16 bit Windows?
>However, they are both evil.
>
I'm afraid I've been turned to the dark side here. I've found them very
useful to add functionality to applications written by others -
particularly MS Excel, where I've written DLL add-ins to do various things
such as NZ bond pricing & pulling in data from ISAM files. There may be
other & better ways of doing this kind of thing, but I don't know what they
are. I believe the Oberon system has some way of adding functionality at
run time.
next prev parent reply other threads:[~2002-02-06 20:49 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 ` [9fans] code complexity George Michaelson
2002-02-06 10:47 ` Boyd Roberts
2002-02-06 20:49 ` Andrew Simmons [this message]
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=3.0.6.32.20020207094917.0098a0b0@pop3.clear.net.nz \
--to=andrew@mbmnz.co.nz \
--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).