Recent changes to issues

#67 Cash not find class koopa.core.parsers.combinators.MatchTree

KrisDS — Sat, 26 May 2018 15:41:08 -0000

status: open --> closed-fixed

#67 Cash not find class koopa.core.parsers.combinators.MatchTree

KrisDS — Sat, 26 May 2018 15:40:48 -0000

Sorry about that. It's been a while since I used svn and I forgot to add those classes in. Should be fixed now.

Cash not find class koopa.core.parsers.combinators.MatchTree

Frank Becker — Sat, 26 May 2018 15:01:38 -0000

After updating to revision 393 I got errors because of the missing class koopa.core.parsers.combinators.MatchTree.

Cash not find class koopa.core.parsers.combinators.MatchTree

Frank Becker — Sat, 26 May 2018 15:01:38 -0000

Ticket 67 has been modified: Cash not find class koopa.core.parsers.combinators.MatchTree
Edited By: KrisDS (kdeschut)
Status updated: u'open' => u'closed-fixed'

COPY REPLACING LEADING produces wrong ast

Frank Becker — Sun, 24 Sep 2017 07:35:04 -0000

When you parse a source with "COPY REPLACING LEADING" you get the following in tne AST for the included line.
<recordDescriptionEntry>
<dataDescriptionEntry>
<levelNumber>
<t><![CDATA[05]]></t>
</levelNumber>
<unknown>
<t><![CDATA[LS-STACK-POINTER]]></t>
<t><![CDATA[ ]]></t>
<t><![CDATA[PIC]]></t>
<t><![CDATA[ ]]></t>
<t><![CDATA[9]]></t>
<t><![CDATA[(]]></t>
<t><![CDATA[4]]></t>
<t><![CDATA[)]]></t>
</unknown>
<t><![CDATA[.]]></t>
</dataDescriptionEntry>
</recordDescriptionEntry>
instead of the correct
<recordDescriptionEntry>
<dataDescriptionEntry>
<levelNumber>
<t><![CDATA[05]]></t>
</levelNumber>
<t><![CDATA[ ]]></t>
<entryName>
<dataName>
<cobolWord>
<t><![CDATA[LS-STACK-POINTER]]></t>
</cobolWord>
</dataName>
</entryName>
<t><![CDATA[ ]]></t>
<pictureClause>
<t><![CDATA[PIC]]></t>
<t><![CDATA[ ]]></t>
<pictureString>
<t><![CDATA[9]]></t>
<t><![CDATA[(]]></t>
<t><![CDATA[4]]></t>
<t><![CDATA[)]]></t>
</pictureString>
</pictureClause>
<unknown/>
<t><![CDATA[.]]></t>
</dataDescriptionEntry>
</recordDescriptionEntry>

#33 MF compiler directives

KrisDS — Wed, 30 Nov 2016 08:00:37 -0000

status: open --> wont-fix

#41 Move support for embedded languages into dedicated grammars

KrisDS — Tue, 29 Nov 2016 15:34:22 -0000

status: open --> closed-fixed

#41 Move support for embedded languages into dedicated grammars

KrisDS — Tue, 29 Nov 2016 15:34:08 -0000

Added syntax in [r384]. E.g.

sql::statement

#65 Spelling of COBOL compilers

KrisDS — Mon, 28 Nov 2016 21:43:02 -0000

It should really just be "Koopa Parser Generator" now, as you can use it for plenty of languages. But the main focus is still COBOL, so I feel it should be in the title. If only so people can find it more easily.

"Koopa" is just a really bad acronym. It went something like "COBOL Parser" to "CO Pa" to "Koopa"... Yeah... I know :-)

I'll fix the spelling as I find it. If someone wants to make a pass and fix it all in one go, I'm happy to accept patches.

Spelling of COBOL compilers

Simon Sobisch — Mon, 28 Nov 2016 19:50:53 -0000

I'd say this is a low-priority issue but wanted to raise it nonetheless. These are the correct spellings

COBOL is COBOL, you are of course free to have "the product" named "Koopa Cobol Parser" instead of "Koopa COBOL Parser" even if the later keeps the acronym (I assume that neither "Koopa" nor "Parser" are acronyms, are they?)
IBM COBOL (IBM COBOL for AIX / IBM Enterprise COBOL)
Micro Focus COBOL
ACUCOBOL-GT (BTW: the GT stands for Graphical Technology, just in case you wonder like I did)
GnuCOBOL (formerly OpenCOBOL - it is fine to have only "GnuCOBOL" in ;-)