From: Stefan Monnier <monnier@iro.umontreal.ca>
To: martin rudalics <rudalics@gmx.at>
Cc: Ross Biro <ross.biro@mindspring.com>, 13479@debbugs.gnu.org
Subject: bug#13479: Cross Compiling for ARM
Date: Fri, 18 Jan 2013 20:18:31 -0500 [thread overview]
Message-ID: <jwvip6u9dle.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <50F98C7B.8090708@gmx.at> (martin rudalics's message of "Fri, 18 Jan 2013 18:55:07 +0100")
>> Most/all calls to Elisp from C should protect themselves with calls to
>> Ffboundp or similar, indeed. Martin, could you take care of that?
> I'm not sure. If most/all calls should be protected we'd better provide
> call_[1-4]_safe function for this purpose.
Could be, but I suspect that when the function is not defined, we might
actually want to do something else rather than not do anything at all,
so maybe just call_safe is not quite sufficient.
> But I haven't the slightest idea of what might happen when some of
> these functions don't get called.
These calls come from your "rewrite" of the window.c code, AFAIK, so
I think you're the person who'd best know what needs to happen when
window.el is not yet loaded,
Stefan
next prev parent reply other threads:[~2013-01-19 1:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 19:36 bug#13479: Cross Compiling for ARM Ross Biro
2013-01-18 14:26 ` Stefan Monnier
2013-01-18 17:55 ` martin rudalics
2013-01-18 22:09 ` Ross Biro
2013-01-19 10:11 ` martin rudalics
2013-01-23 3:49 ` Ross Biro
2013-01-23 7:31 ` martin rudalics
2013-01-19 1:18 ` Stefan Monnier [this message]
2013-01-24 4:42 ` Jason Rumney
2024-01-10 11:11 ` Stefan Kangas
-- strict thread matches above, loose matches on Subject: below --
2011-07-28 18:53 bug#9192: Cross-compile " Toon Claes
2024-01-10 11:11 ` bug#13479: Cross Compiling " Stefan Kangas
2024-01-10 11:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-10 11:56 ` Stefan Kangas
2024-01-10 13:10 ` Toon Claes via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=jwvip6u9dle.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=13479@debbugs.gnu.org \
--cc=ross.biro@mindspring.com \
--cc=rudalics@gmx.at \
/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).