The lambda-st runtime and the VSCode extension (.vsix) are provided free of charge to partner companies that have signed an NDA; they are not publicly distributed. Please get in touch before evaluating.

Your First Surgery

Create find_todos.st:

"Extract all TODO comments from source code"
| grammar source matches |

grammar := Grammar from: '
    todo: "TODO" /[^\\n]*/
    %ignore /./
'.

source := File read: 'target.js'.
matches := Grammar findAll: grammar in: source.

matches do: [:m |
    (m at: 'text') displayNl.
].

Run it:

lambda-st run find_todos.st

You just performed code surgery. No regex wrestling, no AST libraries - just declare the pattern and extract.

Note the doubled backslash in /[^\\n]*/. A string literal reads \n as a real line feed - one of five escapes (\n \r \t \0 \\) Lambda Smalltalk reads for affinity with C, the shell, JSON and regex - and a grammar rule ends at a line feed, so a single backslash would cut the rule in half. \\n hands the grammar the two characters \ and n, which is what the regex wants. Every other backslash (\w, \d, \s) passes through untouched, and regexMatches: and the other regex messages take '[^\n]*' as written - it is the grammar lexer that needs the doubling. The other two places to double are a Windows path ('C:\temp' holds a tab) and a regex matching a backslash ('\\\\'). See String Literals in the API reference.

VSCode Extension

Full IDE support for serious work:

Setup

  1. VSCode: Extensions → "..." → "Install from VSIX..."
  2. Select the lambda-smalltalk-x.x.x.vsix file

The extension auto-detects lambda-st-lsp and lambda-st-dap in your workspace or PATH.

Debugging

  1. Open a .st file
  2. Click line gutter to set breakpoints
  3. F5 to start debugging
  4. Step through, inspect variables, evaluate expressions

Library and Plugin Search Paths

When you use Module import: or Plugin load:, Lambda Smalltalk searches these locations in order:

PriorityPathDescription
1Current directory./lib/Text/Text.st
2Executable directoryWhere lambda-st is installed
3LAMBDA_ST_LIB_PATHCustom library paths
4LAMBDA_ST_PLUGIN_PATHCustom plugin paths

Environment variables use ; as separator on Windows, : on Unix.

Example: If you install Lambda Smalltalk to C:\lambda-st\, the bundled libraries at C:\lambda-st\lib\ are automatically found.

Module import: 'Text'.        "Loads lib/Text/Text.st"
Plugin load: 'excel_plugin'.  "Loads plugins/excel_plugin.dll"

Next Steps