1  |   Order by index

Nov 7, 2000, 2:02pm

(applies to X1.exe 2.9999950 and Av99Bot/SrvcXlgBot 1.66, which will be
available soon)

Dear xelagot script makers (and users),

The next version of xelagot applies strict rules to scripts, enforcing many
of the currently legal syntax laws. Some illegal constructions, which work
up to now, will cause the script to abort. This enforcement is needed to be
able to catch and stop recursive and circular calls (which can cause a stack
overflow killing the application), and loops which do not return control to
the application (causing it to freeze). The new syntax control checks Main,
Event, Sub and Text boundaries

The most common error is a Goto pointing to a label outside its own Sub,
Event or Main. In the following example, the statement Goto OneA in Sub One
is legal, but the same statement in Sub Two is not legal (but worked).

Sub One
... code
IfInt %r > 1 Goto OneA
... code
EndSub
Label OneA
... code
EndSub

Sub Two
... code
IfInt %r > 1 Goto OneA
... code
EndSub

Another less common error is a ResetTo pointing to a label outside the Main
part of the script.

If you think your scripts may be defective, when you upgrade install the new
X1.exe in a COPY of the bot's current directory (so that the settings are
preserved) and test and eventually fix your scripts first.

Notice that X1.exe will produce error messages on screen, so this
facilitates debugging your script. Some errors are trapped during script
initialisation, others (like Goto errors) at runtime.

For more details, see http://www.imatowns.com/xelagot/xlgaserrors.html

Nov 7, 2000, 5:19pm

Not to argue about it, I will have to fix many programs as I point at gotos
outside of the subs a lot, but why is this being done?

Not complaining, my scripts will be cleaner I guess, but I just wondered why we
are suddenly jumping to stricter conventions in language....


[View Quote] > (applies to X1.exe 2.9999950 and Av99Bot/SrvcXlgBot 1.66, which will be
> available soon)
>
> Dear xelagot script makers (and users),
>
> The next version of xelagot applies strict rules to scripts, enforcing many
> of the currently legal syntax laws. Some illegal constructions, which work
> up to now, will cause the script to abort. This enforcement is needed to be
> able to catch and stop recursive and circular calls (which can cause a stack
> overflow killing the application), and loops which do not return control to
> the application (causing it to freeze). The new syntax control checks Main,
> Event, Sub and Text boundaries
>
> The most common error is a Goto pointing to a label outside its own Sub,
> Event or Main. In the following example, the statement Goto OneA in Sub One
> is legal, but the same statement in Sub Two is not legal (but worked).
>
> Sub One
> ... code
> IfInt %r > 1 Goto OneA
> ... code
> EndSub
> Label OneA
> ... code
> EndSub
>
> Sub Two
> ... code
> IfInt %r > 1 Goto OneA
> ... code
> EndSub
>
> Another less common error is a ResetTo pointing to a label outside the Main
> part of the script.
>
> If you think your scripts may be defective, when you upgrade install the new
> X1.exe in a COPY of the bot's current directory (so that the settings are
> preserved) and test and eventually fix your scripts first.
>
> Notice that X1.exe will produce error messages on screen, so this
> facilitates debugging your script. Some errors are trapped during script
> initialisation, others (like Goto errors) at runtime.
>
> For more details, see http://www.imatowns.com/xelagot/xlgaserrors.html

Nov 7, 2000, 5:36pm

duh......nevermind....I re-read Alex's reasons.... I have had that problem, and
cleaned a lot up.. still have a bit to re-do though.


[View Quote] > Not to argue about it, I will have to fix many programs as I point at gotos
> outside of the subs a lot, but why is this being done?
>
> Not complaining, my scripts will be cleaner I guess, but I just wondered why we
> are suddenly jumping to stricter conventions in language....
>
[View Quote]

Nov 9, 2000, 8:05pm

[View Quote] XelaG

Nov 14, 2000, 8:29pm

Yikes.... 19 proggies later I can relax....LOL
You did us a GREAT favor though with the interface....
It gave the error, and line number, saved a lot of bug hunting.
thanx Alex ))
Bought time this mess of mine stopped chewing my ram up....LOL

[View Quote] > (applies to X1.exe 2.9999950 and Av99Bot/SrvcXlgBot 1.66, which will be
> available soon)
>
> Dear xelagot script makers (and users),
>
> The next version of xelagot applies strict rules to scripts, enforcing many
> of the currently legal syntax laws. Some illegal constructions, which work
> up to now, will cause the script to abort. This enforcement is needed to be
> able to catch and stop recursive and circular calls (which can cause a stack
> overflow killing the application), and loops which do not return control to
> the application (causing it to freeze). The new syntax control checks Main,
> Event, Sub and Text boundaries
>
> The most common error is a Goto pointing to a label outside its own Sub,
> Event or Main. In the following example, the statement Goto OneA in Sub One
> is legal, but the same statement in Sub Two is not legal (but worked).
>
> Sub One
> ... code
> IfInt %r > 1 Goto OneA
> ... code
> EndSub
> Label OneA
> ... code
> EndSub
>
> Sub Two
> ... code
> IfInt %r > 1 Goto OneA
> ... code
> EndSub
>
> Another less common error is a ResetTo pointing to a label outside the Main
> part of the script.
>
> If you think your scripts may be defective, when you upgrade install the new
> X1.exe in a COPY of the bot's current directory (so that the settings are
> preserved) and test and eventually fix your scripts first.
>
> Notice that X1.exe will produce error messages on screen, so this
> facilitates debugging your script. Some errors are trapped during script
> initialisation, others (like Goto errors) at runtime.
>
> For more details, see http://www.imatowns.com/xelagot/xlgaserrors.html

Nov 15, 2000, 5:09pm

Well LOL, 'bout chewing ram... 2.9999952 fixes a problem introduced
probably a couple of months ago: the Server software in xelagots, av99bots,
srvcxlgbots and the stand-alone versions, even if it was not being used, was
very slowly but surely chewing up memory (memory leak). This bug has now
been fixed in all bots and servers.

XelaG.

[View Quote]

1  |   Order by index