PL/I Subset G: Parsing

"I'm working on a compiler and runtime library for PL/I Subset G (henceforth just G). I intend to support the ANSI X3.74-1987 standard with a bare minimum of extensions. Compatibility with other PL/I compilers is not intended. The compiler will be open source; the library will be under the MIT license and will include existing components such as decNumber and #LMDB needed by G."

https://www.reddit.com/r/ProgrammingLanguages/comments/1re3ndx/pli_subset_g_parsing/

I wonder what's up with resurrecting dead programming languages recently. Reminded me of the Algol-68 frontend for gcc that someone else recently posted.

Has anyone done a modern implementation of BCPL yet?

@hyc I'm happily getting into Ada and will try to use it for infra work. ☺️

@monospace is Ada dead? I thought it was still the default language for DoD projects.

@hyc SNOBOL?

@martyh hm I remember writing SNOBOL on the mainframe back at UMich. But strings are pretty fully supported by most languages today

@hyc I wonder why PL/I ANSI Subset G of 1987 "requires" LMDB. Seems fishy to me.

@martyh yeah I was wondering that too. Didn't think it had built in DB support. Unlike COBOL.

@hyc we should crowdfund Bill Joy to bang one out in a weekend

@martyh turns out, it's not entirely unlike COBOL.

"Because PL/I provides indexed sequential files for which I want to use #LMDB,"

https://www.reddit.com/r/ProgrammingLanguages/comments/1riew0c/comment/o89rjd8/

@wouter @hyc In 1973 there were two or three PL/I compilers (E/F and the Checkout Compiler) plus the systems development variant, initially BSL then renamed to PL/S. The theory was "One Language to Rule Them All" or some such ... we've seen how that plan works out.