From: Keith Seitz <keiths@cygnus.com>
To: Mo DeJong <mdejong@cygnus.com>
Cc: <insight@sources.redhat.com>
Subject: Re: PATCH: Tix fix for dllexport via TCL_STORAGE_CLASS
Date: Wed, 15 Aug 2001 11:23:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0108151121100.25893-100000@makita.cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1010814193830.29712A-100000@rtl.cygnus.com>
On Tue, 14 Aug 2001, Mo DeJong wrote:
> Here is a little patch that does effect Insight.
> This will fix the dllimport modifier used by the EXTERN
> keyword in tix. This was broken in tix but Tcl 8.0
> did not make use of the dllexport modifiers to
> function declarations so it did not matter. When tix
> is compiled with Tcl 8.3 this blows up rather badly.
> This patch has been tested with Cygwin gcc under Windows
> so I think it is safe to add.
I don't know who actually controls this stuff, but I guess that I would
have some say in it...
I don't see anything obvious that would raise a red flag. If it works, it
works. Go for it.
Besides, if it turns problematic, I'll just have to ramp up my effort at
dumping tix out of the repository (or at least insight)! :-)
Keith
prev parent reply other threads:[~2001-08-15 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 19:46 Mo DeJong
2001-08-15 11:23 ` Keith Seitz [this message]
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.GSO.4.33.0108151121100.25893-100000@makita.cygnus.com \
--to=keiths@cygnus.com \
--cc=insight@sources.redhat.com \
--cc=mdejong@cygnus.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).