Skip to main content
↑
↓
Spherical forums
Community for the
Sphere game engine
New?
Contact Us
to register an account!
1 Hour
1 Day
1 Week
1 Month
Forever
Community
Help
Search
Recent Posts
Log in
Contact Us
News
Spherical
Facebook
-
Twitter
-
Discord chat
New?
Contact us
to register an account!
Sphere Development
Engine Development
Sphere 1.x error behavior
1
Print
Topic: Sphere 1.x error behavior
(Read 4649 times)
previous topic
-
next topic
0 Members and 1 Guest are viewing this topic.
Fat Cerberus
Big Chungus
Posts: 2,774
*MUNCH*
Logged
Global Moderator
Sphere Developer
Sphere 1.x error behavior
December 03, 2016, 11:15:08 am
In the process of assessing minisphere backwards compatibility, I found out that Sphere 1.x is quite misbehaved when certain kinds of errors occur.
If one does this in Sphere 1.5:
Code: (javascript)
[Select]
try { LoadImage("nonexistent"); }
catch(e) { }
It produces an uncatchable error and terminates the engine, bypassing the try/catch entirely. This is not really desirable behavior: I don't think I'll emulate that particular quirk.
neoSphere 5.9.2
-
neoSphere
engine -
Cell
compiler -
SSj
debugger
forum thread
|
on GitHub
Radnen
Big Chungus
Posts: 1,440
Sphere Studio Developer
Logged
Senior Staff
Wise Warrior
Re: Sphere 1.x error behavior
Reply #1
–
December 04, 2016, 12:11:58 am
Oh man this has messed me up many times. Many resource and other functions do indeed quit without throwing an error. I've wrapped my game in a try catch block to catch anything, but many times it just fails flat.
If you use code to help you code you can use less code to code. Also, I have approximate knowledge of many things.
Sphere-sfml
here
Sphere Studio editor
here
1
Print
Sphere Development
Engine Development
Sphere 1.x error behavior