1.

Solve : pause / wait?

Answer»

Quote

im reinventing the wheel

How do you suppose to do that.Quote from: BatchFileCommand on JANUARY 12, 2009, 04:34:22 PM
Quote
im reinventing the wheel

How do you suppose to do that.

because it's been done before. i'll see if i cant whip up something, this time it will have a more throurgh debugging to avoid another bug REPORT Quote
this time it will have a more throurgh debugging to avoid another bug report

I've tried it with pure batch files (78 kb!) I've tried. Even with measly 4 kb, there's always going to spell errors or some kind of problem with administrator access etc. you TALKING about FINFO?Quote from: BatchFileCommand on January 13, 2009, 04:58:04 PM
Quote
this time it will have a more throurgh debugging to avoid another bug report

I've tried it with pure batch files (78 kb!) I've tried. Even with measly 4 kb, there's always going to spell errors or some kind of problem with administrator access etc.


If you use a compiled language like VB.NET,VB6, VCPP, or various others... you cannot even compile the program if it has misspellings. Unless of course the typo is still a valid symbol.Quote


If you use a compiled language like VB.NET,VB6, VCPP, or various others... you cannot even compile the program if it has misspellings. Unless of course the typo is still a valid symbol.

That is one thing I don't like about that though.
Quote from: BatchFileCommand on January 14, 2009, 04:43:23 PM
Quote


If you use a compiled language like VB.NET,VB6, VCPP, or various others... you cannot even compile the program if it has misspellings. Unless of course the typo is still a valid symbol.

That is one thing I don't like about that though.


yeah, it's MUCH better if it crashes with a syntax error on the victim... I mean, clients machine. much more professional.

if there are parts of the program that are only executed in extreme conditions, and there is an syntax error... you wouldn't even know until those "extreme conditions" are satisfied. and with 72 PAGES of batch code, there will be a LOT of unexplored code paths just waiting to throw a interpreter error.thats why its smart to seperate the batch programs.


Discussion

No Comment Found