script wizard and assert()

[LETARTARE]

hello,
in the Squirrel 3.0 reference manuel found :

assert(exp)
throws an exception if exp is null

is that this function is available in the wizard scripts ?

if not, how to raise an exception in a wizard script?

thank you.

[oBFusCATed]

As far as I know we're still using squirrel 2.x, so you have to check its manual.

[LETARTARE]

thank you for the answer.

Squirrel 2.2  is identical ...

assert(exp)
throws an exception if exp is null

[oBFusCATed]

OK. Have you tried it?
What do you expect to happen?
Who is going to catch it?

[LETARTARE]

OK. Have you tried it?

yes with my configuration

What do you expect to happen?

crash Code::Blocks !!!

Who is going to catch it?

I do not know, this is why I ask questions?

[oBFusCATed]

crash Code::Blocks !!!

Why?
But I'm sure it won't happen, probably you'll get an error in the log or it will be silently ignored.

[LETARTARE]

I think I misunderstood

What do you expect to happen?

in fact, this is what happened during the test

Code

local board = null;
assert(board)

This exception should be recovered by "Code::Blocks" to notify the user ?
This is not the case.

[oBFusCATed]

I don't understand sorry. Please explain better or provide a sample script.

[ollydbg]

Code

local board = null;
assert(board)

This exception should be recovered by "Code::Blocks" to notify the user ?

I tried the code in "Scripting console", there will pop an error message box, and no crash of C::B.

Welcome to the script console!
> local board = null;
> assert(board)

AN ERROR HAS OCCURED [the index 'board' does not exist]

CALLSTACK
*FUNCTION [main()] ScriptConsole line [1]

LOCALS
[this] TABLE

AN ERROR HAS OCCURED [the index 'board' does not exist]

CALLSTACK
*FUNCTION [main()] ScriptConsole line [1]

LOCALS
[this] TABLE

[ollydbg]

If I add the code in a project wizard script, then I see a message box said: script error has occurred, please press yes to see the exact errors.

Then I click Yes, there will be a dialog to show the detailed error messages. Still no crash of C::B.

[LETARTARE]

@ollydbg
thank you very much for taking the time to check these two lines of code.

So I try on the other machine with the same configuration, and I confirm your results: we get the warning messages.

I incriminates my first PC, I'll check.

Thank you again for the constructive responses