Menu
▾
▴
[netrexx-pipelines] NetRexx/Pipelines compile / ANT problem
|
From: Jeff H. <Je...@Je...> - 2020-12-04 21:25:22
|
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I am having a problem with "something" in the NetRexx/Pipelines
compile routines. And I have no idea where, much less any
solution.</p>
<p>I have written a stage DISPLAY, which compiles and works nicely.
But it uses both <b>addpipe</b> and <b>callpipe</b>. In order
to compile it, using <font face="monospace">pipc</font>, I can
not use <b>nrx</b> as the file extension -- it balks at the "<span
style="color:#CCCCCC;background-color:#012456;">*in0:</span>"
with "<span style="color:#CCCCCC;background-color:#012456;">Error:
Unexpected character found in source: ':' (hexadecimal encoding:
003A)</span>"--, but compiles when the same file has a <b>njp</b>
extension. From display.njp, the compiled <b>class</b> file
works just fine as a stage in a pipe, either from the command line
or in another <b>njp</b> file.</p>
<p>But the usual <font face="monospace">java -jar
ant/ant-launcher.jar compile</font> ignores the <b>njp</b>
file.</p>
<p>So for an immediate workaround, how can I get the ANT to see the
njp-file?</p>
<p>Possibly longer term, can we get the compiler work with either
file type?</p>
<p>This is the code the compiler does not like when it is in a
nrx-file:</p>
<blockquote>
<p> <font face="monospace"> callpipe (display_stage debug 0 )<br>
<br>
*in0: |<br>
fo: fanout |<br>
tag {tag} |<br>
literal {title} |<br>
literal {style} |<br>
diskw {fname} ?<br>
cmd {fname} ?<br>
fo: |<br>
*out0:</font><br>
</p>
</blockquote>
<p>Thanks for any help,</p>
<p>Jeff<br>
</p>
<p><br>
</p>
<p><br>
</p>
</body>
</html>
|
