{"id":6648,"date":"2022-09-04T10:53:09","date_gmt":"2022-09-04T05:23:09","guid":{"rendered":"https:\/\/jassweb.com\/solved\/solved-c-how-can-a-pointer-overwrite-a-local-const-block-of-memory-but-not-the-global-const-block-of-memory\/"},"modified":"2022-09-04T10:53:09","modified_gmt":"2022-09-04T05:23:09","slug":"solved-c-how-can-a-pointer-overwrite-a-local-const-block-of-memory-but-not-the-global-const-block-of-memory","status":"publish","type":"post","link":"https:\/\/jassweb.com\/solved\/solved-c-how-can-a-pointer-overwrite-a-local-const-block-of-memory-but-not-the-global-const-block-of-memory\/","title":{"rendered":"[Solved] C – How can a pointer overwrite a local const block of memory but not the global const block of memory?"},"content":{"rendered":"

[ad_1]
\n<\/p>\n

\n
\n
<\/div>\n
\n
\n

It is completely up to the implementation. For example, const<\/code> data on bare metal ARM uCs is stored in the FLASH memory. You can write to there but it will have no effect at all.<\/p>\n

Hosted systems will behave differently depending on the OS, its version and hardware.<\/p>\n

How can I overwrite a const block of memory<\/code><\/strong><\/em> simply if you want to write do not declare it const<\/code>. If you do respect the promise given to the compiler.<\/p>\n

If it is just curiosity of the beginner, there is no other way than experimenting. Experiment, debug and try to interpret the result.<\/p>\n

EDIT.<\/p>\n

In most common implementations:<\/p>\n