From: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
Cc: emacs-devel@gnu.org
Subject: Re: Problem with library images on Windows (again)
Date: Fri, 20 May 2005 14:19:28 +0200 [thread overview]
Message-ID: <m3mzqq144v.fsf@seneca.benny.turtle-trading.net> (raw)
In-Reply-To: <428DB8F3.3070108@gnu.org> (Jason Rumney's message of "Fri, 20 May 2005 11:16:19 +0100")
Hi Jason,
Jason Rumney writes:
> The version of TIFF headers I have uses extern "C" if compiling
> under C++, so I doubt the library is using Pascal calling
> conventions. Maybe Juanma's library is different than mine.
'extern "C"' doesn't mean what you think it means, at least not in
most compilers.
In theory 'extern "<Language>"' is the C++ equivalent of the
propriatory '__cdecl', '__stdcall' and '__pascal' keywords known from
the C compilers. But the exact behaviour of that C++ feature is
implementation defined, especially for languages other than "C".
In practice with MSC++ and GCC, '__stdcall' and 'extern "C"' are
*both* needed (or at least it's highly recommended to use both) in C++
mode to actually get '__stdcall' calling conventions and name
mangling.
benny
prev parent reply other threads:[~2005-05-20 12:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 15:53 Problem with library images on Windows (again) Juanma Barranquero
2005-05-18 19:30 ` Andreas Schwab
2005-05-18 22:44 ` Juanma Barranquero
2005-05-19 6:58 ` Jason Rumney
2005-05-18 22:16 ` Jason Rumney
2005-05-18 22:52 ` Juanma Barranquero
2005-05-19 3:50 ` Eli Zaretskii
2005-05-19 8:13 ` Juanma Barranquero
2005-05-19 19:05 ` Eli Zaretskii
2005-05-19 19:31 ` Juanma Barranquero
2005-05-19 19:32 ` Juanma Barranquero
2005-05-20 7:20 ` Eli Zaretskii
2005-05-20 8:24 ` Kim F. Storm
2005-05-20 10:01 ` Eli Zaretskii
2005-05-20 10:16 ` Jason Rumney
2005-05-20 10:42 ` Juanma Barranquero
2005-05-20 14:44 ` Eli Zaretskii
2005-05-20 15:46 ` Jason Rumney
2005-05-20 15:52 ` Eli Zaretskii
2005-05-20 16:33 ` Juanma Barranquero
2005-05-20 17:57 ` Juanma Barranquero
2005-05-21 10:21 ` Jason Rumney
2005-05-21 10:33 ` Juanma Barranquero
2005-05-21 21:13 ` Jason Rumney
2005-05-22 21:21 ` Juanma Barranquero
2005-06-03 12:08 ` Juanma Barranquero
2005-06-03 13:06 ` David Kastrup
2005-06-03 15:28 ` jasonr
2005-06-03 17:23 ` Stefan Monnier
2005-06-05 0:44 ` Juanma Barranquero
2005-06-06 11:26 ` Juanma Barranquero
2005-06-14 2:02 ` Juanma Barranquero
2005-06-14 7:32 ` David Kastrup
2005-06-14 9:15 ` Juanma Barranquero
2005-05-20 16:31 ` Juanma Barranquero
2005-05-20 16:29 ` Juanma Barranquero
2005-05-20 12:19 ` Benjamin Riefenstahl [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3mzqq144v.fsf@seneca.benny.turtle-trading.net \
--to=b.riefenstahl@turtle-trading.net \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).