PureBasic Forums - English

I had completely forgotten about this forum. I dumped PureBasic 3 years ago and moved on to another development environment.

@Bitblazer

Try/Catch deals with system errors quite well in other languages.

Sounds like you either need to make sure your hardware never fails...

Perhaps I should ask Harry Potter to wave his magic wand and make that happen.

This is my last post on this particular thread. It's going nowhere.

@freak

I am not sure I am being hostile. In fact, I am quite jovial but I feel others have been hostile to me for asking about a means structured error handling.

I understand why so many of you don't want to use it, and I've heard all the arguments before. However, if you don't want a particular ...

So, in your bubble:

- memory can't become corrupted by a power surge (not power outage) while running the software?
- hard disk drives never fail while using your software?
- networks/internet never fail while using your software?
- motherboards/communications ports never fizzle while using your ...

@mk-soft

This is some thorough and useful knowledge to have. And you are correct... I should have started a new thread with my question.

I greatly appreciate the information!.!.!

@box_80

Mostly, it was just a curiosity. But PB is beginning to become as addictive for me as coffee. I would at some point like to probe the minds of the PB masters to learn the proper way to dispose of/clean up each type of variable and objects. It's one of my pet peaves. Even in languages which ...

Very interesting conversation!

Regarding kenmo's statement -

#Null$ does not remove a variable from existence, just resets its value, so EnableExplicit won't complain.

Just out of pure curiosity, does PB have a keyword or method to remove variables from existence?

He is entitled to his own opinion.

This argument is invalid, as a memory leak would occur in a language without garbage collection if the programmer doesn't manualy clean up/dispose of the object regardless of whether he is using OnErrorGoto(), Try/Catch/Endtry, or no error handling mechanism at all. Your examples have nothing to do ...

I'm confused...

If you don't want to use such a feature, that is okay. But WHY are you so adamant against myself and others who have mentioned it seeking to find a way to properly implement it? What does it hurt you? I cannot think of one possible reason why someone else developing a feature you ...

You and others keep saying this. So, I'm just going to ignore you and those who share your opinion from this point.
If you don't like the feature I mention, life is simple... don't use it and leave others alone who might want it.

It's not for you. But thanks for your input.

This Try/Catch error handling structure by Danilo https://www.purebasic.fr/english/viewtopic.php?t=49903 works very well at continuing with the program's execution following an un expected error. Yet, unfortunately, it doesn't seem accommodate any means I can see to extract either the error number ...

Okay, after a year and a half away I am picking this puppy (PureBasic) back up.

The main issue I have when tinkering with PB is that the built-in error handler exits after an unexpected error occurs, even though sometimes it may not be a critical error. I know this won't be changed, as I have read ...

@Marc56us

Thank you, Sir!

That was very lacking on my part to not think to look in among the operators...

Update: > I just found I can download a PDF version of the PB manual. It's a bit more searchable than the online version.

@Olliv

Olliv wrote:Houla...

2 remarks...

1) Please use normalized markups

I deeply apologize. Despite having programmed for 30+ years (in other languages), this is my first time ever using an online forum. So, please forgive my slowness at learning the proper protocol for doing things.