[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Patch for unicode in varnames...

From: PePa
Subject: Re: Patch for unicode in varnames...
Date: Tue, 6 Jun 2017 21:40:31 +0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1

On 06/06/2560 21:20, Greg Wooledge wrote:
> Scripts that can only *run* in a UTF-8 encoding-locale are a bad idea.

Even currently, when functions in a bash script are beyond ASCII, they
can still be run anywhere. I would imagine it would be the same when
variable names are also allowed to be in some unicode encoding.

Editing them might be more difficult -- even when your editor renders
the script correctly, as the names might not make sense to you. It might
help people with other native languages though.

The net loss to you is less than the potential gains for people that
want it. And remember, function names could already be in a strange
script..! There is a precedent, and it would make sense to enhance the
support to those that desire it.

But I don't think you need to be too afraid, I've never encountered a
bash script with function names in non-ASCII characters. (But who knows,
in some domains that we would not very easily encounter it is already


reply via email to

[Prev in Thread] Current Thread [Next in Thread]