From: Pip Cet <pipcet@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: [EXPERIMENT] Emacs with the SpiderMonkey garbage collector
Date: Fri, 24 Nov 2017 23:27:12 +0000 [thread overview]
Message-ID: <CAOqdjBerV-T6gwFN+gT-txsNDAQhzZXTBFERJpx=Vh8dhjtTVw@mail.gmail.com> (raw)
In-Reply-To: <e3706b2d-7289-dba5-382a-8ce276ace94b@cs.ucla.edu>
On Fri, Nov 24, 2017 at 6:20 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
> Pip Cet wrote:
>> The most vexing issue for me right now is that I haven't figured out
>> how to get gnulib working with g++ without modifying files after every
>> sh autogen.sh, though. I admit I don't understand the gnulib build
>> process at all, so any hints would be appreciated.
>
> Emacs has a special way of using Gnulib, unfortunately. I wrote the Gnulib
> interface (sorry! :-) and so can perhaps be of help here. What sort of
> modifications are needed after autogen.sh? Perhaps we can lessen and/or
> eliminate the need for them.
I have to remove the memrchr prototype. Editing gnulib.mk seems like
it should help, but for some reason it doesn't; is gnulib.mk
regenerated by autogen.sh, and, if so, how do I change its options?
>> The other issues are minor (a union and a typedef sharing a name, C++
>> keywords, enums treated as ints),
>
>
> If you would submit patches to fix these, that might help you in future
> merges.
> Of the three, enums treated as ints seems like it'd be the most
> hassle, as enums are the only way that C has to name small ints that can be
> used where an integer constant expression can be used. I'd hate to have to
> cast these names to int every time I used them, just to pacify C++. Perhaps
> the enum-to-int business could be handled by the C-to-C++ translator
> instead.
So let's do the first and maybe the keywords, but leave the enums in.
next prev parent reply other threads:[~2017-11-24 23:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 19:01 [EXPERIMENT] Emacs with the SpiderMonkey garbage collector Pip Cet
2017-11-24 8:07 ` Paul Eggert
2017-11-24 16:23 ` Pip Cet
2017-11-24 18:20 ` Paul Eggert
2017-11-24 23:27 ` Pip Cet [this message]
2017-11-25 0:21 ` Paul Eggert
2017-11-25 23:50 ` Pip Cet
2017-11-24 22:13 ` Stefan Monnier
2017-11-24 23:05 ` Pip Cet
2017-11-25 4:15 ` Stefan Monnier
2017-11-25 23:50 ` Pip Cet
2017-11-26 1:20 ` Stefan Monnier
2017-11-26 4:20 ` Paul Eggert
2017-11-26 5:11 ` Stefan Monnier
2017-11-26 10:27 ` martin rudalics
[not found] ` <jwva7z9rgqh.fsf-monnier+Inbox@gnu.org>
[not found] ` <9d7be625-85ae-54d5-3897-6f701c8ea124@cs.ucla.edu>
[not found] ` <jwvo9npprfw.fsf-monnier+emacs@gnu.org>
2017-12-01 1:03 ` Steve Fink
[not found] <CAOqdjBe98BpWE- Ey8fPY1DmfCiLYnB06d30Xqf_KMm_muvKbDg@mail.gmail.com>
2017-12-01 17:57 ` Steve Fink
2017-12-03 0:37 ` Pip Cet
2017-12-03 5:24 ` Steve Fink
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='CAOqdjBerV-T6gwFN+gT-txsNDAQhzZXTBFERJpx=Vh8dhjtTVw@mail.gmail.com' \
--to=pipcet@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
/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).