Re: Refresh of XyWWWeb.U2 v119 (15 September 2006)

[Carl Distefano cld@xxxxxxxx]

Reply to note from Harry Binswanger  Sat, 16 Sep
2006 18:19:00 -0400

> And the error message makes sense to me: shouldn't it be SV not
> SX?

No, it should -- indeed, MUST -- be SX. SV is for strings. SX is
for interpreted expressions. A concatenation -- such as
++ or, what amounts to the same thing,
"""+@UPR()+""" -- is an expression requiring interpretation.
Hence, SX.

The problem with your snippet is in "@UPR()". ""
presumes that S/G 50 has content (or, at a minimum, is initialized
()). In frame CallOrGo*, this condition is always satisfied,
because the whole operation is senseless unless the user supplies an
argument ([d:\path\]filename), which is passed via S/G 50. In your
disembodied snippet, S/G 50 is uninitialized. Hence, it bombs.

When you run the snippet with RUNCODE, S/G 50 is
initialized, fortuitously, by frame PrsCMline (which is launched
when you hit ). Hence, it works.

Make sense?

--
Carl Distefano
cld@xxxxxxxx