[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Lua strictlessness
- From: Robert Virding <robert.virding@...>
- Date: Thu, 29 Aug 2013 20:28:17 +0200 (CEST)
"The same way you handle errors today" would be my reply. You can have errors today in your code which the parser/compiler must handle, even in embedded systems, this would be logical place to handle warnings as well.
----- Original Message -----
> From: "Luiz Henrique de Figueiredo" <email@example.com>
> To: "Lua mailing list" <firstname.lastname@example.org>
> Sent: Thursday, 29 August, 2013 4:16:01 PM
> Subject: Re: Lua strictlessness
> > So I think at least the compiler should at least warn by default, with an
> > option to keep quiet. Preferably disallow it.
> How do you propose to handle warnings in a embedded language? The Lua
> parser cannot emit warnings to stdout or stderr because these files may
> not even exist or be visible. Moreover, it'd be impolite to trample on
> the host's output. So, should the parser maintain a list of warnings for
> the host to check? What can the host do about them?