<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 14, 2019, 9:54 AM Peter Dimov <<a href="mailto:pdimov@gmail.com">pdimov@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Tom Honermann wrote:<br>
<br>
> I think we *might* be successful in using "execution encoding" to apply <br>
> to both the compile-time and run-time encodings by extending the term with <br>
> specific qualifiers; e.g., "presumed execution encoding" and <br>
> "run-time/system/native execution encoding".<br>
<br>
This would be implying that there's a single "execution" or "native" <br>
encoding, whereas there are many.<br>
<br>
- encoding used for character literals<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">We are specifically talking about that uniquely and how to refer to that.</div><div dir="auto"><br></div><div dir="auto">Of course such strings will be interpreted with a different encoding to the one they were writing in at compile time - Even if the standard assumes compatibility between how a string is layed out in memory and how it will be interpreted by standard and system provided facilities.</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- what the locale has been set to (at compile time, at run time)<br>
- what file names use, per filesystem, there can be more than one (*)<br>
- what file contents use<br>
- what the console/the terminal uses<br>
<br>
(*) Here "none" (arbitrary NTBS not interpreted as characters by the FS) is <br>
an option<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Probably the only portable option even.</div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
</blockquote></div></div></div>