Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.std.c
Subject: Re: Add @ to basic character set?
Date: Sat, 10 Jul 2021 08:46:23 -0700
Organization: A noiseless patient Spider
Lines: 23
Message-ID: <86zguu894g.fsf@linuxsc.com>
References: <rqfeip$lrr$1@solani.org> <s2e3av$429$1@solani.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader02.eternal-september.org; posting-host="e13df7ffef68eec8a0b0a92150d2f271"; logging-data="2695"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18zfWoeDCHRzl1JscQbzP2LcY80ZtcDT/E="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:H47nUAlIRE6PsRYATefbE2PGshs= sha1:ZaWdBk0Bf1dj3b5BTAEKyv65Ca8=
Xref: csiph.com comp.std.c:6263

Philipp Klaus Krause <pkk@spth.de> writes:

> Am 05.12.20 um 08:58 schrieb Philipp Klaus Krause:
>
>> I wonder if it would make sense to add @ to the basic character set.
>> Virtually everyone is using it in comments and strings already anyway
>> (for email addresses), and I don't see anything preventing
>> implementations from supporting it, as it is available in both ASCII and
>> common EBCDIC code pages:
>>
>> http://www.colecovision.eu/stuff/proposal-basic-@.html
>
> After some discussion and thought, IMO, the way forward is to add @ to
> the source and execution character sets, but not the basic source
> character set:
>
> http://www.colecovision.eu/stuff/proposal-@.html
>
> Do you think this proposal makes sense as is?  If yes, do you have a
> preference for adding them as single bytes vs. not specifying if they
> are single bytes?  If yes, why?

I would vote against the proposal, because it does nothing useful.