Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

DarkBASIC Professional Discussion / It would be really cool if...

Author
Message
ZomBfied
22
Years of Service
User Offline
Joined: 2nd Oct 2002
Location:
Posted: 4th Jan 2003 22:09
The error messages told you which line the error actually occurred in. But what would be even cooler is when the error is like "(blank) does not exist" it told you which (blank)"

in other words if it could tell you:

File: "c:\game\blabla.x" does not exist
or
Object 69 does not exist
or
Sound 200 does not exist
and so on.

That would be really valuable and save some time and headaches.
MrTAToad
22
Years of Service
User Offline
Joined: 26th Aug 2002
Location: United Kingdom
Posted: 4th Jan 2003 22:10
Yes indeedly

Good news everyone! I really am THAT good...
http://www.nickk.nildram.co.uk/ for great plug-ins - oh my, yes!
jasuk70
22
Years of Service
User Offline
Joined: 3rd Dec 2002
Location: Hemel Hempstead
Posted: 5th Jan 2003 01:50
As well as the Step through mode actually telling you where you really are in a program instead of saying you a next going to execute the middle part of a 3 line comment!
levent
22
Years of Service
User Offline
Joined: 2nd Nov 2002
Location: United States
Posted: 5th Jan 2003 03:41
It would also be nice to trap errors within programs. Statement like, ON ERROR GOTO, ON ERROR GOSUB, ON ERROR <function Name>, as well as manipulating the current error number/string. It would also be extremely useful to throw user defined errors, like, THROW ERROR <num> which could be trapped somewhere in the code.

-levent.
ZomBfied
22
Years of Service
User Offline
Joined: 2nd Oct 2002
Location:
Posted: 5th Jan 2003 05:20
I'd be happy if we just had a little more helpful, more accurate error info.

Rob K
Retired Moderator
22
Years of Service
User Offline
Joined: 10th Sep 2002
Location: Surrey, United Kingdom
Posted: 5th Jan 2003 13:34
It would be nice if DBP could jump to the line and also tell us which source file the error occurred in.

All this error info would add to the size of the exe, but Lee could add the option to build in or leave out Debug info so that we could include it when creating test exes, but leave it out on final release.

NOBODY has a forum name as stupid as Darth Shader. I do.
Kangaroo2
22
Years of Service
User Offline
Joined: 26th Sep 2002
Location: United Kingdom
Posted: 6th Jan 2003 01:01
It would be useful, but I was massively greatful for the improved eroor finding that DBP bring anyway. Its usually fairly obvious what you've done wrong That said sometimes it is really unhelpful

* If the apocalypse comes, email me *
the architect
22
Years of Service
User Offline
Joined: 6th Jan 2003
Location: United Kingdom
Posted: 8th Jan 2003 21:40
It would be lovely if DBPro could actually fix the errors for us and then advise us on better ways to utilise the code or even better, write it for us!!!

MrTAToad
22
Years of Service
User Offline
Joined: 26th Aug 2002
Location: United Kingdom
Posted: 8th Jan 2003 22:02
Thats cheating!

Good news everyone! I really am THAT good...
http://www.nickk.nildram.co.uk/ for great plug-ins - oh my, yes!
The Darthster
22
Years of Service
User Offline
Joined: 25th Sep 2002
Location: United Kingdom
Posted: 8th Jan 2003 23:48
If you use functions, it really messes up the error detection, the errors will be on random lines, sometimes with nothing or comments on, and the errors don't make any sense. It describes the wrong thing, sometimes 'variable is not compatible with this type' or something will come up when I've forgotten to close a loop or something.
rapscaLLion
22
Years of Service
User Offline
Joined: 29th Aug 2002
Location: Canada
Posted: 8th Jan 2003 23:50
It would be cool if DB actually had error reports that gave the correct line, and were actually legible... instead of "#100010: can not perform 'string' cast on type @variable @line 1" you could just say something like: "Error On Line 1: Variable variablenamehere (type, ie- string integer etc) Incompatible with variable2namehere (type)"

Alex Wanuch
aka rapscaLLion
Kousen Dev Progress >> Currently Working On Editors
MrTAToad
22
Years of Service
User Offline
Joined: 26th Aug 2002
Location: United Kingdom
Posted: 9th Jan 2003 00:01
Yes, the error report gets worse with multiple files... this really needs sorting...

Good news everyone! I really am THAT good...
http://www.nickk.nildram.co.uk/ for great plug-ins - oh my, yes!
JamDotNET
22
Years of Service
User Offline
Joined: 15th Jan 2003
Location: United States
Posted: 15th Jan 2003 15:54
What would be great...

Try
<code to attempt>
Catch Ex as Exception
<code to run on error>
<ie. log the Ex description & # or show it somewhere>
Finally
<code to run regardless if error occurred or not
End Try

But maybe I should shut up until I actually get my copy of DBP - LOL

Jam
MrTAToad
22
Years of Service
User Offline
Joined: 26th Aug 2002
Location: United Kingdom
Posted: 15th Jan 2003 17:17
The ON ERROR has been dismissed I think, as being too slow.

Good news everyone! I really am THAT good...
http://www.nickk.nildram.co.uk/ for great plug-ins - oh my, yes!

Login to post a reply

Server time is: 2025-05-18 14:31:40
Your offset time is: 2025-05-18 14:31:40