Ah, that would explain it. I don't think either Francis or I are currently using<br>the new preprocessing code at all. Currently we mainly use cheap for XML<br>RMRS ^_^ One day I would like to put together a nice test set for cheap so
<br>that we can catch this kind of stuff earlier.<br><br>Eric<br><br><div><span class="gmail_quote">On 11/6/06, <b class="gmail_sendername">Ben Waldron</b> <<a href="mailto:bmw20@cl.cam.ac.uk">bmw20@cl.cam.ac.uk</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Eric Nichols wrote:<br>> Are PPCRE functions currently being used in PET? If not, that would
<br>> explain why<br>> this problem wasn't noticed earlier. Even if the change does cause the<br>> linker to<br>> favor rmrs over PPCRE, this still doesn't sound like a permanent<br>> solution. I think<br>> I will continue to persue a solution on the ECL/PET side of things.
<br>I don't know why the problem wasn't noticed (or perhaps didn't occur?)<br>earlier. PPCRE is used heavily in the preprocessor (activated via<br>"-tok=fsr"). I don't use PET regularly, but when I last tested it with
<br>RMRS output (in the process of integrating the FSR preprocessor) I<br>didn't observe the current problem. Most people will be using an<br>official PET release, which will be older than the contents of the<br>current SVN...
<br><br>Note also that something is broken in the current ERG with respect to<br>cfrom/cto on EPs (the values get lost, at least when running under the<br>LKB). I have no idea if this is relevant...<br><br>- Ben<br></blockquote>
</div><br><br clear="all"><br>-- <br>--Eric Nichols