cjw at eml.cc
Sat Jan 15 21:49:29 EST 2011
I did this somewhat, but the idea of matching errors with error messages is certainly wise.
Sent from my Verizon Wireless BlackBerry
From: Jim Ault <jimaultwins at yahoo.com>
Sender: use-livecode-bounces at lists.runrev.com
Date: Sat, 15 Jan 2011 18:38:19
To: How to use LiveCode<use-livecode at lists.runrev.com>
Reply-To: How to use LiveCode <use-livecode at lists.runrev.com>
Subject: Re: Line Hint
Try creating know errors, then observe the error reporting.
Start with small scripts, misspell, mis-reference, etc to get a feel
On Jan 15, 2011, at 5:17 PM, Calvin Waterbury wrote:
> We have a winner!
> Boy! do I feel like a schmolez!
> Thanks for the clarification, Jeff.
>> Jeffrey Massung <mailto:massung at gmail.com>
>> Saturday, January 15, 2011 7:12 PM
>> Well, "line hint" isn't really accurate, because aren't they two
>> separate items? So "line" would be the line # the error occurred on
>> and "hint" would be something like "Field 'hoohaw' doesn't exist,"
>> I haven't done hardly anything with error decoding in LC, but that
>> would make sense to me.
>> Jeff M.
>> Calvin Waterbury <mailto:cjw at eml.cc>
>> Saturday, January 15, 2011 6:41 PM
>> Hi David C.,
>> Nope. I'm referring to the "Errors" window when something flubs.
>> It says on the left side of that dialog...
>> I know this is an error message, but does "line hint" mean anything
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode