From: jasonr@btinternet.com
Cc: emacs-devel@gnu.org
Subject: Re: [Patch for Windows implementation of play-sound]
Date: Tue, 22 Oct 2002 10:05:32 +0100 (BST) [thread overview]
Message-ID: <4380404.1035277532467.JavaMail.root@127.0.0.1> (raw)
If you need to copy structs from include files,
the mingw32 w32 headers are a safer option, since
they are already reverse engineered from the w32 APIs
and GPLed, and the fragment is usually small enough
that we won't need papers for it.
I agree that setting WINVER and _WIN32_WINNT explicitly
is not a viable solution, as these are internal to
the compiler, and may cause the compiler to make invalid
assumptions if set incorrectly.
> from: Juanma Barranquero <lektu@terra.es>
> date: Tue, 22 Oct 2002 08:37:53
> to: Bkey1@tampabay.rr.com
> cc: emacs-devel@gnu.org
> subject: Re: [Patch for Windows implementation of play-sound]
>
> On Mon, 21 Oct 2002 21:08:51 -0400, "Ben Key" <Bkey1@tampabay.rr.com> wrote:
>
> > This is not true. I did not say that the newest version of MSSDK is
> > required. I said that I have it installed. My patch will work with the
> > include files that are included with Visual C 6.0. You will, however, see
> > a large number of warning messages due to the following segment of the
> > version of WINDOWS.H that is included with Visual C 6.0:
>
> Ok, you're right, it does not *require* it. Still, getting such a large
> list of (menacing) warnings for the benefit of adding a function (even
> if play-sound can be considered an important one) doesn't seem right.
>
> > This warning message is displayed because I had to define WINVER and
> > _WIN32_WINNT to at least 0x0500 to avoid a compilation error I was
> > experiencing. I do not at this time have the details about that compilation
> > error.
>
> Then please investigate that further. Perhaps it is as simple as a new
> struct or whatever that could be copied. OTOH, I don't know the legal
> status of copying a fragment of a Microsoft #include file for use in a
> program, although I know that bindings to other languages routinely do
> adapt code from windows.h and other includes.
>
> Thanks,
>
> /L/e/k/t/u
>
>
>
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://mail.gnu.org/mailman/listinfo/emacs-devel
next reply other threads:[~2002-10-22 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 9:05 jasonr [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-22 13:56 [Patch for Windows implementation of play-sound] bkey1
2002-10-22 9:28 jasonr
2002-10-21 6:52 [Bkey1@tampabay.rr.com: Patch " Juanma Barranquero
2002-10-22 1:08 ` [Patch " Ben Key
2002-10-22 7:37 ` Juanma Barranquero
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=4380404.1035277532467.JavaMail.root@127.0.0.1 \
--to=jasonr@btinternet.com \
--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).