Brian Milby wrote:
> Clone stack avoids the check. It is not that hard to get
> multiple stacks with the same short name but different
> long names in memory (in a standalone).
Clone alters the name of the new clone stack. The engine prepends it
with "Copy of ".
AFAIK it's done that since 1998.
FWIW I did some extensive research on duplicate stack names issues about
four years ago, attempting to pin down how the engine behaves and what
the IDE does.
https://quality.livecode.com/show_bug.cgi?id=1061#c20
TL/DR: The engine has no problem with duplicate short stack names, but
some IDE needs will be compromised until there is an adjustment to how
the engine internally resolves short stack name references;
Currently the old MC implementation remains in place in which those are
resolved by load order (which is almost never what any scripter needs),
but more useful would be layer/message path order (which is what most
scripts and esp IDE tools need).
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
[email protected] http://www.FourthWorld.com
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
