From 7f1b344f997e49aaf3fa1968c6e739503bda2e5f Mon Sep 17 00:00:00 2001 From: ragnar Date: Sat, 25 May 2024 12:46:24 +0200 Subject: [PATCH] Update effective-lexing.md to more clearly callout the lexing API MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I coerced some of my students into trying out parsley. They seem to like it in general, but they missed the existence of the lexing API, and spend some time implementing their own lexer. This tries to make the callout in the beginning more “in your face”. --- docs/tutorial/effective-lexing.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/tutorial/effective-lexing.md b/docs/tutorial/effective-lexing.md index 4c6c5b22f..4d7408cbb 100644 --- a/docs/tutorial/effective-lexing.md +++ b/docs/tutorial/effective-lexing.md @@ -5,9 +5,9 @@ laika.site.metadata.description = "How to handle low-level tokenisation in a par # Effective Lexing @:callout(info) -Note that the start of this page describes the underlying fundamentals behind -lexing with parser combinators, but this is abstracted by the functionality -at the end. +Parsley offers a user-friendly API for lexing, which is detailed at the end of this document. We recommend using this API for most purposes. + +The initial sections of this document explain the fundamental principles behind lexing with parser combinators. @:@ In the previous post, we saw the basic principles behind handling whitespace in a transparent manner.