Re: [Mumps2Py:] Working Fix: "handle a case causing an infinite loop."

[Patrick Gallot <pgallot@xxxxxxxxxxxx>]

Hi Frank,
Based on what you've sent me,
I suspect that most of the remaining parsing problems  are not "old 
style" code - meaning from an older version of Mumps,
but code using "implementation-specific" non-standard variants.

For example $system.subvar is not a standard Mumps construct,
neither is the G.varname construct passed in via the 
implementation-specific $ZK() function.

(per the mumps standard, all commands and intrinsic functions, and 
variables starting with "z" are reserved for implementation-specific)

Regards,
-Patrick

Frank Guder wrote:
> Hi Patrick,
>
> thanks for the quick fix! It works.
>
> It "seems" (we have to check the output carefully to be sure) as if most of
> the parsing errors come from the "old style" routines (typically 199x as
> date) in our file. The customer written parts are parsed very well.
> I will update you as soon as we have our first analysis (that is, GXL-graph
> of the whole thing).
>
> Best regards,
> Frank
>
>
> -----Ursprüngliche Nachricht-----
> Von: Listengine [mailto:listengine@xxxxxxxxxxxxxxxxx] Im Auftrag von
> subversion@xxxxxxxxxxxxx
> Gesendet: Dienstag, 11. März 2008 15:08
> An: discuss@xxxxxxxxxxxxxxxxxx
> Betreff: [Mumps2Py:] [168] handle a case causing an infinite loop.
>
> Revision: 168
> Author:   pgallot
> Date:     2008-03-11 14:07:52 +0000 (Tue, 11 Mar 2008)
>
> Log Message:
> -----------
> handle a case causing an infinite loop.
>
> Modified Paths:
> --------------
>     trunk/mumps2py/mumps2tok.py
>
>
>
>
> ---
>
>
>   


---