FreeBasic Wish list

[Frobozz]

Actually I thought of a neat feature, make ON ERROR do more than GOTO. Example:

Code:

On Error Print "Error found"

or

Code:

On Error Call ErrorHandler()

Or you could just make it a block like:

Code:

On Error
  Print "Error found"
  Call ErrorHandler()
End On Error

Make the block one is a little overkill, but the others would be nice.

[Dinosaur]

Now I am the expert on Error handling.
Part of my wish list is that either
1. Give me Resume Next
or

2. Tell me where I can find the Addr of the last line executed

In pds I read the map file and tell the operator of my machines
Error Number
Module Number
Line Number
File current during Error

But believe me, that took months of Codeview traces.

Regards

[Badjas]

Classes??? way too complicated to implement to put on a wishlist. Perhaps in like version 5 eh? Now I think of it, could IDE's make up for the 'lack' of classes? Ability to group code that operates on a typed var... I think that's for developers the most helpful feature. Keeping code managable. The language must stay basic imho (though pointers is a necesary addition). If the sugestion of IDE help isn't enough, then you probably talk about inheritance. But then you also must think of virtual and abstract methods stuff.

I agree that the error handling in BASIC does suck hard. try-catch blocks just make more sense. But ehm.. I won't put this on a wish list just yet. I don't know how easy it is to make this. And what others think about it.

And I think AND and OR operators are more readable than || and && operators. But .. that's a typical holy war source isn't it.

[Frobozz]

Classes are not as difficult to implement as you think they are. When it boils down to it classes are really implemented by the parser used to translate the language. Once translated, a program may not have the appearance of classes at all.

When a class is processed by the parser, it sets records into it's memory consisting of various bits of info. For example, it will remember if it is public, private, etc. When the parser encounters an attempt to set a value on an object's variable, it will check if whatever is attempting to set the value has the permissions to do so. If it has the correct permissions, it will compile it in. If not, it will report an error message.

Once compiled, permissions aren't actually in existance. All permissions are implemented by the compiler alone. Data in a class could be implemented as easily as a TYPE is implemented. :wink:

[barok]

It's open source, so why don't you put in classes yourself?