From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 66261@debbugs.gnu.org
Subject: bug#66261: Disassembling a regexp's bytecode
Date: Fri, 29 Sep 2023 19:24:39 +0300 [thread overview]
Message-ID: <83msx5x7zs.fsf@gnu.org> (raw)
In-Reply-To: <jwva5t580k2.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 29 Sep 2023 11:47:50 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 66261@debbugs.gnu.org
> Date: Fri, 29 Sep 2023 11:47:50 -0400
>
> >> - First, in order to easily use the same code between REGEX_EMACS_DEBUG
> >> and my new `re--describe-compiled`, I need to print sometimes to
> >> `stderr` and sometimes to a string, which I do using `open_memstream`.
> >> AFAIK `open_memstream` is not directly available in Windows (and
> >> maybe under some other Unixes either, tho it's in POSIX-2008, IIUC).
> >> Could someone help me get an `opem_memstream` emulation working
> >> (maybe via gnulib)?
> > Gnulib doesn't have such an emulation, AFAICT.
> > Why cannot you fall back to temporary files when open_memstream is not
> > available?
>
> Doesn't seem worth the trouble (and I must admit that the idea of using
> a temp file hurts my sense of aesthetics, on top of it 😀. Tho, it'd be
> OK if it were done for me by gnulib).
Then just let it write to stderr, it's okay to do that in
ENABLE_CHECKING code.
next prev parent reply other threads:[~2023-09-29 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 2:28 bug#66261: Disassembling a regexp's bytecode Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-29 15:06 ` Eli Zaretskii
2023-09-29 15:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-29 16:24 ` Eli Zaretskii [this message]
2023-09-29 16:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-29 18:56 ` Stefan Monnier 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=83msx5x7zs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66261@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).