std library hooks

[Manu]

On 15 April 2012 08:56, Nick Sabalausky <SeeWebsiteToContactMe at semitwist.com
> wrote:

> "Manu" <turkeyman at gmail.com> wrote in message
> news:mailman.1717.1334400919.4860.digitalmars-d at puremagic.com...
> >
> > Indeed, but I also want to produce some log output. A dialog box is nice
> > too, so artists can choose to 'ignore' and programmers can 'debug'.
> >
>
> I keep flip-flopping on this.
>
> At first, I was going to reply and say "No, allowing 'ignore' is bad
> because
> it just means continuing to work within a corrupted state. Only bad things
> can come from that."
>
> Then I realized, "If the artist had a bunch of unsaved work when the error
> occurred, it's possible the state might still be good enough for them to
> save their work. No point in denying them that for the sake of purity. If
> it
> results in a corrupted save, well...they *are* using version control,
> aren't
> they?"
>
> But my current thought now is: Shouldn't there just be some sort of
> journaling or auto-save or some such? That would eliminate the need, and
> temptation, to work through a corrupted state.
>
> No doubt I'll flip-flop again...
>

The reason more often than not, is that an assert may affect some
individual system fatally, and that system will fail, but the artist simply
doesn't care about that thing (it's most likely experimental and not ready
for them to use anyway). It's usually good practise for the programmer to
write code in such a way that a colossal failure in his new experimental
system doesn't bring the whole game down if it crashes. The artist just
wants to run around and see that his new work is correct when put in
context in-game.
So they are usually not DOING work (that they risk losing) with the crashed
(but survived) game engine, they are typically just testing their work on
context. So if the prior assert's invalid state starts creeping and does
bring down the whole thing, they won't lose any work, just a little time an
patience :)

It's not unusual to see artists persisting with a buggy build of the game,
booting, clicking through 20 assert messages, then finally to a point where
it stops complaining and they can see their work, potentially while half
the world is broken around them :)
It's not worth wasting a programmers time in this case, so they don't.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20120415/ea38ba63/attachment.html>