End Point Blog: President of UN General Assembly Thanks End Point

The President of UN General Assembly, Peter Thomson, thanked End Point for supporting the Ocean Conference, which was held at the United Nations Headquarters this past summer to bring attention and action to saving the world’s oceans.

End Point’s Liquid Galaxy helped bring to life “Reconnecting Humanity to the Sea,” an exhibition meant to showcase the beauty of the ocean and the challenges it faces today. End Point created the presentation’s content and showcased it at the conference.

“We were very pleased to see End Point’s Liquid Galaxy used to promote a hopeful future for the world’s oceans. It’s very satisfying to see our technology used to make an important story that much more compelling.”

Rick Peltzman
End Point, CEO

This UN press release explains more about the conference and its results:
“UN Ocean Conference wraps up with actions to restore ocean health, protect marine life”

See the letter:

End Point Blog: Using GitHub for Blog Comments

Last Saturday, November 11, we rolled out a new website that we’ve been working on for a few months. Part of this update was moving from Blogger as our blogging platform to static HTML generated by Middleman. We were more than happy to move away from Blogger for a variety of reasons, including its lack of HTTPS support for custom domains and how difficult it was to keep its templating and styling up to date with our main website. We were also able to move from http://blog.endpoint.com to https://www.endpoint.com/blog.

The most obvious thing that is missing from Middleman’s blog extension is the lack of a commenting system. After exploring some options for comments, we settled on using GitHub issues and comments, inspired by Don Williamson’s post about doing the same thing. It’s a bit of an unconventional approach, so this post will explain how to use our commenting system and how we implemented it.

Commenting requires a GitHub account, which is easy to sign up for and free, and the general target audience of our blog will often already have a GitHub account. At the bottom of each post will be a link to a GitHub issue at the top of the list of comments, if there are any. Click on the issue, write and post your comment, and it’ll appear on the blog post when you reload the page. It’s pretty simple.

Now, for the gritty details. Don’s post shows the JavaScript he uses to find the correct GitHub issue and fetch its comments, but it required a bit of modification to work in our Middleman project. First, we needed a way to get the right GitHub issue number. Don’s example has that worked into the JavaScript with Hugo, fetching it from some parameter value, but I opted to create a hidden input on the page that would provide the right number:

<input type="hidden" name="gh_issue" value="<%= current_page.data.gh_issue_number =>">

Or in HAML:

%input{type: "hidden", name: "gh_issue", value: current_page.data.gh_issue_number}

And we can fetch that value with jQuery:

var issue_id = $('[name="gh_issue"]').val();

From there, we just had to modify the IDs referenced in Don’s JavaScript to match ours, and comments were working perfectly! Well, new comments were.

Our blog is over 9 years old now, with over 1,300 posts and comments on many of those, and we needed to pull those existing comments over into GitHub as well. Actually copying the data wasn’t too difficult. I wrote a simple Python script to use the Blogger API to fetch posts and their comments, sort them by date, create an appropriately-named GitHub issue, and add the comments to them. Aside from GitHub’s anti-abuse detection system getting in the way a few times, it was an easy process.

We wanted to preserve original author and timestamp information, so I had my script prepend the comment body with that information in a code block so it could be easily read by people reading comments on GitHub and parsed by JavaScript:

original author: ...
date: ...

To parse that out, I wrote a quick and dirty regex that runs if I’m the user who created the comment:

if (data.user.login == "phinjensen") {
  var regex = /^```\r?\noriginal author: ([^\r\n]+)\r?\ndate: ([^\r\n]+)\r?\n```/;
  var info = data.body.match(regex);
  if (info) {
    author_name = info[1];
    date = new Date(info[2]);
    data.body_html = data.body_html.replace(/^<pre><code>.+\r?\n.+\r?\n<\/code><\/pre>/, '');
  }
}

If that regex isn’t matched, then the author and date data is left as-is and parsed as normal. Here’s the full JavaScript we’re using:

function formatDate(date) {
  var monthNames = [
    "January", "February", "March",
    "April", "May", "June", "July",
    "August", "September", "October",
    "November", "December"
  ];

  var day = date.getDate();
  var monthIndex = date.getMonth();
  var year = date.getFullYear();

  return monthNames[monthIndex] + ' ' + day + ', ' + year;
}

$(document).ready(function () {
    var issue_id = $('[name="gh_issue"]').val();
    var url = "https://github.com/EndPointCorp/end-point-blog/issues/" + issue_id
    var api_url = "https://api.github.com/repos/EndPointCorp/end-point-blog/issues/" + issue_id + "/comments"

  $.ajax(api_url, {
    headers: { Accept: "application/vnd.github.v3.full+json" },
    dataType: "json",
    success: function(comments) {
      $(".comments").append("Visit the <b><a href='" + url + "'>GitHub Issue</a></b> to comment on this post.");
      $.each(comments, function(i, data) {
        var date, author_name;

        if (data.user.login == "phinjensen") {
          var regex = /^```\r?\noriginal author: ([^\r\n]+)\r?\ndate: ([^\r\n]+)\r?\n```/;
          var info = data.body.match(regex);
          if (info) {
            author_name = info[1];
            date = new Date(info[2]);
            data.body_html = data.body_html.replace(/^<pre><code>.+\r?\n.+\r?\n<\/code><\/pre>/, '');
          }
        }
        if (!date) {
          date = new Date(data.created_at);
        }

        var $comment = $("<div/>", {'class': 'comment'});
        if (!author_name) {
          $comment.append($("<img/>", {
            'src': data.user.avatar_url,
            'class': 'avatar-image'
          }));
        }
        var $body = $("<div/>", {'class': 'comment-body'});
        var $header = $("<span/>", {'class': 'comment-header'});

        if (author_name) {
          $header.append(author_name);
        } else {
          $header.append($("<a/>", {'href': data.user.html_url, 'text': data.user.login}));
        }
        $header.append(" commented on " + formatDate(date));
        $body.append($header);
        $body.append($("<div>" + data.body_html + "</div>", {'class': 'comment-body',}));
        $comment.append($body);
        $(".comments").append($comment);
      });
    },
    error: function() {
      $(".comments").append("Comments are not open for this post yet.");
    }
  });
});

Huge thanks to Don Williamson for sharing his implementation of this idea! If you have any feedback for us and how we’re doing it, let us know in the comments!

Perl Foundation News: Grant Extension Approved: Tony Cook's maintaining Perl 5 Grant

Tony Cook recently requested an extension of his Maintaining the Perl 5 Grant.

I'm pleased to announce that the Board of Directors approved extension of another $20,000. It'll allow him to dedicate another 400 hours to this work.

I would like to thank the community members who took time to comment on this grant extension request and our sponsors who made funding the grant possible through our Perl 5 Core Maintenance Fund. For the fund status, please also see P5CMF running out of funds.

I also appreciate Tony Cook, who publishes regular progress report on his work.

Sawyer X: Perl 5 Porters Mailing List Summary: November 2nd-12th

Hey everyone,

Following is the p5p (Perl 5 Porters) mailing list summary for the past week and a half.

Enjoy!

November 2nd-12th

News and Updates

If your company uses Perl 5 and would like to contribute to show support and to assure its sustained maintenance and development, The Perl Foundation is looking for more donations to the Perl 5 Core Maintenance Fund. You can read more here.

