Stack name conflicts resolved?

Richard Gaskin ambassador at
Mon Nov 7 10:00:36 EST 2016

Ben Rubinstein wrote:

 > Currently if I understand it correctly there are issues which seem
 > just too hard to fix: so instead
 > - the most egregious
 > of these issues - was 'fixed' by adding the check that Richard's
 > trying to remove.

In all fairness, I'm not *trying* to remove it, but have in fact removed 
it - in my own copy of the IDE.

As I noted in this post, I've not closed #1061 because I recognize that 
the IDE has different responsibilities beyond those of our own apps:

I'm just glad to find that the rule for looking up stacks by name built 
into the engine is simple, understandable, and very useful.

We can have confidence that our standalones, which don't include 
IDE-specific code, will allow stacks of the same name to run without 
issue according to a fairly simple search rule.

This means that I can have a classroom of students sharing stacks 
without having to impose all sorts of complicated schemes to ensure that 
stack names are unique.

For standalones, the engine behavior is beautifully elegant.

But I do recognize that the IDE has a special role with special 
responsibilities, and have left my original enhancement request open as 
we explore ways to address that, hopefully arriving at a middle ground 
which provides confidence about which stack we're working on while also 
giving us the freedom to use stacks as easily as the engine allows.

  Richard Gaskin
  Fourth World Systems
  Software Design and Development for the Desktop, Mobile, and the Web
  Ambassador at      

More information about the Use-livecode mailing list