unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: emacs-devel@gnu.org, jasonr@btinternet.com, rms@gnu.org
Subject: Re: Updated patch for a Windows implementation of play-sound
Date: Wed, 23 Oct 2002 01:30:02 -0400	[thread overview]
Message-ID: <200210230530.g9N5U3q05183@rum.cs.yale.edu> (raw)
In-Reply-To: 000001c27a50$fb6b70d0$6401a8c0@GODDESS

> This is an updated version of my patch to provide a Windows compatible
> implementation of play-sound.  Currently only Emacs version 21.3.5 is
> supported by this patch.  I will later be releasing a version of this patch
> that supports version 21.2.

If I were you I wouldn't bother with a 21.2 version.  It would
only be used by people who want sound but don't want to use 21.3.50
and yet are willing to get the source code and recompile.  I expect
this group of people to be pretty small (especially on w32).

> * src/lisp.h has been modified so that the preprocessor symbol
> _USE_PLAY_SOUND_INTERNAL is defined.  In the pending 21.2 compatible version
> of this patch, this change will not be included.  This change is necessary
> for version 21.3 because the file w32sound.c is used for both versions and
> the name of the play-sound internal function is different in version 21.3
> (play-sound-internal) than it is in version 21.2 (play-sound).  If the
> preprocessor function _USE_PLAY_SOUND_INTERNAL is defined, the primary
> function in w32sound.c is defined as play-sound-internal and it is defined
> as play-sound otherwise.

The main target should be 21.3.50 so it would be better not to add
unrelated cruft in it.

> * src/sound.c has been modified to avoid any chance of a conflict between
> w32sound.c and sound.c.  Previously the statement
>   #ifdef HAVE_SOUND
> was used to determine whether or not to compile the file.  This has been
> changed to
>   #if defined(HAVE_SOUND) && !defined(_WIN32)
> 
> * src/w32sound.c has been added.  This contains my Windows implementation of
> play-sound.  It is conditionally compiled as follows:
>   #if defined(HAVE_SOUND) && defined(_WIN32)

How about not adding a new file w32sound.c but instead adding the
corresponding code to sound.c (and of course wrap things in
#ifdef WINDOWSNT (or _WIN32, I don't know what is what: most of
the Emacs C code I've seen seems to be using WINDOWSNT)).
This way the parsing and other such things will be shared.

Oh, and please just send the plaintext patch as attachment,
so we don't need to save/unpack the zip archive to read it.


	Stefan

  reply	other threads:[~2002-10-23  5:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23  4:59 Updated patch for a Windows implementation of play-sound Ben Key
2002-10-23  5:30 ` Stefan Monnier [this message]
2002-10-23  6:16   ` Eli Zaretskii

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=200210230530.g9N5U3q05183@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@btinternet.com \
    --cc=rms@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).