bug-bash
[Top][All Lists]
Advanced

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

Re: RFE: Please allow unicode ID chars in identifiers


From: Greg Wooledge
Subject: Re: RFE: Please allow unicode ID chars in identifiers
Date: Mon, 5 Jun 2017 08:14:08 -0400
User-agent: Mutt/1.4.2.3i

On Sun, Jun 04, 2017 at 09:20:45AM +0700, Peter & Kelly Passchier wrote:
> On 04/06/2560 04:48, L A Walsh wrote:
> >> Greg Wooledge wrote:
> >>> Here is a demonstration of the cost of what you are proposing.  In my
> >>> mail user agent, your variable shows up as L??v.
> >>>
> >>> Source code with your UTF-8 identifiers would no longer even be
> >>> READABLE  
> >>
> >> What display/OS do you have that you can't run UTF-8 on?
> 
> So it's his mail client: reading unicode source in their old mail client
> is going to be problematic for some people...

imadev:~$ uname -a
HP-UX imadev B.10.20 A 9000/785 2008897791 two-user license

imadev:~$ ls -lt /usr/bin | tail -1
-r-xr-xr-x   1 bin        bin          12288 May 30  1996 from

It's the system on which I run my email MUA (mutt) and my IRC client.
It's also the NIS slave server for this floor (subnet).  It's also
where I put the squid proxy that all the Debian systems use for
apt-get.

Up until a few months ago, when our legacy Perforce server died, it
was also where I did all the development for an in-house Tcl (mostly)
application.  Having absolutely no intention of attempting to replace
Perforce with another Perforce, I simply took the existing checkout
(Perforce calls it a "client") that I already had, copied it over to
the Debian half of my dual-boot Debian/Windows system, and made a git
repository out of it.  (Compiling git for HP-UX 10.20 did not sound like
a fun thing to do, with all that https and stuff that it seems to want.)

This is the pace at which changes happen out here in the real world.



reply via email to

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