From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: Steven Tamm <steventamm@mac.com>, emacs-devel@gnu.org
Subject: Re: Carbon port: setting the creator code (patch)
Date: Sun, 10 Jul 2005 09:56:01 +0900 [thread overview]
Message-ID: <wl3bqn5vj2.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <8F8C693C-FCF4-4C74-9473-2329578539DC@mac.com>
>>>>> On Sat, 9 Jul 2005 09:08:16 -0700, Steven Tamm <steventamm@mac.com> said:
> That doesn't mean we shouldn't add the feature to "set a creator
> code", but it should take in the code as a parameter (a four
> character string or a 32-bit number).
> (mac-set-creator-type "EMAx")
> (mac-set-file-type "TEXT")
Apparently the argument for a file name is missing. :-)
I think these functions should follow the convention of existing
operations on files. For example, with respect to the default
directory, error handling, and argument names. Maybe the function
name should be "mac-set-file-creator". We can additionally think of
"mac-file-creator" and "mac-file-type", or "mac-file-attributes" for
reading these kinds of information.
And more importantly, please care about BLOCK_INPUT when adding new C
functions. It required much effort to fill missing BLOCK_INPUTs that
had been a cause of unstability in the Carbon port.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2005-07-10 0:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 9:05 Carbon port: setting the creator code (patch) David Reitter
2005-07-09 3:04 ` Steven Tamm
2005-07-09 8:11 ` Sébastien Kirche
2005-07-09 13:06 ` David Reitter
2005-07-09 16:08 ` Steven Tamm
2005-07-10 0:56 ` YAMAMOTO Mitsuharu [this message]
2005-07-10 11:55 ` David Reitter
2005-07-10 11:16 ` David Reitter
2005-07-10 13:30 ` Benjamin Riefenstahl
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wl3bqn5vj2.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=emacs-devel@gnu.org \
--cc=steventamm@mac.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.