Pages: 1 2 3 4 5 6 [7] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 23 post(s) |
Sky Grunthor
Minmatar MKS Directorate
|
Posted - 2007.09.21 19:52:00 -
[181]
Originally by: kuromei Edited by: kuromei on 16/09/2007 07:56:37 As a doctorate candidate in computer science and math, I painfully understand how difficult this bug must have been to find. However, leaving open ended conditionals will always be prone to throwing this error. You can never know the full set of values users will pass to them, and therefore refraining from "else {" is logically guarenteed to ensure this problem doesn't cascade, which makes it incredibly easy to prevent and troubleshoot.
It's also one of the downsides with using a nonstrict programming language, which from the error report, you guys obviously are, but honestly the benefits usually outweight the negatives.
Anyway, I appreciate your communication, and your vigilance is solving it. As usual, you guys are the best!
to clarify this.. it has nothing to do with the "Programing Language" they are using in this particular instance (i.e. Stackless Python)... It was database related. Database interactions are their own little (well large) specialty and have their own plethora of problems that occur. MKS Directorate Home
|
James Duar
Merch Industrial GoonSwarm
|
Posted - 2007.09.22 12:42:00 -
[182]
Originally by: Sky Grunthor
Originally by: kuromei Edited by: kuromei on 16/09/2007 07:56:37 As a doctorate candidate in computer science and math, I painfully understand how difficult this bug must have been to find. However, leaving open ended conditionals will always be prone to throwing this error. You can never know the full set of values users will pass to them, and therefore refraining from "else {" is logically guarenteed to ensure this problem doesn't cascade, which makes it incredibly easy to prevent and troubleshoot.
It's also one of the downsides with using a nonstrict programming language, which from the error report, you guys obviously are, but honestly the benefits usually outweight the negatives.
Anyway, I appreciate your communication, and your vigilance is solving it. As usual, you guys are the best!
to clarify this.. it has nothing to do with the "Programing Language" they are using in this particular instance (i.e. Stackless Python)... It was database related. Database interactions are their own little (well large) specialty and have their own plethora of problems that occur.
No it was a database issue being caused by the way a routine in the programming language was being handled, which I think was his point.
He wasn't ragging on Python, so much as commenting on the tendency of people to use generic "everything else" handlers, which are fine mostly but best practice would be to know exactly every value your routine will get.
|
Amarus
Minmatar Dinky Core Miners
|
Posted - 2007.09.26 23:18:00 -
[183]
Has there been any news on what solution CCP plan to offer alliances affected by this problem? Total silence isn't helping.
|
|
|
|
Pages: 1 2 3 4 5 6 [7] :: one page |
First page | Previous page | Next page | Last page |