lua-users home
lua-l archive

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


Great Sean Conner said that.
>Not very well.  They kept going, but the errors accumulated so you would
>get a cascade of errors.
Yes, a cascade of errors may report.
What about modifying the code of Lua and letting it use the same
method to report multiple errors like C/C++ (after a complete
complication)?

Thanks to all of you.
On Wed, Jan 27, 2021 at 9:42 AM Sean Conner <sean@conman.org> wrote:
>
> It was thus said that the Great 孙世龙 sunshilong once stated:
> > Gé Weijers, Thank you for your detailed explanation.
> > My understanding of this question is at a different level with your
> > generous help.
> >
> > I agree with what all you said indeed.
> >
> > I still have a question, how C/C++ achieve this goal (i.e. reporting
> > multiple errors after running a compilation)?
>
>   Not very well.  They kept going, but the errors accumulated so you would
> get a cascade of errors.  A minor example:
>
> src/callbacks.c: In function `handle_aflinks':
> src/callbacks.c:707: error: syntax error before "char"
> src/callbacks.c:705: warning: empty body in an if-statement
> src/callbacks.c: At top level:
> src/callbacks.c:724: error: syntax error before '}' token
> make: *** [src/callbacks.o] Error 1
>
>   Two errors, one warning.  The actual error?  A missing opening '{'.  The
> conventional wisdom was to ignore all reported errors except for the first
> one.
>
>   -spc