unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Jason Rumney <jasonr@f2s.com>
Cc: Juanma Barranquero <lekktu@gmail.com>,
	Chong Yidong <cyd@stupidchicken.com>,
	Emacs Devel <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] emacs/lib-src emacsclient.c ChangeLog
Date: Wed, 10 Dec 2008 08:55:58 -0800 (PST)	[thread overview]
Message-ID: <200812101655.mBAGtwPw025867@mothra.ics.uci.edu> (raw)
In-Reply-To: <493FF0F7.1070305@f2s.com> (Jason Rumney's message of "Thu, 11 Dec 2008 00:40:23 +0800")

Jason Rumney <jasonr@f2s.com> writes:

  > Juanma Barranquero wrote:
  > > But the base discussion is whether features should be tested by
  > > feature tests, or lumped together into the WINDOWSNT, DOS_NT,
  > > NS_IMPL_* bags. We've been saying for years that Emacs lisp programs
  > > must not check the Emacs version, but features. The same reasoning
  > > applies to checking HAVE_DAEMON vs. WINDOWSNT.
  > >   
  > 
  > When it is just not possible to support a feature because of the
  > platform, then I have no problem using the platform constant to
  > conditionally compile it out. But if it is just a lack of developers
  > on a particular platform that is preventing the feature from being
  > implemented, then it is much easier for later developers who wish to
  > implement it if there is a feature specific constant.
  > 
  > NO_SOCKETS_IN_FILE_SYSTEM is sitting on a blurry line, since although
  > Windows does not support unix domain sockets, it is conceivable that
  > an emulation of them using named pipes could be developed in future.

The problem with that is that WINDOWSNT has many many idiosyncrasies,
having a #define for each one of them adds an overhead for the ones of
us working on free systems.




  parent reply	other threads:[~2008-12-10 16:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1LAQV6-0003hq-HV@cvs.savannah.gnu.org>
2008-12-10 15:01 ` [Emacs-diffs] emacs/lib-src emacsclient.c ChangeLog Juanma Barranquero
2008-12-10 15:25   ` Juanma Barranquero
2008-12-10 15:46     ` Dan Nicolaescu
2008-12-10 15:54       ` Juanma Barranquero
2008-12-10 16:15         ` Chong Yidong
2008-12-10 16:20           ` Juanma Barranquero
2008-12-10 16:35             ` Chong Yidong
2008-12-10 16:50               ` Juanma Barranquero
2008-12-10 16:40             ` Jason Rumney
2008-12-10 16:46               ` Juanma Barranquero
2008-12-10 16:55               ` Dan Nicolaescu [this message]
2008-12-10 19:26                 ` Lennart Borgman
2008-12-10 19:36                   ` Dan Nicolaescu
2008-12-10 19:51                     ` Lennart Borgman
2008-12-10 20:03                       ` Dan Nicolaescu
2008-12-10 20:18                         ` Lennart Borgman
2008-12-10 20:26                           ` Dan Nicolaescu
2008-12-10 20:34                             ` Lennart Borgman
2008-12-10 16:31           ` Dan Nicolaescu
2008-12-10 16:33           ` Harald Hanche-Olsen
     [not found] <E1LAYb6-0004jn-HF@cvs.savannah.gnu.org>
2008-12-10 23:45 ` 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=200812101655.mBAGtwPw025867@mothra.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@f2s.com \
    --cc=lekktu@gmail.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.
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).