Nikita,
On Apr 9, 2015 8:56 AM, "Nikita Popov" wrote:
>
> On Thu, Apr 9, 2015 at 12:33 PM, Niklas Keller wrote:
>
> > Hi Nikita,
> >
> > I like the new display format, but there's one thing I miss. If you
> > replace the exception name for warnings and fatals, how does a user know
> > which exce
On 09/04/15 13:55, Nikita Popov wrote:
>> I like the new display format, but there's one thing I miss. If you
>> > replace the exception name for warnings and fatals, how does a user know
>> > which exception he has to catch?
> Sorry, I don't understand what you mean here. The first part of the me
On Thu, Apr 9, 2015 at 12:33 PM, Niklas Keller wrote:
> Hi Nikita,
>
> I like the new display format, but there's one thing I miss. If you
> replace the exception name for warnings and fatals, how does a user know
> which exception he has to catch?
>
> Regards, Niklas
>
Sorry, I don't understand
Am 09.04.2015 10:04 schrieb "Nikita Popov" :
>
> New message:
>
> UnexpectedValueException: Failed to open directory "" in %s on line %d
>...
> Essentially exceptions would display like ordinary error, but with "Fatal
> error" / "Warning" / ... replaced by the exception name, and showing a
> stack
Hi Nikita,
I like the new display format, but there's one thing I miss. If you replace
the exception name for warnings and fatals, how does a user know which
exception he has to catch?
Regards, Niklas
Nikita Popov schrieb am Do., 09.04.2015, 10:04:
> Hi internals!
>
> A lot of people have been
Hi internals!
A lot of people have been confused about engine exceptions currently
displaying as normal fatal errors (if they aren't caught). We'll have to
change this to use exception messages.
Before doing this I'd like to clean up the messages a bit to make them more
friendly for CLI usage. Cu
