panic() -- An assert that isn't compiled out
fatal() -- some configuration parameter caused a problem
Ok, I thought so. Do we want to keep these names? I will promise
that I have learned finally, but the names seem a bit to synonymous to
me. I will go through my code and convert the proper
On May 28, 2008, at 11:23 AM, nathan binkert wrote:
panic() -- An assert that isn't compiled out
fatal() -- some configuration parameter caused a problem
Ok, I thought so. Do we want to keep these names? I will promise
that I have learned finally, but the names seem a bit to synonymous to
I've always remembered it as the simulator panicking when something
unexpected happens, definitely not including user error, and fatal is
the other one. I almost always use panic because I don't deal with user
input and configuration that much, although putting in more of that is
part of what
I don't know if it's worth spending time adding more indirection to the
error path so python can print an error. If the error is fatal python isn't
going to be able to correct it and continue.
I don't plan to make it part of the standard run, but I plan to make
it either something that happens
