Pierre Sahores wrote:

> No sure about debugging. Even if the mc debugger is clearly a little poor
> (message path management), we have to remember that the hc debugguer (and, in a
> minus part, the sc debugger) does just half the work the mc debugger does
> because the hc xcmd/xfcn are on the mc side built-in command. I prefer,
> personnaly, more of those best built-in commands than a too perfect debugger,
> acting on just a small commands/functions library. Is that wrong ?

Have you looked at the HyperCard debugger since version 2.3? There are
so many features there that I miss in MetaCard. MC's debugger won't even
let you abort the debugging process on command unless there is an error.
MC won't let you see the full value of a multiple-line variable (!), and
won't let you see the value of the contents of an array. For me, the
ability to see the contents of variables is what debugging is all about.

I would also like a message watcher like HyperCard's. Many problems in
scripts could be easily debugged if the path a message is taking through
the hierarchy were clearly displayed. MetaCard's message hierarchy can
be confusing for people used to other scripting environments,
particularly the way it handles background/group messaging.

SuperCard's debugger allows you to flag a variable so that every time it
occurs in any handler, the debugger will open. That's a feature I wish
MC had too.

The only way to achieve a lot of this functionality is to build the
debugger into the engine rather than maintain it as a scripted stack. I
think functionality would be greatly improved if that happened.
MetaCard's debugger is the most useless of any of the three scripted
environments I have worked with. Such a powerful program needs an
equally powerful debugging tool.

-- 
Jacqueline Landman Gay         |     [EMAIL PROTECTED]
HyperActive Software           |     612-724-1596
Custom hypermedia solutions    |     http://www.hyperactivesw.com

Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.

Reply via email to