On Fri, 7 Jun 2019 10:48:52 +0200, Jiri Malak <
malak...@gmail.com>
wrote:
>I don't think the simple solution.
>Because line is divided before it is processed by scan_scr().
>It will require much deeper change and appropriate code is shared by
>multiple logical part as GML tag processing etc.
It is my understanding that Frank Beythien followed the documented
procedure in the Reference Manual 8.1 Processing Rules, as modified by
actual experience, and the documentation of control word .cw in the
script-tso, in relevant part:
"If substitution (.SU) of Set Symbols is ON and the input line is a
control-word line, the substitution scan will terminate at the
first control word separator. The remainder of the line will be
substituted when it is processed later as an input line."
This pretty much means that the behavior you observed is "correct"
insofar as the documentation goes. What you have discovered is a
deviation from the documented behavior on the part of wgml 4.0.
Diving briefly into this code, which I have made a few modifications
to, but not very many, I noticed a "ProcFlags.CW_sep_ignore" which, if
it were set when a symbol evaluation has been identified early enough
in the process, might solve the problem. Or not, as the case may be.
But, no, like most of these problems, the solution is /not/ to tear
out large chunks of code and start over. The solution is to find
/where the problem is/ and /fix it/. And the fix itself is usually
fairly simple; the hard part is figuring how to do it.
I have no doubt that, once wgml is stable (does all the docs correctly
and works properly within the build system), some, many, or all of the
various subsystems could do with being torn out and rewritten.
Preferably after thinking about it a bit. I have several such possible
projects in mind myself, for some of my early decisions have produced
some incredibly obtuse code. But not unti wgml is stable, so that
regressions can be caught easily and fixed.
>Anyway it is used in all Error Description documents as wccerrs.gml,
>wpperrs.gml etc.
Then it will have to be dealt with when I get to those documents, if
you don't want to do it now. I can't blame you for not wanting to;
figuring out what to change and where to change is likely to be rather
harder than other problems I have encountered.
>Dne 7.6.2019 v 3:06 Paul S Person napsal(a):
>> On Thu, 06 Jun 2019 17:30:23 -0700, Paul S Person
>> <pspe...@ix.netcom.invalid> wrote:
>>
>> The last line in this paragraph:
>>
>>> But there is hope: while wgml 4.0 accepts your example and puts "test"
>>> in both symbols (.ty is your friend!), if you don't change the control
>>> word separator but simply use it you get an error:
>>
>> should have been
>>
>>> word separator but simply use it in the symbol in place of "$", you get an error: