[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: misleading error message from variable modifier
From: |
Clark Wang |
Subject: |
Re: misleading error message from variable modifier |
Date: |
Fri, 2 Mar 2018 14:07:30 +0800 |
On Fri, Mar 2, 2018 at 12:37 PM, don fong <dfong@dfong.com> wrote:
> Chet, thanks. in subst.c there is code that looks similar to what i had
> suggested. but i don't see the tests that i submitted. i also don't see
> the change listed in CHANGES?
>
It's in the file CWRU/CWRU.chlog:
2/24
----
subst.c
- parameter_brace_expand_error: add parameter saying whether or not
we are checking whether value is null, so we can have different
error messages for ${x:?} and ${x?}. Report and fix from
don fong <dfong@dfong.com>
- Re: misleading error message from variable modifier, don fong, 2018/03/01
- Re: misleading error message from variable modifier, Chet Ramey, 2018/03/01
- Re: misleading error message from variable modifier, don fong, 2018/03/01
- Re: misleading error message from variable modifier,
Clark Wang <=
- Re: misleading error message from variable modifier, Chet Ramey, 2018/03/02
- Re: misleading error message from variable modifier, don fong, 2018/03/02
- Re: misleading error message from variable modifier, Chet Ramey, 2018/03/04
- Re: misleading error message from variable modifier, don fong, 2018/03/07
- Re: misleading error message from variable modifier, Chet Ramey, 2018/03/08
- Re: misleading error message from variable modifier, don fong, 2018/03/09
- Re: misleading error message from variable modifier, Chet Ramey, 2018/03/10
- Re: misleading error message from variable modifier, Chet Ramey, 2018/03/14
- Re: misleading error message from variable modifier, don fong, 2018/03/17
- Re: misleading error message from variable modifier, Chet Ramey, 2018/03/17