From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: Carbon port emacs-unicode-2 build problem under MacOSX
Date: Wed, 07 Nov 2007 14:52:23 +0900 [thread overview]
Message-ID: <wlhcjypppk.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <m2mytqvda1.fsf@lifelogs.com>
>>>>> On Tue, 06 Nov 2007 23:24:22 -0600, Ted Zlatanov <tzz@lifelogs.com> said:
YM> Could you precisely describe in what aspects you think it's "much
YM> better"?
> Well, the short answer is that it actually takes input from the
> keyboard. I'd say that's a big improvement over today's Carbon port
> builds.
OK, I'm not interested in the comparison between a working one and a
not working one.
> That aside, it has better integration with the MacOS, a nice
> Preferences dialog, better font rendering, and other improvements
> listed in the ChangeLog.
What is "better integration with the MacOS", concretely? In what
sense the font rendering in the Carbon port is worse?
And I don't think the Preference dialog that can't be controlled from
Emacs Lisp is suitable for Emacs.
YM> If it were really deprecated, Apple wouldn't have added any new
YM> frameworks to Carbon in Leopard.
> According to this article:
> http://arstechnica.com/reviews/os/mac-os-x-10-5.ars/6
> "Yep, it's (finally) the end of the line for Carbon GUI applications
> in Mac OS X. Oh, sure, they'll be around for years and years to
> come, but the lack of 64-bit support is a long-term death sentence.
> The last vestiges of the original Macintosh API are finally being
> put to rest. They've done their job and are being given a decent
> burial, I think. A slow, almost natural transition. Bugs will be
> fixed in the 32-bit Carbon APIs, of course, but no new features will
> be added. All new GUI APIs in Leopard and future Mac OS X releases
> will be added as Cocoa-only APIs."
> This is based on Apple's official announcements, not the author's
> opinion.
It says about the *GUI* APIs in Carbon, not the whole Carbon APIs.
That's why I'm making the Carbon+AppKit port (for Emacs 22) mentioned
elsewhere:
http://lists.gnu.org/archive/html/emacs-devel/2007-09/msg00395.html
YM> Did that cause any real problems?
YM> I'm asking because they are related not only to the effectively
YM> unmaintained Carbon port for Emacs 23 but also to the maintained
YM> one for Emacs 22.
> No, deprecation warnings are not a problem in themselves, they
> indicate the API will go away. That's their purpose, generally.
> I assumed that the deprecation warnings I saw while compiling the
> Carbon port were Apple's way of telling developers the Carbon APIs
> are deprecated. Am I wrong?
It wouldn't go away soon for the binary compatibility for existing
Carbon applications. And the warnings are not about the whole Carbon,
again. Actually, as for the Carbon+AppKit port in 64-bit environment,
it compiles without any `deprecated' warnings and runs, though there
still remain a few major problems such as suspected ATSUI bug, which
I've already reported to Apple, and some unexec problem.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2007-11-07 5:52 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 12:02 Carbon port emacs-unicode-2 build problem under MacOSX CHENG Gao
2007-11-06 12:14 ` CHENG Gao
2007-11-06 12:29 ` Kenichi Handa
2007-11-06 13:52 ` CHENG Gao
2007-11-06 19:28 ` Ted Zlatanov
2007-11-06 23:27 ` Glenn Morris
2007-11-07 4:59 ` Ted Zlatanov
2007-11-07 13:19 ` Carbon port vs. Emacs.app plus Emacs.app problem report w/test-case Mike Mattie
2007-11-07 13:54 ` Ted Zlatanov
2007-11-07 15:45 ` Mike Mattie
2007-11-06 12:34 ` Carbon port emacs-unicode-2 build problem under MacOSX Jason Rumney
2007-11-06 13:58 ` CHENG Gao
2007-11-06 19:26 ` Ted Zlatanov
2007-11-07 4:13 ` YAMAMOTO Mitsuharu
2007-11-07 5:24 ` Ted Zlatanov
2007-11-07 5:52 ` YAMAMOTO Mitsuharu [this message]
2007-11-07 6:03 ` YAMAMOTO Mitsuharu
2007-11-07 14:19 ` Ted Zlatanov
2007-11-07 14:34 ` Jason Rumney
[not found] ` <m2abpqt5mm.fsf@lifelogs.com>
2007-11-07 16:40 ` Adrian Robert
2007-11-08 4:42 ` Richard Stallman
2007-11-08 1:27 ` YAMAMOTO Mitsuharu
2007-11-08 2:31 ` YAMAMOTO Mitsuharu
2007-11-24 9:18 ` YAMAMOTO Mitsuharu
2008-02-12 0:59 ` YAMAMOTO Mitsuharu
2007-11-07 14:15 ` Adrian Robert
2007-11-07 15:05 ` Jason Rumney
2007-11-07 16:09 ` Stefan Monnier
2007-11-08 4:42 ` Richard Stallman
2007-11-08 15:56 ` Dan Nicolaescu
2007-11-09 4:12 ` Richard Stallman
2007-11-09 7:47 ` Dan Nicolaescu
2007-11-09 10:34 ` Eli Zaretskii
2007-11-09 15:09 ` Dan Nicolaescu
2007-11-10 17:54 ` Richard Stallman
2007-11-12 5:17 ` How to re-orgranize ChangeLog.unicode for merging Kenichi Handa
2007-11-12 20:22 ` Eli Zaretskii
2007-11-12 22:17 ` Andreas Schwab
2007-11-13 4:08 ` Eli Zaretskii
2007-11-18 22:47 ` Richard Stallman
2007-11-18 22:47 ` Richard Stallman
2007-11-07 16:14 ` Carbon port emacs-unicode-2 build problem under MacOSX Dan Nicolaescu
2007-11-08 4:42 ` Richard Stallman
2007-11-07 18:30 ` CHENG Gao
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=wlhcjypppk.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.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).