Zefram started work on his maintenance grant!

Karl Williamson has published a basic implementation of script runs!

Karl had also requested (RFC: make utf16 to/from utf8 functions private to the core) to make the UTF 16 from/to UTF 8 functions in core be core-only.

Grant Reports

Issues

New Issues

Resolved Issues

Rejected Issues

Suggested Patches

Andrew Fresh provided a patch in Perl #132401 to support Time::HiRes in File::Copy.

John Lightsey provided a patch in Perl #132405 to fix a typo that prevents deparsing some transliterations.

A patch by Nicholas R. (Atoomic) in Perl #132418 to introduce macros to simply @INC setting

Tomasz Konojacki provided a patch in Perl #132421 to fix compilation errors under non-english Visual C++ 2015/2017.

Chase Whitener provided a patch in Perl #132422 to modernize IO::Socket Documentation.

David Cantrell provided a documentation patch for experimental::lexical_topic.

Todd Rinaldo provided a patch for Perl #132429 (B::Deparse generated code affected by use vars?)

Discussion

Nicholas R. provided a patch in Perl #132406: to raise discussion of not loading Config in Storable just for detecting FLOCK support.

Perl Foundation News: Maintaining Perl 5 (Tony Cook): October 2017 Report

This is a monthly report by Tony Cook on his grant under Perl 5 Core Maintenance Fund. We thank the TPF sponsors to make this grant possible.

Approximately 23 tickets were reviewed, and 7 patches were
applied

[Hours]         [Activity]
  0.33          #122807 review discussion
  0.45          #124349 review discussion and apply patch
  0.40          #125619 review discussion, research, briefly comment
  0.25          #125760 review discussion, add to 5.30 blockers for make
                them croak instead
  0.18          #126707 review discussion and code, comment
  0.17          #126849 check upstream report and close
  0.83          #127063 re-check patch, testing, apply to blead
 39.85          #127743 work on cherry-picking from cperl
                #127743 more cherry-picking
                #127743 more cherry-picking
                #127743 more cherry-picking
                #127743 more cherry-picking
                #127743 more cherry-picking
                #127743 more cherry-picking
                #127743 more cherry-picking
                #127743 work on cherry-picking from cperl
                #127743 work on cherry-picking from cperl
                #127743 code review
                #127743 code review
                #127743 more code review
                #127743 more code review, consider fixes
                #127743 status email
                #127743 email discussion
                #127743 work on fixes
                #127743 work on possible way to test large numbers of Svs
                #127743 manage to produce buggy behaviour, work on fix
                #127743 large object tag implementation, testing
                #127743 test 2G+ object tag handling, testing
                #127743 audit 2G+ tag handling for hooks, work on
                regression tests for 2G+ object tag handling
                #127743 more work on tests
  3.21          #128765 work on fix
                #128765 more work on fix
                #128765 more work on fix, fail to figure out efficient
                masking
  0.33          #130080 research, add to maint-votes
  0.92          #131065 (sec) comment
  0.92          #131878 (sec) work up a patch and comment with patch
  1.88          #131982 testing (including some strange results) minor
                portability change, apply to blead
  8.98          #132013 work on an implementation
                #132013 work on an implementation
                #132013 testing, debugging
                #132013 debugging, add groups, - prefix
                #132013 more tests, docs, polish, comment with patch
  0.25          #132159 testing, apply to blead
  0.40          #132160 review patch, testing, apply to blead
  0.73          #132171 review, testing, apply to blead
  0.42          #132234 try to reproduce, comment
  5.50          #132245 debugging, find a memory leak, work on a fix,
                testing
                #132245 re-work fix, testing, comment with patches
                #132245 restesting, apply to blead
  0.28          comment on Zefram’s character encoding comment
  0.52          default_inc_excludes_dot query
  0.28          fix io/tell.t
  0.52          script runs discussion: comment
======
 67.60 hours total

Perl Foundation News: Call For Proposals: November 2017 Round

The Grants Committee has expended its budget for the period ending with 2017.

