A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://lists.gnu.org/archive/html/emacs-devel/2022-11/msg01329.html below:

Re: scratch/comp-static-data 5aa3db2f11: comp: Add support for compiling

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] From: Eli Zaretskii Subject: Re: scratch/comp-static-data 5aa3db2f11: comp: Add support for compiling elisp constants into static data. Date: Sun, 20 Nov 2022 09:37:27 +0200 
> From: Richard Stallman <rms@gnu.org>
> Cc: vibhavp@gmail.com, akrl@sdf.org, luangruo@yahoo.com,
>       emacs-devel@gnu.org
> Date: Sat, 19 Nov 2022 20:15:33 -0500
> 
>   > I'm not aware of any aspect of the change which would cause crashes in
>   > these cases.
> 
> It is possible I misunderstood what the change was for.  The message
> seemed to say that it would put the values of variables defined with
> `defconst' into read-only memory.  If there are cases in which that
> affects the program's execution, I expect it will cause a failure of
> some sort in those same cases.

I'd need to understand what does "read-only memory" mean in this context.
Does the code use some memory-protection capabilities to enforce that?  Or
does it do something else?

Vibhav, please chime in and help us understand what the code does.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4