I believe in the past there were threads on this issue, and I believe it is the
latter. It makes sense, because as we have seen there can be issues. If you
were to run the stack on Windows, save it and then open it on another platform
again, another recompile would ensue, but if nothing is amiss
Executing the relayer command via a do statement fixed the problem.
For my own eduction, I'd like to know a little more about the "as needed"
compilation Richard mentioned. Does this happen every time a stack is
opened, or only the first time a stack is opened on a different platform
than it was
You're right, that's strange. The first mention I can find of it in either
the dictionary or the release notes is 6.0(DP1).
I think you may have solved the mystery though. I do see relayer in the
commandnames in 5.5.4 on OSX but it's not there on 5.5.0 on Windows which
is where I see the problem
Pete-
Thursday, March 13, 2014, 6:29:11 PM, you wrote:
> As mentioned, it compiles fine on OSX under 5.5.4 even though the relayer
> command doesn't exist in that version.
Actually, it does. Type this in the messagebox:
put "relayer" is among the lines of the commandnames
--
-Mark Wieder
ahs
Pete-
Thursday, March 13, 2014, 6:29:11 PM, you wrote:
> I plan on entering a bug report on this but in the meantime I'm hoping
> someone will come up with a workaround (other than having 2 separate
> version of the stack!) I know some languages have conditional compile
> switches but I don't th
Hi Richard,
The exact line is:
relayer tControlToRelayerID before getLineInfo(pendline+1,"longID")
As mentioned, it compiles fine on OSX under 5.5.4 even though the relayer
command doesn't exist in that version.
After the startup error on Windows, I tried a compile of the script and got
the same
Peter Haworth wrote:
I should add that the code in question shouldn't even be executing during
startup and that the script error window includes the heading "error while
compiling".
Why is any compiling happening at that point? Even if there is a good
reason for it, why does this situation caus
I’m going to hazard a guess and say that when moving from platform to platform,
a stacks scripts get re-compiled for compatibility issues.
Bob
On Mar 13, 2014, at 16:58 , Peter Haworth wrote:
> I have a stack, developed on OSX, that tests which version of LC I'm
> running under and if v6 or
I have a stack, developed on OSX, that tests which version of LC I'm
running under and if v6 or later, executes a relayer command. If less than
v6, some other commands are executed instead since the relayer command
doesn't exist prior to v6.
This has all compiled and worked fine on OSX, even when
