Oops. Got that last post wrong (whats up with including bra-kets ?)
That's just reminded me of a question that got redirected to me from our Japenese customers, who asked what "Aieeeee !!!!! Can't contact license manager !" was about. Even more alarmingly, apart from the fact that the guys somehow knew it was one of mine, was this warning message was in the piece of code launching Netscape and had nothing to do with anything remotely licensed. Damn, ever have had one of those days. Still my favourite from us, however, was the Error Message That Shouldn't Be In Released Code when the graphics got zoomed out too much, just said "cockup in scale calcs" - nuff said
>blushknew it was one of mine, was this warning message was in the piece of code launching Netscape and had nothing to do with anything remotely licensed. Damn, ever have had one of those days. Still my favourite from us, however, was the Error Message That Shouldn't Be In Released Code when the graphics got zoomed out too much, just said "cockup in scale calcs" - nuff said
Used to see this 'bug' many times from our beloved developers on NT passing over stuff for the Un*x builds. Basically, have to train them to realise that a text file is not a valid text file if it doesn't have a terminating newline.... classic example is 'Parse file with file names in (with sed,perl,whatever), do something with each file'
Guess what.. nothing gets done with the last file if there's no terminating newline and all hell breaks loose further on down the line.
Guess this is really a feature, possibly a mis-feature. Is also a good way to get Windows developers to look at the damn output of their parsers ! (eventually:)
Slashdot Mirror
Oops. Got that last post wrong (whats up with including bra-kets ?)
That's just reminded me of a question that got redirected to me from our Japenese customers, who asked what "Aieeeee !!!!! Can't contact license manager !" was about. Even more alarmingly, apart from the fact that the guys somehow knew it was one of mine, was this warning message was in the piece of code launching Netscape and had nothing to do with anything remotely licensed. Damn, ever have had one of those days.
Still my favourite from us, however, was the Error Message That Shouldn't Be In Released Code when the graphics got zoomed out too much, just said "cockup in scale calcs" - nuff said
>blushknew it was one of mine, was this warning message was in the piece of code launching Netscape and had nothing to do with anything remotely licensed. Damn, ever have had one of those days.
Still my favourite from us, however, was the Error Message That Shouldn't Be In Released Code when the graphics got zoomed out too much, just said "cockup in scale calcs" - nuff said
Used to see this 'bug' many times from our beloved developers on NT passing over stuff for the Un*x builds. Basically, have to train them to realise that a text file is not a valid text file if it doesn't have a terminating newline.... classic example is 'Parse file with file names in (with sed,perl,whatever), do something with each file'
:)
Guess what.. nothing gets done with the last file if there's no terminating newline and all hell breaks loose further on down the line.
Guess this is really a feature, possibly a mis-feature. Is also a good way to get Windows developers to look at the damn output of their parsers ! (eventually