Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Luc Newsgroups: comp.lang.tcl Subject: Re: Tcl9: source files are interpreted as utf-8 by default Date: Fri, 10 Jan 2025 16:29:44 -0300 Organization: A noiseless patient Spider Lines: 18 Message-ID: <20250110162944.366c7ef2@lud1.home> References: <20250108113519.42eb3746@lud1.home> <20250108114254.7f56f049@lud1.home> <20250108124055.15c92a05@lud1.home> <20250108162339.7c04023e@lud1.home> <20250108172312.253b829c@lud1.home> <20250109143836.3b0ed7bb@lud1.home> <20250110005353.1b9b9d43@lud1.home> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Injection-Date: Fri, 10 Jan 2025 20:29:45 +0100 (CET) Injection-Info: dont-email.me; posting-host="e55446f85fa17a0cd4fb59aa289d63df"; logging-data="226173"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19AuaUEqTi04qihdDBpRMgm7g6exHVcUlI=" Cancel-Lock: sha1:fdHEp+ba0UI1DHQ+eaJSTfcn9Gg= Bytes: 1910 On Fri, 10 Jan 2025 06:38:02 +0000, eric wrote: >> The 8.6 way is wiser. >Not sure... your choice of encoding may not be the one of your >application users. >In this case, your code may fail to load in the user's encoding choice. ************************** The user's choice is and always will be a point of uncertainty. Tcl9 introduces an additional uncertainty with the developer. -- Luc >>