[Top][All Lists]

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

Re: error message for missing fi is not helpful

From: Manuel Reiter
Subject: Re: error message for missing fi is not helpful
Date: Fri, 14 Sep 2018 16:26:14 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0

On 13.09.2018 04:29, L A Walsh wrote:
This isn't *exactly* what you wanted, but this gives the line number
of the last unmatched statement (but doesn't tell you what the statement
was).  The diff was against bash-4.4.23 (4.4 base w/23 patches)

Thank you for taking the time to look into this! There seems to be a problem with your code though: if word_top is zero and EOF_Reached is true, you set msg to msg0 without initializing msg0 first.

Reviving the code you commented out (your first attempt?) I came to the attached result. I also added if/fi to the compound commands tracked by word_top. There are probably others that I have missed missed.

Anyway, if you store the word in a separate array where the line #
is stored, you _could_ list the matching word, but I suspect just the
line it started on would be enough for most users.

I totally agree with that.

Thanks and best regards,


Attachment: parse.y.diff
Description: Text Data

reply via email to

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