Re: How much do we care about undefined behavior triggered by invalid bytecode?

[Philipp Stephani <p.stephani2@gmail.com>]

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

Noam Postavsky <npostavs@gmail.com> schrieb am Di., 22. Mai 2018 um
15:42 Uhr:

> On 22 May 2018 at 09:31, Philipp Stephani <p.stephani2@gmail.com> wrote:
> > It's pretty easy to find examples of (printed representations of) invalid
> > bytecode that trigger C-level assertions or undefined behavior
> ("crashes").
> > Should these be reported as bugs, or do we assume that any bytecode
> object
> > is valid?
>
> The latter, according to the manual (elisp) Byte-Code Objects:
>
>    You should not try to come up with the elements for a byte-code
> function yourself, because if they are inconsistent, Emacs may crash
> when you call the function.  Always leave it to the byte compiler to
> create these objects; it makes the elements consistent (we hope).
>

That refers only to calling bytecode objects, not to e.g. reading their
printed representation. Would it also apply to reading or other forms of
handling bytecode objects? If so, the documentation should say so.

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