Re: RFE: Please allow unicode ID chars in identifiers

"Every technical field -- and most nontechnical fields -- has developed conventional shorthand notation to make convenient the presentation and discussion involving frequently used concepts. For example, because of long acquaintance, x+y*z is clearer to us than multiply y by z

Re: RFE: Please allow unicode ID chars in identifiers

On Sat, 2017-06-03 at 01:20 -0700, L A Walsh wrote: > Some conventions regarding character set usage have already been "solved" > and encoded in binary properties of the characters.  For example, the > start and continue "ID" properties are best associated with names used > for variables.  Referrin

Re: RFE: Please allow unicode ID chars in identifiers

On 04/06/2560 01:00, George wrote: > There's a series of trade-offs between keeping the implementation relatively > simple vs. supporting equivalency where the user may reasonably expect > it. I will personally never use non-ascii in a bash script, even though I use unicode extensively, also in th

Re: Builtin read with -n0 or -N0 (nchars == 0) behaves as a read with no -n/-N argument

Hello, Sorry for the late reply. My solution is to change *line 294* of builtins/read.def. Change if (code == 0 || *intval < 0* || intval != (int)intval) to if (code == 0 || i*ntval <= 0* || intval != (int)intval) Command: ./bash -c 'read -n0 <<< "abc";declare -p REPLY' Output: ./bash: line

Re: RFE: Please allow unicode ID chars in identifiers

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? Still curious

Re: RFE: Please allow unicode ID chars in identifiers

On Sat, Jun 3, 2017 at 4:48 PM, 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 >>> >> >

Re: RFE: Please allow unicode ID chars in identifiers

John McKown wrote: On Sat, Jun 3, 2017 at 4:48 PM, 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. So

Re: RFE: Please allow unicode ID chars in identifiers

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 d

Re: Builtin read with -n0 or -N0 (nchars == 0) behaves as a read with no -n/-N argument

On Sun, Jun 04, 2017 at 01:45:42AM +0530, Pranav Deshpande wrote: [...] > My solution is to change *line 294* of builtins/read.def. > > Change > if (code == 0 || *intval < 0* || intval != (int)intval) > > to > > if (code == 0 || i*ntval <= 0* || intval != (int)intval) [...] > Is this solution o

Re: Builtin read with -n0 or -N0 (nchars == 0) behaves as a read with no -n/-N argument

Is that more advantageous? On Sun, Jun 4, 2017 at 10:46 AM, dualbus wrote: > On Sun, Jun 04, 2017 at 01:45:42AM +0530, Pranav Deshpande wrote: > [...] > > My solution is to change *line 294* of builtins/read.def. > > > > Change > > if (code == 0 || *intval < 0* || intval != (int)intval) > > > >

Re: Builtin read with -n0 or -N0 (nchars == 0) behaves as a read with no -n/-N argument

On Sun, Jun 4, 2017 at 12:16 AM, dualbus wrote: [...] > Although there's a problem with the solution: > > dualbus@debian:~$ for sh in bash ~/src/gnu/bash-build/bash ksh93 mksh; do > $sh -c ': | read -n 0; echo $?'; done > 1 > 0 > 1 > 1 > > Since the read(2) system call doesn't take plac