In accordance with the TPF rules of operation (http://www.perlfoundation.org/rulesofoperation), grants evaluations are stalled until further notice. I'm expecting that we'll be able to re-open evaluations starting in the January 2018 period.

Thanks to all the TPF sponsors that make the grants process possible. Please consider becoming one and donating at http://donate.perlfoundation.org/

If you have further questions, please contact me at tpf-grants-secretary at perl-foundation.org.

NeilB: The Great London Perl Bake Off

You may not have noticed, but the London Perl Workshop is happening later this month (Saturday 25th November). It's a free-to-attend community event: organised by members of the community, for the community, and made possible by sponsorship from companies in our community.

Reinforcing the community theme, we're trying an experiment this year: crowd-sourcing bakes from attendees for one of the coffee breaks. If you're an experienced baker, an occasional dabbler (like myself), or even a complete neophyte looking for a reason to start, why not give it a go?

We've got 10 bakers, each of whom will bring some kind of bake. Still space for a few more, if you want to join us! Nut-free please.

You don't need to be an experienced baker. We can provide a recipe, though googling "foolproof [thing] recipe" will do the job. And you've got time to practice.

If you're happy to help out, just drop me a line please, so I can coordinate: neil at bowers dot com.

perlancar's blog: List of new CPAN distributions – Oct 2017

perlancar's blog
dist author version abstract
ALBD HENRYST 0.01 a perl implementation of Literature Based Discovery
Acme-ID-CompanyName PERLANCAR 0.001 Generate nice-sounding, generic Indonesian company names
Acme-Math-Josan MUTO 0.01 do 'josan'
Acme-Monme WHISKYSHU 0.01 The great new Acme::Monme!
Alien-Build-Plugin-Build-Premake5 JJATRIA 0.001 Premake5 build plugin for Alien::Build
Alien-Hush LETO 0.8888 Easy installation of the Hush cryptocoin full node daemon
Alien-LibreSSL PLICEASE 0.01 Alien wrapper for LibreSSL (alternative to OpenSSL)
Alien-XInputSimulator ATHREEF 0.001 Perl distribution for XInputSimulator
Alien-Zcash LETO 0.01 Easy installation of the Zcash cryptocoin full node daemon
Alien-premake5 JJATRIA 0.001 Build or find premake5
App-Anchr WANGQ 0.4.3 Assembler of N-free CHRomosomes
App-Brl2Brl LRS 0.01 Convert between braille character sets.
App-CGIThis SIMBABQUE 0.001 Export the current directory like a cgi-bin
App-Conf OKLAS 0.01 Configuration files management library and program
App-Elog JACOBG 0.01 An Apache error log viewer
App-HTTPSThis PERLANCAR 0.001 Export the current directory over HTTPS
App-Prove-Plugin-CumulativeTimer MASIUCHI 0.01 A prove plugin to display cumulative elapsed time of tests.
App-TEWK-tt TEWK 0.01 runs a CXXTest test
App-mysqlinfo PERLANCAR 0.001 Get/extract information from MySQL database
AppLib-CreateSelfSignedSSLCert PERLANCAR 0.150 Create self-signed SSL certificate
Bio-PhyloXS RVOSA v0.1.0 Core modules for Bio::Phylo, re-implemented using C
Business-BR-CNJ DLIMA 0.01 Harness brazilian CNJ (Conselho Nacional de Justiça) data and functions.
Business-BR-CNJ-NumberExtractor DLIMA 0.01 Extract brazilian CNJ numbers (Conselho Nacional de Justiça) from a text file or a web page.
Business-BR-CNJ-WebService DLIMA 0.01 Interacts with brazilian CNJ (Conselho Nacional de Justiça) SOAP WebService.
CBitcoin FAVIOFLAM 0.6 A wrapper for the Picocoin C Library
CXC-DS9 DJERIUS 0.01 Things of Utility with DS9
Catalyst-Plugin-DBIC-ConsoleQueryLog JJNAPIORK 0.001 A simple log to console for DBIC querylogs
Class-Accessor-PackedString-Set PERLANCAR 0.001 Like Class::Accessor::PackedString, but store attributes as they are set
Config-LNPath LNATION 0.01 Currently just a Simple YAML Config Reader.
Confluence-REST RLOVELAND 0.01 Thin wrapper around Confluence's REST API
Context-Singleton BARNEY 1.0.0 handles context specific singletons
DBIx-Class-HashAccessor GETTY 0.001 Helper functions to install accessors for serialized hash columns
Dancer2-Plugin-GraphQL ETJ 0.01 a plugin for adding GraphQL route handlers
Dancer2-Plugin-WebSocket YANICK 0.0.1 add a websocket interface to your Dancers app
Data-SeaBASS JLEFLER 0.172780 Object-oriented interface for reading/writing SeaBASS files
Data-ValidateInterdependent AMON 0.000001 safely validate interdependent parameters
DateTime-Duration-Lite PERLANCAR 0.001 Duration objects for date math (lite version)
DateTime-Tiny-Compact PERLANCAR 0.001 DateTime::Tiny but uses less space
DateTimeX-Duration-Lite PERLANCAR 0.002 Duration objects for date math (lite version)
DateTimeX-Tiny-Compact PERLANCAR 0.002 DateTime::Tiny but uses less space
Defined-KV ROBN 0.001 Create a KV pair, but only if the value is defined
Device-Network-ConfigParser PUGLET 0.001 Harness for parsing network device confiugrations
Directory-Scanner STEVAN 0.01 Streaming directory scanner
Dist-Zilla-Plugin-Git-FilePermissions SKIRMESS 0.001 fix the file permissions in your Git repository with Dist::Zilla
Dist-Zilla-Plugin-Git-RequireUnixEOL SKIRMESS 0.001 Enforce the correct line endings in your Git repository with Dist::Zilla
Dist-Zilla-PluginBundle-Author-AMON AMON 0.000001 dzil config choices by AMON
Ei NKUITSE 0.07 manage an inventory of stuff
File-Globstar GUIDO 0.1 Perl Globstar (double asterisk globbing) and utils
Flexconf OKLAS 0.01 Configuration files management library and program
Games-Sudoku-CLI SZABGAB 0.01 play Sudoku on the command line
Geo-Coder-Free NHORNE 0.01 Provides a geocoding functionality using free databases of towns
Geo-Coder-Postcodes NHORNE 0.01 Provides a geocoding functionality using https://postcodes.io.
Geo-Coder-US-Census NHORNE 0.01 Provides a geocoding functionality using http:://geocoding.geo.census.gov for the US.
Getopt-Long-Less-Dump PERLANCAR 0.001 Run a Getopt::Long::Less-based script but only to dump the spec
HTML-Untidy JEFFOBER 0.01 yet another way to write HTML quickly and programmatically
HTTP-Tiny-FileProtocol RENEEB 0.01 Add support for file:// protocol to HTTP::Tiny
Hash-Iterator MIRKOS 0.001 Perl extension for blah blah blah
Java-Doc PRBRENAN 20171006 Extract documentation from Java source code.
Lingua-FuzzyTrans-PT2GL AMBS 0.001 Translates Portuguese words to Galician using fuzzy replacements
Lingua-Stem-Uk RRVCKU 0.01 Porter's stemming algorithm for Ukrainian
List-Breakdown TEJR 0.13 Build list sublists matching conditions
Mail-Milter-Authentication-Handler-ARC MBRADSHAW 1.001003 ARC Module
Mail-Run-Crypt TEJR 0.01 Encrypt and mail output from command runs
Marky RUBYKAT 0.033 web application for bookmark databases
Math-Model MORITZ 0.1
Math-Vectors2 PRBRENAN 20171007 Vectors in two dimensions.
Mojo-Bass FERREIRA 0.1.0 Mojo::Base + lexical "has"
Mojolicious-Plugin-ClientIP-Pluggable BINARY 0.01 Client IP header handling for Mojolicious requests
Mojolicious-Plugin-DBIxCustom WFSO v0.1.0 链接DBIx::Custom到Mojoliciousçš„æ’件
Mojolicious-Plugin-GraphQL ETJ 0.01 a plugin for adding GraphQL route handlers
Mojolicious-ServiceManage WFSO 0.01 Service management for Mojolicious Framework
Mojolicious-Services WFSO v1.0.0 Mojolicious::Services 是为Mojolicious框架æ供的Service管ç†æ’件。
Muster RUBYKAT 0.61 web application for content management
Net-AMQP-RabbitMQ-Batch WHISK 0.2301 simple batch processing of messages for RabbitMQ.
Net-Frame-Layer-ICMPv6-MLD VINSWORLD 1.00 Multicast Listener Discovery layer object
Net-Host64 EHERMAN 0.001 Interface to libehnet64 "Easy Host-Network 64" library
OTRS-OPM-Installer RENEEB 0.01 Install OTRS add ons
PGPLOT-Device DJERIUS 0.09 autogenerate PGPLOT device names
Pcore-Proxy ZDM v0.1.1
Plack-App-URLMux BURNES 0.02 Map multiple applications in defferent url path.
Pootle-Client KIVILAHTI 0.01 Pootle API Client library
RT-Extension-GroupSummary GIBUS 0.01 RT-Extension-GroupSummary Extension
RT-Extension-Memo GIBUS 0.01 RT-Extension-Memo Extension
RT-Extension-ModifyUsersPrefs GIBUS 0.01 Allow to modify other users' preferences
SQL-Translator-Producer-GraphQL ETJ 0.01 GraphQL schema producer for SQL::Translator
String-Tagged-Terminal PEVANS 0.01 format terminal output using String::Tagged
Task-Devel-Essentials MHASCH 0.004 Bundle of modules useful for developers
Term-ANSIColor-Conditional PERLANCAR 0.001 Colorize text only if color is enabled
Test-Applify KIWIROY 0.02 Testing Applify scripts
Text-More-Perl6 TBROWDER v0.1.8
Type-TinyX-Facets DJERIUS 0.01 Easily create a facet parameterized Type::Tiny type
Types-PDL DJERIUS 0.01 PDL types using Type::Tiny
Vlc-Engine BRNFLK 0.001
WWW-API-Bitfinex HDELGADO 0.01 API Btifinex
WWW-Oxontime MGV 0.001 live Oxford bus departures from Oxontime
WebService-BitbucketServer CCM 0.600 Bindings for Bitbucket Server REST APIs
WebService-OverheidIO WATERKIP 1.0 A (semi) abstract class that implements logic to talk to Overheid.IO
Win32-AutoItX MTELNOV 1.00 AutoItX3 perl interface
Win32-Net-Info VINSWORLD 1.00 Win32 Network Adapter Interface
Wx-Perl-IconDepot HANJE 0.01 Use icon libraries quick & easy
Xcode-Project JOHNTSAI 0.001001
YAML-SyckWrapper VSESPB 0.001 Loads YAML files in old and new fashion encoding ways.
Yandex-Disk VRAG 0.01 a simple API for Yandex Disk
ZMQ-Raw JACQUESG 0.01 Perl bindings to the ZeroMQ library
Zonemaster-Engine ZNMSTR 2.000000 A tool to check the quality of a DNS zone
Zonemaster-LDNS ZNMSTR 1.0.0 Perl wrapper for the ldns DNS library.
perl-term-colormap XXFELIXXX 0.11 Colormaps for ANSI 256 Color Terminals!
perl_create_fileV MHCRNL 03
roles STEVAN 0.01 A simple pragma for composing roles.
slots STEVAN 0.01 A simple pragma for managing class slots.

Dave's Free Press: Journal: Module pre-requisites analyser

Dave's Free Press: Journal: CPANdeps

Dave's Free Press: Journal: Perl isn't dieing

Dave's Free Press: Journal: YAPC::Europe 2007 report: day 3

Dave's Free Press: Journal: Devel::CheckLib can now check libraries' contents

Ocean of Awareness: Top-down parsing is guessing

Top-down parsing is guessing. Literally. Bottom-up parsing is looking.

The way you'll often hear that phrased is that top-down parsing is looking, starting at the top, and bottom-up parsing is looking, starting at the bottom. But that is misleading, because the input is at the bottom -- at the top there is nothing to look at. A usable top-down parser must have a bottom-up component, even if that component is just lookahead.

A more generous, but still accurate, way to describe the top-down component of parsers is "prediction". And prediction is, indeed, a very useful component of a parser, when used in combination with other techniques.

Of course, if a parser does nothing but predict, it can predict only one input. Top-down parsing must always be combined with a bottom-up component. This bottom-up component may be as modest as lookahead, but it must be there or else top-down parsing is really not parsing at all.

So why is top-down parsing used so much?

Top-down parsing may be unusable in its pure form, but from one point of view that is irrelevant. Top-down parsing's biggest advantage is that it is highly flexible -- there's no reason to stick to its "pure" form.

A top-down parser can be written as a series of subroutine calls -- a technique called recursive descent. Recursive descent allows you to hook in custom-written bottom-up logic at every top-down choice point, and it is a technique which is completely understandable to programmers with little or no training in parsing theory. When dealing with recursive descent parsers, it is more useful to be a seasoned, far-thinking programmer than it is to be a mathematician. This makes recursive descent very appealing to seasoned, far-thinking programmers, and they are the audience that counts.

Switching techniques

You can even use the flexibility of top-down to switch away from top-down parsing. For example, you could claim that a top-down parser could do anything my own parser (Marpa) could do, because a recursive descent parser can call a Marpa parser.

A less dramatic switchoff, and one that still leaves the parser with a good claim to be basically top-down, is very common. Arithmetic expressions are essential for a computer language. But they are also among the many things top-down parsing cannot handle, even with ordinary lookahead. Even so, most computer languages these days are parsed top-down -- by recursive descent. These recursive descent parsers deal with expressions by temporarily handing control over to an bottom-up operator precedence parser. Neither of these parsers is extremely smart about the hand-over and hand-back -- it is up to the programmer to make sure the two play together nicely. But used with caution, this approach works.

Top-down parsing and language-oriented programming

But what about taking top-down methods into the future of language-oriented programming, extensible languages, and grammars which write grammars? Here we are forced to confront the reality -- that the effectiveness of top-down parsing comes entirely from the foreign elements that are added to it. Starting from a basis of top-down parsing is literally starting with nothing. As I have shown in more detail elsewhere, top-down techniques simply do not have enough horsepower to deal with grammar-driven programming.

Perl 6 grammars are top-down -- PEG with lots of extensions. These extensions include backtracking, backtracking control, a new style of tie-breaking and lots of opportunity for the programmer to intervene and customize everything. But behind it all is a top-down parse engine.

One aspect of Perl 6 grammars might be seen as breaking out of the top-down trap. That trick of switching over to a bottom-up operator precedence parser for expressions, which I mentioned above, is built into Perl 6 and semi-automated. (I say semi-automated because making sure the two parsers "play nice" with each other is not automated -- that's still up to the programmer.)

As far as I know, this semi-automation of expression handling is new with Perl 6 grammars, and it may prove handy for duplicating what is done in recursive descent parsers. But it adds no new technique to those already in use. And features like

  • mulitple types of expression, which can be told apart based on their context,
  • n-ary expressions for arbitrary n, and
  • the autogeneration of multiple rules, each allowing a different precedence scheme, for expressions of arbitrary arity and associativity,

all of which are available and in current use in Marpa, are impossible for the technology behind Perl 6 grammars.

I am a fan of the Perl 6 effort. Obviously, I have doubts about one specific set of hopes for Perl 6 grammars. But these hopes have not been central to the Perl 6 effort, and I will be an eager student of the Perl 6 team's work over the coming months.

Comments

To learn more about Marpa, there's the official web site maintained by Ron Savage. I also have a Marpa web site. Comments on this post can be made in Marpa's Google group, or on our IRC channel: #marpa at freenode.net.

Dave's Free Press: Journal: I Love Github

Dave's Free Press: Journal: Palm Treo call db module

Dave's Free Press: Journal: Graphing tool

Dave's Free Press: Journal: Travelling in time: the CP2000AN

Dave's Free Press: Journal: XML::Tiny released

Dave's Free Press: Journal: YAPC::Europe 2007 report: day 1

Ocean of Awareness: Parsing: an expanded timeline

The fourth century BCE: In India, Pannini creates a sophisticated description of the Sanskrit language, exact and complete, and including pronunciation. Sanskrit could be recreated using nothing but Pannini's grammar. Pannini's grammar is probably the first formal system of any kind, predating Euclid. Even today, nothing like it exists for any other natural language of comparable size or corpus. Pannini is the object of serious study today. But in the 1940's and 1950's Pannini is almost unknown in the West. His work has no direct effect on the other events in this timeline.

1943: Emil Post defines and studies a formal rewriting system using productions. With this, the process of reinventing Pannini in the West begins.

1948: Claude Shannon publishes the foundation paper of information theory. Andrey Markov's finite state processes are used heavily.

1952: Grace Hopper writes a linker-loader and describes it as a "compiler". She seems to be the first person to use this term for a computer program. Hopper uses the term "compiler" in its original sense: "something or someone that brings other things together".

1954: At IBM, a team under John Backus begins working on the language which will be called FORTRAN. The term "compiler" is still being used in Hopper's looser sense, instead of its modern one. In particular, there is no implication that the output of a "compiler" is ready for execution by a computer. The output of one 1954 "compiler", for example, produces relative addresses, which need to be translated by hand before a machine can execute them.

1955: Noam Chomsky is awarded a Ph.D. in linguistics and accepts a teaching post at MIT. MIT does not have a linguistics department and Chomsky, in his linguistics course, is free to teach his own approach, highly original and very mathematical.

1956: Chomsky publishes the paper which is usually considered the foundation of Western formal language theory. The paper advocates a natural language approach that involves

  • a bottom layer, using Markov's finite state processes;
  • a middle, syntactic layer, using context-free grammars and context-sensitive grammars; and
  • a top layer, which involves mappings or "transformations" of the output of the syntactic layer.

These layers resemble, and will inspire, the lexical, syntactic and AST transformation phases of modern parsers. For finite state processes, Chomsky acknowledges Markov. The other layers seem to be Chomsky's own formulations -- Chomsky does not cite Post's work.

1957: Steven Kleene discovers regular expressions, a very handy notation for Markov's processes. Regular expressions turn out to describe exactly the mathematical objects being studied as finite state automata, as well as some of the objects being studied as neural nets.

1957: Noam Chomsky publishes Syntactic Structures, one of the most influential books of all time. The orthodoxy in 1957 is structural linguistics which argues, with Sherlock Holmes, that "it is a capital mistake to theorize in advance of the facts". Structuralists start with the utterances in a language, and build upward.

But Chomsky claims that without a theory there are no facts: there is only noise. The Chomskyan approach is to start with a grammar, and use the corpus of the language to check its accuracy. Chomsky's approach will soon come to dominate linguistics.

1957: Backus's team makes the first FORTRAN compiler available to IBM customers. FORTRAN is the first high-level language that will find widespread implementation. As of this writing, it is the oldest language that survives in practical use. FORTRAN is a line-by-line language and its parsing is primitive.

1958: John McCarthy's LISP appears. LISP goes beyond the line-by-line syntax -- it is recursively structured. But the LISP interpreter does not find the recursive structure: the programmer must explicitly indicate the structure herself, using parentheses.

1959: Backus invents a new notation to describe the IAL language (aka ALGOL). Backus's notation is influenced by his study of Post -- he seems not to have read Chomsky until later.

1960: Peter Naur improves the Backus notation and uses it to describe ALGOL 60. The improved notation will become known as Backus-Naur Form (BNF).

1960: The ALGOL 60 report specifies, for the first time, a block structured language. ALGOL 60 is recursively structured but the structure is implicit -- newlines are not semantically significant, and parentheses indicate syntax only in a few specific cases. The ALGOL compiler will have to find the structure. It is a case of 1960's optimism at its best. As the ALGOL committee is well aware, a parsing algorithm capable of handling ALGOL 60 does not yet exist. But the risk they are taking will soon pay off.

1960: A.E. Gleenie publishes his description of a compiler-compiler. Glennie's "universal compiler" is more of a methodology than an implementation -- the compilers must be written by hand. Glennie credits both Chomsky and Backus, and observes that the two notations are "related". He also mentions Post's productions. Glennie may have been the first to use BNF as a description of a procedure instead of as the description of a Chomsky grammar. Glennie points out that the distinction is "important".

Chomskyan BNF and procedural BNF: BNF, when used as a Chomsky grammar, describes a set of strings, and does not describe how to parse strings according to the grammar. BNF notation, if used to describe a procedure, is a set of instructions, to be tried in some order, and used to process a string. Procedural BNF describes a procedure first, and a language only indirectly.

Both procedural and Chomskyan BNF describe languages, but usually not the same language. That is,

  • Suppose D is some BNF description.
  • Let P(D) be D interpreted as a procedure,
  • Let L(P(D)) be the language which the procedure P(D) parses.
  • Let G(D) be D interpreted as a Chomsky grammar.
  • Let L(G(D)) be the language which the grammar G(D) describes.
  • Then, usually, L(P(D)) != L(G(D)).

The pre-Chomskyan approach, using procedural BNF, is far more natural to someone trained as a computer programmer. The parsing problem appears to the programmer in the form of strings to be parsed, exactly the starting point of procedural BNF and pre-Chomsky parsing.

Even when the Chomskyan approach is pointed out, it does not at first seem very attractive. With the pre-Chomskyan approach, the examples of the language more or less naturally lead to a parser. In the Chomskyan approach the programmer has to search for an algorithm to parse strings according to his grammar -- and the search for good algorithms to parse Chomskyan grammars has proved surprisingly long and difficult. Handling semantics is more natural with a Chomksyan approach. But, using captures, semantics can be added to a pre-Chomskyan parser and, with practice, this seems natural enough.

Despite the naturalness of the pre-Chomskyan approach to parsing, we will find that the first fully-described automated parsers are Chomskyan. This is a testimony to Chomsky's influence at the time. We will also see that Chomskyan parsers have been dominant ever since.

1961: In January, Ned Irons publishes a paper describing his ALGOL 60 parser. It is the first paper to fully describe any parser. The Irons algorithm is Chomskyan and top-down with a "left corner" element. The Irons algorithm is general, meaning that it can parse anything written in BNF. It is syntax-driven (aka declarative), meaning that the parser is actually created from the BNF -- the parser does not need to be hand-written.

1961: Peter Lucas publishes the first description of a purely top-down parser. This can be considered to be recursive descent, though in Lucas's paper the algorithm has a syntax-driven implementation, useable only for a restricted class of grammars. Today we think of recursive descent as a methodology for writing parsers by hand. Hand-coded approaches became more popular in the 1960's due to three factors:

  • Memory and CPU were both extremely limited. Hand-coding paid off, even when the gains were small.
  • Non-hand coded top-down parsing, of the kind Lucas's syntax-driven approach allowed, is a very weak parsing technique. It was (and still is) often necessary to go beyond its limits.
  • Top-down parsing is intuitive -- it essentially means calling subroutines. It therefore requires little or no knowledge of parsing theory. This makes it a good fit for hand-coding.

1963: L. Schmidt, Howard Metcalf, and Val Schorre present papers on syntax-directed compilers at a Denver conference.

1964: Schorre publishes a paper on the Meta II "compiler writing language", summarizing the papers of the 1963 conference. Schorre cites both Backus and Chomsky as sources for Meta II's notation. Schorre notes that his parser is "entirely different" from that of Irons 1961 -- in fact it is pre-Chomskyan. Meta II is a template, rather than something that readers can use, but in principle it can be turned into a fully automated compiler-compiler.

1965: Don Knuth invents LR parsing. The LR algorithm is deterministic, Chomskyan and bottom-up, but it is not thought to be practical. Knuth is primarily interested in the mathematics.

1968: Jay Earley invents the algorithm named after him. Like the Irons algorithm, Earley's algorithm is Chomskyan, syntax-driven and fully general. Unlike the Irons algorithm, it does not backtrack. Earley's algorithm is both top-down and bottom-up at once -- it uses dynamic programming and keeps track of the parse in tables. Earley's approach makes a lot of sense and looks very promising indeed, but there are three serious issues:

  • First, there is a bug in the handling of zero-length rules.
  • Second, it is quadratic for right recursions.
  • Third, the bookkeeping required to set up the tables is, by the standards of 1968 hardware, daunting.

1969: Frank DeRemer describes a new variant of Knuth's LR parsing. DeRemer's LALR algorithm requires only a stack and a state table of quite manageable size. LALR looks practical.

1969: Ken Thompson writes the "ed" editor as one of the first components of UNIX. At this point, regular expressions are an esoteric mathematical formalism. Through the "ed" editor and its descendants, regular expressions will become an everyday part of the working programmer's toolkit.

Recognizers: In comparing algorithms, it can be important to keep in mind whether they are recognizers or parsers. A recognizer is a program which takes a string and produces a "yes" or "no" according to whether a string is in part of a language. Regular expressions are typically used as recognizers. A parser is a program which takes a string and produces a tree reflecting its structure according to a grammar. The algorithm for a compiler clearly must be a parser, not a recognizer. Recognizers can be, to some extent, used as parsers by introducing captures.

1972: Alfred Aho and Jeffrey Ullman publish a two volume textbook summarizing the theory of parsing. This book is still important. It is also distressingly up-to-date -- progress in parsing theory slowed dramatically after 1972. Aho and Ullman describe a straightforward fix to the zero-length rule bug in Earley's original algorithm. Unfortunately, this fix involves adding even more bookkeeping to Earley's.

1972: Under the names TDPL and GTDPL, Aho and Ullman investigate the non-Chomksyan parsers in the Schorre lineage. They note that "it can be quite difficult to determine what language is defined by a TDPL parser". That is, GTDPL parsers do whatever they do, and that whatever is something the programmer in general will not be able to describe. The best a programmer can usually do is to create a test suite and fiddle with the GTDPL description until it passes. Correctness cannot be established in any stronger sense. GTDPL is an extreme form of the old joke that "the code is the documentation" -- with GTDPL nothing documents the language of the parser, not even the code.

GTDPL's obscurity buys nothing in the way of additional parsing power. Like all non-Chomskyan parsers, GTDPL is basically a extremely powerful recognizer. Pressed into service as a parser, it is comparatively weak. As a parser, GTDPL is essentially equivalent to Lucas's 1961 syntax-driven algorithm, which was in turn a restricted form of recursive descent.

At or around this time, rumor has it that the main line of development for GTDPL parsers is classified secret by the US government. GTDPL parsers have the property that even small changes in GTDPL parsers can be very labor-intensive. For some government contractors, GTDPL parsing provides steady work for years to come. Public interest in GTDPL fades.

1975: Bell Labs converts its C compiler from hand-written recursive descent to DeRemer's LALR algorithm.

1977: The first "Dragon book" comes out. This soon-to-be classic textbook is nicknamed after the drawing on the front cover, in which a knight takes on a dragon. Emblazoned on the knight's lance are the letters "LALR". From here on out, to speak lightly of LALR will be to besmirch the escutcheon of parsing theory.

1979: Bell Laboratories releases Version 7 UNIX. V7 includes what is, by far, the most comprehensive, useable and easily available compiler writing toolkit yet developed.

1979: Part of the V7 toolkit is Yet Another Compiler Compiler (YACC). YACC is LALR-powered. Despite its name, YACC is the first compiler-compiler in the modern sense. For some useful languages, the process of going from Chomskyan specification to executable is fully automated. Most practical languages, including the C language and YACC's own input language, still require manual hackery. Nonetheless, after two decades of research, it seems that the parsing problem is solved.

1987: Larry Wall introduces Perl 1. Perl embraces complexity like no previous language. Larry uses YACC and LALR very aggressively -- to my knowledge more aggressively than anyone before or since.

1991: Joop Leo discovers a way of speeding up right recursions in Earley's algorithm. Leo's algorithm is linear for just about every unambiguous grammar of practical interest, and many ambiguous ones as well. In 1991 hardware is six orders of magnitude faster than 1968 hardware, so that the issue of bookkeeping overhead had receded in importance. This is a major discovery. When it comes to speed, the game has changed in favor of the Earley algorithm.

But Earley parsing is almost forgotten. Twenty years will pass before anyone writes a practical implementation of Leo's algorithm.

1990's: Earley's is forgotten. So everyone in LALR-land is content, right? Wrong. Far from it, in fact. Users of LALR are making unpleasant discoveries. While LALR automatically generates their parsers, debugging them is so hard they could just as easily write the parser by hand. Once debugged, their LALR parsers are fast for correct inputs. But almost all they tell the users about incorrect inputs is that they are incorrect. In Larry's words, LALR is "fast but stupid".

2000: Larry Wall decides on a radical reimplementation of Perl -- Perl 6. Larry does not even consider using LALR again.

2002: John Aycock and R. Nigel Horspool publish their attempt at a fast, practical Earley's parser. Missing from it is Joop Leo's improvement -- they seem not to be aware of it. Their own speedup is limited in what it achieves and the complications it introduces can be counter-productive at evaluation time. But buried in their paper is a solution to the zero-length rule bug. And this time the solution requires no additional bookkeeping.

2004: Bryan Ford publishes his paper on PEG. Implementers by now are avoiding YACC, and it seems as if there might soon be no syntax-driven algorithms in practical use. Ford fills this gap by repackaging the nearly-forgotten GTDPL. Ford adds packratting, so that PEG is always linear, and provides PEG with an attractive new syntax. But nothing has been done to change the problematic behaviors of GTDPL.

2006: GNU announces that the GCC compiler's parser has been rewritten. For three decades, the industry's flagship C compilers have used LALR as their parser -- proof of the claim that LALR and serious parsing are equivalent. Now, GNU replaces LALR with the technology that it replaced a quarter century earlier: recursive descent.

Today: After five decades of parsing theory, the state of the art seems to be back where it started. We can imagine someone taking Ned Iron's original 1961 algorithm from the first paper ever published describing a parser, and republishing it today. True, he would have to translate its code from the mix of assembler and ALGOL into something more fashionable, say Haskell. But with that change, it might look like a breath of fresh air.

Marpa: an afterword

The recollections of my teachers cover most of this timeline. My own begin around 1970. Very early on, as a graduate student, I became unhappy with the way the field was developing. Earley's algorithm looked interesting, and it was something I returned to on and off.

The original vision of the 1960's was a parser that was

  • efficient,
  • practical,
  • general, and
  • syntax-driven.

By 2010 this vision seemed to have gone the same way as many other 1960's dreams. The rhetoric stayed upbeat, but parsing practice had become a series of increasingly desperate compromises.

But, while nobody was looking for them, the solutions to the problems encountered in the 1960's had appeared in the literature. Aycock and Horspool had solved the zero-length rule bug. Joop Leo had found the speedup for right recursion. And the issue of bookkeeping overhead had pretty much evaporated on its own. Machine operations are now a billion times faster than in 1968, and are probably no longer relevant in any case -- cache misses are now the bottleneck.

The programmers of the 1960's would have been prepared to trust a fully declarative Chomskyan parser. With the experience with LALR in their collective consciousness, modern programmers might be more guarded. As Lincoln said, "Once a cat's been burned, he won't even sit on a cold stove." But I found it straightforward to rearrange the Earley parse engine to allow efficient event-driven handovers between procedural and syntax-driven logic. And Earley tables provide the procedural logic with full knowledge of the state of the parse so far, so that Earley's algorithm is a better platform for hand-written procedural logic than recursive descent.

References, comments, etc.

My implementation of Earley's algorithm is called Marpa. For more about Marpa, there is the semi-official web site, maintained by Ron Savage. The official, but more limited, Marpa website is my personal one. Comments on this post can be made in Marpa's Google group, or on our IRC channel: #marpa at freenode.net.

Dave's Free Press: Journal: Thanks, Yahoo!

Dave's Free Press: Journal: YAPC::Europe 2007 report: day 2

Ocean of Awareness: What are the reasonable computer languages?

"You see things; and you say 'Why?' But I dream things that never were; and I say 'Why not?'" -- George Bernard Shaw

In the 1960's and 1970's computer languages were evolving rapidly. It was not clear which way they were headed. Would most programming be done with general-purpose languages? Or would programmers create a language for every task domain? Or even for every project? And, if lots of languages were going to be created, what kinds of languages would be needed?

It was in that context that Čulik and Cohen, in a 1973 paper, outlined what they thought programmers would want and should have. In keeping with the spirit of the time, it was quite a lot:

  • Programmers would want to extend their grammars with new syntax, including new kinds of expressions.
  • Programmers would also want to use tools that automatically generated new syntax.
  • Programmers would not want to, and especially in the case of auto-generated syntax would usually not be able to, massage the syntax into very restricted forms. Instead, programmers would create grammars and languages which required unlimited lookahead to disambiguate, and they would require parsers which could handle these grammars.
  • Finally, programmers would need to be able to rely on all of this parsing being done in linear time.

Today, we think we know that Čulik and Cohen's vision was naive, because we think we know that parsing technology cannot support it. We think we know that parsing is much harder than they thought.

The eyeball grammars

As a thought problem, consider the "eyeball" class of grammars. The "eyeball" class of grammars contains all the grammars that a human can parse at a glance. If a grammar is in the eyeball class, but a computer cannot parse it, it presents an interesting choice. Either,

  • your computer is not using the strongest practical algorithm; or
  • your mind is using some power which cannot be reduced to a machine computation.

There are some people out there (I am one of them) who don't believe that everything the mind can do reduces to a machine computation. But even those people will tend to go for the choice in this case: There must be some practical computer parsing algorithm which can do at least as well at parsing as a human can do by "eyeball". In other words, the class of "reasonable grammars" should contain the eyeball class.

Čulik and Cohen's candidate for the class of "reasonable grammars" were the grammars that a deterministic parse engine could parse if it had a lookahead that was infinite, but restricted to distinguishing between regular expressions. They called these the LR-regular, or LRR, grammars. And the LRR grammars do in fact seem to be a good first approximation to the eyeball class. They do not allow lookahead that contains things that you have to count, like palindromes. And, while I'd be hard put to eyeball every possible string for every possible regular expression, intuitively the concept of scanning for a regular expression does seem close to capturing the idea of glancing through a text looking for a telltale pattern.

So what happened?

Alas, the algorithm in the Čulik and Cohen paper turned out to be impractical. But in 1991, Joop Leo discovered a way to adopt Earley's algorithm to parse the LRR grammars in linear time, without doing the lookahead. And Leo's algorithm does have a practical implementation: Marpa.

References, comments, etc.

To learn more about Marpa, there's the official web site maintained by Ron Savage. I also have a Marpa web site. Comments on this post can be made in Marpa's Google group, or on our IRC channel: #marpa at freenode.net.

Dave's Free Press: Journal: YAPC::Europe 2007 travel plans

Dave's Free Press: Journal: Wikipedia handheld proxy

Dave's Free Press: Journal: Bryar security hole

Dave's Free Press: Journal: POD includes

Dave's Free Press: Journal: cgit syntax highlighting

Dave's Free Press: Journal: CPAN Testers' CPAN author FAQ

Ocean of Awareness: What parser do birds use?

"Here we provide, to our knowledge, the first unambiguous experimental evidence for compositional syntax in a non-human vocal system." -- "Experimental evidence for compositional syntax in bird calls", Toshitaka N. Suzuki, David Wheatcroft & Michael Griesser Nature Communications 7, Article number: 10986

In this post I look at a subset of the language of the Japanese great tit, also known as Parus major. The above cited article presents evidence that bird brains can parse this language. What about standard modern computer parsing methods? Here is the subset -- probably a tiny one -- of the language actually used by Parus major.

      S ::= ABC
      S ::= D
      S ::= ABC D
      S ::= D ABC
    

Classifying the Parus major grammar

Grammophone is a very handy new tool for classifying grammars. Its own parser is somewhat limited, so that it requires a period to mark the end of a rule. The above grammar is in Marpa's SLIF format, which is smart enough to use the "::=" operator to spot the beginning and end of rules, just as the human eye does. Here's the same grammar converted into a form acceptable to Grammophone:

      S -> ABC .
      S -> D .
      S -> ABC D .
      S -> D ABC .
    

Grammophone tells us that the Parus major grammar is not LL(1), but that it is LALR(1).

What does this mean?

LL(1) is the class of grammar parseable by top-down methods: it's the best class for characterizing most parsers in current use, including recursive descent, PEG, and Perl 6 grammars. All of these parsers fall short of dealing with the Parus major language.

LALR(1) is probably most well-known from its implementations in bison and yacc. While able to handle this subset of Parus's language, LALR(1) has its own, very strict, limits. Whether LALR(1) could handle the full complexity of Parus language is a serious question. But it's a question that in practice would probably not arise. LALR(1) has horrible error handling properties.

When the input is correct and within its limits, an LALR-driven parser is fast and works well. But if the input is not perfectly correct, LALR parsers produce no useful analysis of what went wrong. If Parus hears "d abc d", a parser like Marpa, on the other hand, can produce something like this:

# * String before error: abc d\s
# * The error was at line 1, column 7, and at character 0x0064 'd', ...
# * here: d
    

Parus uses its language in predatory contexts, and one can assume that a Parus with a preference for parsers whose error handling is on an LALR(1) level will not be keeping its alleles in the gene pool for very long.

References, comments, etc.

Those readers content with sub-Parus parsing methods may stop reading here. Those with greater parsing ambitions, however, may wish to learn more about Marpa. A Marpa test script for parsing the Parus subset is in a Github gist. Marpa has a semi-official web site, maintained by Ron Savage. The official, but more limited, Marpa website is my personal one. Comments on this post can be made in Marpa's Google group, or on our IRC channel: #marpa at freenode.net.

Dave's Free Press: Journal: Thankyou, Anonymous Benefactor!

Dave's Free Press: Journal: Number::Phone release

Dave's Free Press: Journal: Ill

Dave's Free Press: Journal: CPANdeps upgrade

Dave's Free Press: Journal: YAPC::Europe 2006 report: day 3

Ocean of Awareness: Introduction to Marpa Book in progress

What follows is a summary of the features of the Marpa algorithm, followed by a discussion of potential applications. It refers to itself as a "monograph", because it is a draft of part of the introduction to a technical monograph on the Marpa algorithm. I hope the entire monograph will appear in a few weeks.

The Marpa project

The Marpa project was intended to create a practical and highly available tool to generate and use general context-free parsers. Tools of this kind had long existed for LALR and regular expressions. But, despite an encouraging academic literature, no such tool had existed for context-free parsing. The first stable version of Marpa was uploaded to a public archive on Solstice Day 2011. This monograph describes the algorithm used in the most recent version of Marpa, Marpa::R2. It is a simplification of the algorithm presented in my earlier paper.

A proven algorithm

While the presentation in this monograph is theoretical, the approach is practical. The Marpa::R2 implementation has been widely available for some time, and has seen considerable use, including in production environments. Many of the ideas in the parsing literature satisfy theoretical criteria, but in practice turn out to face significant obstacles. An algorithm may be as fast as reported, but may turn out not to allow adequate error reporting. Or a modification may speed up the recognizer, but require additional processing at evaluation time, leaving no advantage to compensate for the additional complexity.

In this monograph, I describe the Marpa algorithm as it was implemented for Marpa::R2. In many cases, I believe there are better approaches than those I have described. But I treat these techniques, however solid their theory, as conjectures. Whenever I mention a technique that was not actually implemented in Marpa::R2, I will always explicitly state that that technique is not in Marpa as implemented.

Features

General context-free parsing

As implemented, Marpa parses all "proper" context-free grammars. The proper context-free grammars are those which are free of cycles, unproductive symbols, and inaccessible symbols. Worst case time bounds are never worse than those of Earley's algorithm, and therefore never worse than O(n**3).

Linear time for practical grammars

Currently, the grammars suitable for practical use are thought to be a subset of the deterministic context-free grammars. Using a technique discovered by Joop Leo, Marpa parses all of these in linear time. Leo's modification of Earley's algorithm is O(n) for LR-regular grammars. Leo's modification also parses many ambiguous grammars in linear time.

Left-eidetic

The original Earley algorithm kept full information about the parse --- including partial and fully recognized rule instances --- in its tables. At every parse location, before any symbols are scanned, Marpa's parse engine makes available its information about the state of the parse so far. This information is in useful form, and can be accessed efficiently.

Recoverable from read errors

When Marpa reads a token which it cannot accept, the error is fully recoverable. An application can try to read another token. The application can do this repeatedly as long as none of the tokens are accepted. Once the application provides a token that is accepted by the parser, parsing will continue as if the unsuccessful read attempts had never been made.

Ambiguous tokens

Marpa allows ambiguous tokens. These are often useful in natural language processing where, for example, the same word might be a verb or a noun. Use of ambiguous tokens can be combined with recovery from rejected tokens so that, for example, an application could react to the rejection of a token by reading two others.

Using the features

Error reporting

An obvious application of left-eideticism is error reporting. Marpa's abilities in this respect are ground-breaking. For example, users typically regard an ambiguity as an error in the grammar. Marpa, as currently implemented, can detect an ambiguity and report specifically where it occurred and what the alternatives were.

Event driven parsing

As implemented, Marpa::R2 allows the user to define "events". Events can be defined that trigger when a specified rule is complete, when a specified rule is predicted, when a specified symbol is nulled, when a user-specified lexeme has been scanned, or when a user-specified lexeme is about to be scanned. A mid-rule event can be defined by adding a nulling symbol at the desired point in the rule, and defining an event which triggers when the symbol is nulled.

Ruby slippers parsing

Left-eideticism, efficient error recovery, and the event mechanism can be combined to allow the application to change the input in response to feedback from the parser. In traditional parser practice, error detection is an act of desperation. In contrast, Marpa's error detection is so painless that it can be used as the foundation of new parsing techniques.

For example, if a token is rejected, the lexer is free to create a new token in the light of the parser's expectations. This approach can be seen as making the parser's "wishes" come true, and I have called it "Ruby Slippers Parsing".

One use of the Ruby Slippers technique is to parse with a clean but oversimplified grammar, programming the lexical analyzer to make up for the grammar's short-comings on the fly. As part of Marpa::R2, the author has implemented an HTML parser, based on a grammar that assumes that all start and end tags are present. Such an HTML grammar is too simple even to describe perfectly standard-conformant HTML, but the lexical analyzer is programmed to supply start and end tags as requested by the parser. The result is a simple and cleanly designed parser that parses very liberal HTML and accepts all input files, in the worst case treating them as highly defective HTML.

Ambiguity as a language design technique

In current practice, ambiguity is avoided in language design. This is very different from the practice in the languages humans choose when communicating with each other. Human languages exploit ambiguity in order to design highly flexible, powerfully expressive languages. For example, the language of this monograph, English, is notoriously ambiguous.

Ambiguity of course can present a problem. A sentence in an ambiguous language may have undesired meanings. But note that this is not a reason to ban potential ambiguity --- it is only a problem with actual ambiguity.

Syntax errors, for example, are undesired, but nobody tries to design languages to make syntax errors impossible. A language in which every input was well-formed and meaningful would be cumbersome and even dangerous: all typos in such a language would be meaningful, and parser would never warn the user about errors, because there would be no such thing.

With Marpa, ambiguity can be dealt with in the same way that syntax errors are dealt with in current practice. The language can be designed to be ambiguous, but any actual ambiguity can be detected and reported at parse time. This exploits Marpa's ability to report exactly where and what the ambiguity is. Marpa::R2's own parser description language, the SLIF, uses ambiguity in this way.

Auto-generated languages

In 1973, Čulik and Cohen pointed out that the ability to efficiently parse LR-regular languages opens the way to auto-generated languages. In particular, Čulik and Cohen note that a parser which can parse any LR-regular language will be able to parse a language generated using syntax macros.

Second order languages

In the literature, the term "second order language" is usually used to describe languages with features which are useful for second-order programming. True second-order languages --- languages which are auto-generated from other languages --- have not been seen as practical, since there was no guarantee that the auto-generated language could be efficiently parsed.

With Marpa, this barrier is raised. As an example, Marpa::R2's own parser description language, the SLIF, allows "precedenced rules". Precedenced rules are specified in an extended BNF. The BNF extensions allow precedence and associativity to be specified for each RHS.

Marpa::R2's precedenced rules are implemented as a true second order language. The SLIF representation of the precedenced rule is parsed to create a BNF grammar which is equivalent, and which has the desired precedence. Essentially, the SLIF does a standard textbook transformation. The transformation starts with a set of rules, each of which has a precedence and an associativity specified. The result of the transformation is a set of rules in pure BNF. The SLIF's advantage is that it is powered by Marpa, and therefore the SLIF can be certain that the grammar that it auto-generates will parse in linear time.

Notationally, Marpa's precedenced rules are an improvement over similar features in LALR-based parser generators like yacc or bison. In the SLIF, there are two important differences. First, in the SLIF's precedenced rules, precedence is generalized, so that it does not depend on the operators: there is no need to identify operators, much less class them as binary, unary, etc. This more powerful and flexible precedence notation allows the definition of multiple ternary operators, and multiple operators with arity above three.

Second, and more important, a SLIF user is guaranteed to get exactly the language that the precedenced rule specifies. The user of the yacc equivalent must hope their syntax falls within the limits of LALR.

References, comments, etc.

Marpa has a semi-official web site, maintained by Ron Savage. The official, but more limited, Marpa website is my personal one. Comments on this post can be made in Marpa's Google group, or on our IRC channel: #marpa at freenode.net.

Header image by Tambako the Jaguar. Some rights reserved.