GNU bug report logs - #54433
29.0.50; Invalid read syntax: "#<" with async-bytecomp

Previous Next

Full log

View this message in rfc822 format

From: Thierry Volpiatto <thievol <at> posteo.net>
To: Alan Mackenzie <acm <at> muc.de>
Cc: Michael Heerdegen <michael_heerdegen <at> web.de>, 54433 <at> debbugs.gnu.org
Subject: bug#54433: 29.0.50; Invalid read syntax: "#<" with async-bytecomp
Date: Sat, 19 Mar 2022 06:17:36 +0000

[Message part 1 (text/plain, inline)]

Hello Alan,

Alan Mackenzie <acm <at> muc.de> writes:

> I think that all the byte-* variables are connected with byte
> compilation.  But I also think that they are (?nearly?) all internal
> variables, so it shouldn't be needed to copy them to an aynchronous
> thread (?or process?).

Thanks to confirm this.

>> > Maybe any variables with "--" in their symbols should be filtered out
>> > of the copying operation.
>
>> Name space problem, byte-* vars and functions have no fixed prefix (not
>> always).
>  
> OK.  I think you're saying that there are other variables with "--" that
> you _do_ need to copy.

No, not anymore. Wanted to say that if needed it is harder to catch foo--,
foo-this--, foo-else-this-- etc... instead of just foo--.

> Well, we're back in communication again.  :-)  I've heard good things
> about posteo.

Yes, works great :-)

Thanks.

-- 
Thierry

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.