From: Ben Elliston <bje@redhat.com>
To: Syd Polk <spolk@redhat.com>
Cc: Mo DeJong <mdejong@cygnus.com>, <sourcenav@sources.redhat.com>
Subject: Re: Adding Ruby support to Source Navigator
Date: Mon, 13 Nov 2000 14:11:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.30.0011140910270.31422-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <3A101BE4.129FADE4@redhat.com>
> I'm trying to decide whether all libraries matching a specific pattern (say,
> "*high*.so" should be loaded, or whether they should be named explicitly in
> the configuration file. Thoughts?
Hmm. I hate configuration files. I would vote for a pattern.
Something like:
sn*high*.so on unix
and
sn*high*.dll on windows.
What about the problems whereby users get confused by implict behaviour?
I have implicit behaviour. :-)
Ben
next prev parent reply other threads:[~2000-11-13 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 13:25 Dave Thomas
2000-11-11 18:55 ` Mo DeJong
2000-11-13 6:05 ` Ben Elliston
2000-11-13 8:47 ` Syd Polk
2000-11-13 14:11 ` Ben Elliston [this message]
2000-11-13 14:28 Ian Roxborough
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=Pine.LNX.4.30.0011140910270.31422-100000@moshpit.cygnus.com \
--to=bje@redhat.com \
--cc=mdejong@cygnus.com \
--cc=sourcenav@sources.redhat.com \
--cc=spolk@redhat.com \
/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).