how to understand the string returned by try/catch block.

Mark Schonewille m.schonewille at economy-x-talk.com
Sun Oct 22 05:16:59 EDT 2006


Hi André,

There is a shareware library available from Ecoomy-x-Talk, which  
translates the errors returned by the try control structure. The  
library also provides a way to write errors to a log file on disk. It  
even works if your stack is password protected. You can find more  
information in the developers section at <http://economy-x-talk.com>.

This is how it translates the error you posted:

Type: Chunk (can't find stack)
Object name: card id 1002
Line:(row 81 col 2)
Hint:

Type: Chunk (can't find object)
Object name: card id 1002
Line:(row 81 col 2)
Hint:

Type: get (error in expression)
Object name: card id 1002
Line:(row 81 col 1)
Hint:

Type: Handler (error in statement)
Object name: card id 1002
Line:(row 81 col 1)
Hint: getCountriesForm

Type: Objec (Name:)
Object name: card id 1002
Line:(row 0 col 0)
Hint: stack "script"

Type: Function (error in function handler)
Object name: card id 1002
Line:(row 31 col 36)
Hint: getCountriesForm


Best,

Mark

--

Economy-x-Talk
Consultancy and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Get your store on-line within minutes with Salery Web Store software.  
Download at http://www.salery.biz

Op 22-okt-2006, om 6:40 heeft Andre Garzia het volgende geschreven:

> Friends,
>
> when using a try/catch block to pick errors, I usually see stuff  
> like this in the errorStatement:
>
> 91,81,2
> 77,81,2
> 223,81,1
> 241,81,1,getCountriesForm
> 353,0,0,stack "script"
> 219,31,36,getCountriesForm
> 499,31,1
> 253,27,1
>
> Does anyone know how to make sense of it? For example I know that  
> stack "script" means the revolution script that I am using for CGI.  
> I also know that the second item of each line is a line number  
> since function getCountriesForm is on line 81 and it is called on  
> line 31 (when the thing explodes). I can't make sense of the first  
> item of each line or the third. I though it might be char number,  
> but it ain't because there's nothing special in char 36 of line 31....
>
> can anyone tell me more about it? This is what I could grok on my own.
>
> Andre




More information about the Use-livecode mailing list