From: joakim@verona.se
To: Juanma Barranquero <lekktu@gmail.com>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, "Eli Zaretskii" <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Windows 9X compatibility
Date: Sun, 28 Mar 2010 20:03:01 +0200 [thread overview]
Message-ID: <m3tys0z5m2.fsf@verona.se> (raw)
In-Reply-To: <f7ccd24b1003280909l29ccebc1x1a86289597a7b4ee@mail.gmail.com> (Juanma Barranquero's message of "Sun, 28 Mar 2010 18:09:55 +0200")
Juanma Barranquero <lekktu@gmail.com> writes:
> On Sun, Mar 28, 2010 at 17:56, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> True, there is some maintenance burden, but I personally find it
>> insignificant. The code to load a library safely and invoke functions
>> that may not exist is very simple, almost boilerplate, and each
>> additional API that needs this treatment just needs more-or-less
>> copy-pasted more of the same.
>>
>> Once again, I'm bewildered by the intense reaction to this issue,
>> given the facts.
>
> FWIW, I agree.
>
> Juanma
>
>
I have done some pretty intense C level Emacs hacking, regarding image
support and the display engine. The many different supported plattforms
does make the code harder to read, and I dont generally know if my code
works on other platforms than my own. OTOH the great cross platform
support is one of the aspects that made me use Emacs initially, so its a
worthwile cause to keep it working on many platforms.
Since dynamic linking has now been approved for the Emacs core, maybe
some plugin architecture could be designed now, that makes it easier to
support different platforms.
--
Joakim Verona
next prev parent reply other threads:[~2010-03-28 18:03 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 15:22 MS-Windows build broken in Fmake_network_process Eli Zaretskii
2010-03-26 15:48 ` Helmut Eller
2010-03-26 17:56 ` Eli Zaretskii
2010-03-26 18:05 ` Helmut Eller
2010-03-26 18:09 ` Eli Zaretskii
2010-03-26 18:17 ` Helmut Eller
2010-03-26 20:05 ` Eli Zaretskii
2010-03-26 21:14 ` Helmut Eller
2010-03-27 8:50 ` Eli Zaretskii
2010-03-27 10:09 ` Helmut Eller
2010-03-27 11:11 ` Eli Zaretskii
2010-03-27 13:56 ` Helmut Eller
2010-03-27 0:48 ` Chong Yidong
2010-03-27 7:42 ` Eli Zaretskii
2010-03-27 16:49 ` Jason Rumney
2010-03-27 16:55 ` Eli Zaretskii
2010-03-27 22:28 ` Christoph
2010-03-28 0:12 ` Florian Beck
2010-03-28 0:37 ` Óscar Fuentes
2010-03-28 7:26 ` Eli Zaretskii
2010-03-28 18:55 ` Chong Yidong
2010-03-28 20:10 ` Eli Zaretskii
2010-03-28 23:23 ` Jason Rumney
2010-03-29 23:39 ` Richard Stallman
2010-03-31 4:57 ` Stephen J. Turnbull
2010-03-31 8:38 ` Eli Zaretskii
2010-03-31 10:38 ` Juanma Barranquero
2010-03-31 11:19 ` Eli Zaretskii
2010-03-31 15:39 ` Stephen J. Turnbull
2010-03-31 16:39 ` Juanma Barranquero
2010-03-31 17:30 ` Stephen J. Turnbull
2010-03-31 17:36 ` Juanma Barranquero
2010-03-31 18:05 ` OT: (was: MS-Windows build broken in Fmake_network_process) Stefan Monnier
2010-03-31 15:28 ` MS-Windows build broken in Fmake_network_process Stephen J. Turnbull
2010-03-31 16:12 ` Eli Zaretskii
2010-03-31 16:59 ` Stephen J. Turnbull
2010-03-31 17:27 ` Eli Zaretskii
2010-03-31 18:08 ` Stephen J. Turnbull
2010-04-06 7:50 ` David Kastrup
2010-04-07 3:21 ` Richard Stallman
2010-04-07 7:59 ` David Kastrup
2010-03-28 0:39 ` Christoph
2010-03-28 7:21 ` Windows 9X compatibility Eli Zaretskii
2010-03-28 14:59 ` Óscar Fuentes
2010-03-28 15:24 ` Lennart Borgman
2010-03-28 15:56 ` Eli Zaretskii
2010-03-28 16:09 ` Juanma Barranquero
2010-03-28 18:03 ` joakim [this message]
2010-03-29 23:39 ` Richard Stallman
2010-03-28 19:57 ` Óscar Fuentes
2010-03-28 20:32 ` Eli Zaretskii
2010-03-28 22:26 ` Juanma Barranquero
2010-03-28 19:27 ` Christoph
2010-03-28 20:18 ` Eli Zaretskii
2010-03-28 21:04 ` Christoph
2010-03-28 7:17 ` Windows 9X compatibility (was: MS-Windows build broken in Fmake_network_process) Eli Zaretskii
2010-03-28 7:33 ` MS-Windows build broken in Fmake_network_process Jason Rumney
2010-03-28 8:12 ` Eli Zaretskii
2010-03-29 23:39 ` Richard Stallman
2010-03-28 9:11 ` Serious performance problem with process output on Mac OSX Christian Lynbech
2010-03-28 14:41 ` Adrian Robert
2010-03-29 21:58 ` Adrian Robert
2010-03-29 23:26 ` David Reitter
2010-03-29 23:54 ` Chong Yidong
2010-03-30 7:43 ` Adrian Robert
2010-03-30 13:05 ` David Reitter
2010-03-30 17:39 ` Jimmy Yuen Ho Wong
2010-03-30 17:47 ` Chong Yidong
2010-03-31 2:38 ` Jimmy Yuen Ho Wong
2010-03-31 4:00 ` Chong Yidong
2010-03-31 13:41 ` Jimmy Yuen Ho Wong
2010-03-31 14:28 ` Chong Yidong
2010-03-31 14:29 ` Adrian Robert
2010-03-29 23:48 ` MS-Windows build broken in Fmake_network_process Davis Herring
2010-03-30 5:41 ` Jason Rumney
2010-03-26 23:03 ` Juanma Barranquero
2010-03-27 0:51 ` YAMAMOTO Mitsuharu
2010-03-27 8:44 ` Eli Zaretskii
2010-03-27 13:01 ` Óscar Fuentes
2010-03-27 13:18 ` Juanma Barranquero
2010-03-28 17:29 ` Kim F. Storm
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=m3tys0z5m2.fsf@verona.se \
--to=joakim@verona.se \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=ofv@wanadoo.es \
/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).