Reply to Re: DinkC Validator public beta
If you don't have an account, just leave the password field blank.
c) My DinkC is already beyond the level to make the mistakes your program finds. It wouldn't prove very useful to me.
OK, now that is bullshoot. True and sincere bullshoot. Don't get me wrong, you're probably a good coder. But saying that you never make mistakes is total bullshoot. I tested my program on some the original Dink scripts and quite a few of SOB's scripts, and in both cases, I found many errors. I don't suppose you're going to tell me that SimonK is not yet "beyond the level to make the mistakes my program finds" because his scripts contains errors my program found, while your scripts certainly would not contain such errors?
It's as easy as forgetting the & at the start of a variable or forgetting to enclose your strings with a " in both ends, or perhaps forgetting a } at the end of a long list of ifs and elses, and whatnot. It doesn't take much do make a mistake. SOB (or perhaps it was the original Dink) had some instances of "freeeze" where it should've said "freeze", e.g. Hard to see with the naked eye, but my program will immediately kick your butt for it.
OK, now that is bullshoot. True and sincere bullshoot. Don't get me wrong, you're probably a good coder. But saying that you never make mistakes is total bullshoot. I tested my program on some the original Dink scripts and quite a few of SOB's scripts, and in both cases, I found many errors. I don't suppose you're going to tell me that SimonK is not yet "beyond the level to make the mistakes my program finds" because his scripts contains errors my program found, while your scripts certainly would not contain such errors?

It's as easy as forgetting the & at the start of a variable or forgetting to enclose your strings with a " in both ends, or perhaps forgetting a } at the end of a long list of ifs and elses, and whatnot. It doesn't take much do make a mistake. SOB (or perhaps it was the original Dink) had some instances of "freeeze" where it should've said "freeze", e.g. Hard to see with the naked eye, but my program will immediately kick your butt for it.