From: Mark H Weaver <mhw@netris.org>
To: guile-devel@gnu.org
Subject: Scanning for coding declarations in all files (not just source)
Date: Sun, 13 Jan 2013 13:25:40 -0500 [thread overview]
Message-ID: <87zk0dq6sb.fsf@tines.lan> (raw)
I just discovered that Guile is scanning for coding declarations in
*all* files opened with 'open-file', not just source files.
For source files, we are scanning for coding declarations twice: once
when when the file is opened, and a second time when 'compile-file' or
'primitive-load' explicitly scans for it.
The relevant commit is 211683cc5c99542dfb6e2a33f7cb8c1f9abbc702.
I was unable to find any discussion of this on guile-devel.
I don't like this. I don't want 'open-file' to second-guess the
encoding I have asked for in my program, based on data in the file.
Also, the manual is misleading. Section 6.17.8 gives the impression
that the scanning is only done for source files.
What do other people think?
Mark
next reply other threads:[~2013-01-13 18:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 18:25 Mark H Weaver [this message]
2013-01-13 19:51 ` Scanning for coding declarations in all files (not just source) Mike Gran
2013-01-15 9:32 ` Ludovic Courtès
2013-01-22 11:38 ` Andy Wingo
2013-01-31 5:06 ` [PATCH] Do not scan for coding declarations in open-file Mark H Weaver
2013-01-31 10:00 ` Andy Wingo
2013-01-31 18:58 ` Mark H Weaver
2013-01-31 20:04 ` Andy Wingo
2013-01-31 22:00 ` Ludovic Courtès
2013-01-31 22:19 ` Noah Lavine
2013-01-31 21:51 ` Ludovic Courtès
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zk0dq6sb.fsf@tines.lan \
--to=mhw@netris.org \
--cc=guile-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.
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).