unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Rocky Bernstein <rocky@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: A couple of things that I think should be in byte bytecode meta comments
Date: Fri, 22 Dec 2017 12:55:15 -0500	[thread overview]
Message-ID: <CANCp2gaHO4E=jdjzchBUQwd8Y8V-fXOcP-PjXkotYNx8M3Ti3g@mail.gmail.com> (raw)
In-Reply-To: <CANCp2gYZJUJxwnP8PJoa2=C9h-Gra5a2VqdDkW8rxd--aL2Nrg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 497 bytes --]

I mean file path or file name, not the file contents.

On Fri, Dec 22, 2017 at 12:54 PM, Rocky Bernstein <rocky@gnu.org> wrote:

> The file from which the bytecode was compiled from.
>
> A SHA of the source code that the compilation came from. That way one can
> be more confident that this bytecode file goes with this particular source
> code and not another file with the same name.  If the SHA is too
> computationally expensive, then a checksum or even size of the file might
> be helpful.
>

[-- Attachment #2: Type: text/html, Size: 820 bytes --]

  reply	other threads:[~2017-12-22 17:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22 17:54 A couple of things that I think should be in byte bytecode meta comments Rocky Bernstein
2017-12-22 17:55 ` Rocky Bernstein [this message]
2017-12-22 18:30   ` Eli Zaretskii
2017-12-22 18:49     ` Rocky Bernstein
2017-12-22 20:25       ` Eli Zaretskii
2017-12-22 20:55         ` Rocky Bernstein
2017-12-23  8:25           ` Eli Zaretskii
2017-12-23  8:44             ` Rocky Bernstein
2017-12-23 15:32               ` Robert Weiner
2017-12-23 17:16                 ` Rocky Bernstein
2017-12-23 18:30                   ` Robert Weiner
2017-12-24  2:44                     ` Rocky Bernstein
2018-01-13 19:44                       ` Thien-Thi Nguyen
2017-12-22 21:27 ` Andreas Schwab
2017-12-22 21:43   ` Rocky Bernstein
2017-12-23  8:25     ` Andreas Schwab
2017-12-23  8:35       ` Rocky Bernstein

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='CANCp2gaHO4E=jdjzchBUQwd8Y8V-fXOcP-PjXkotYNx8M3Ti3g@mail.gmail.com' \
    --to=rocky@gnu.org \
    --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).