<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Utilities on JFuncMachine</title>
    <link>https://jfuncmachine.org/utilities/index.html</link>
    <description>Recent content in Utilities on JFuncMachine</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <atom:link href="https://jfuncmachine.org/utilities/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>S-Expressions</title>
      <link>https://jfuncmachine.org/utilities/sexpr/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://jfuncmachine.org/utilities/sexpr/index.html</guid>
      <description>The org.jfuncmachine.sexprlang.parser package provides a Parser class that reads a file or string containing one or more S-expressions and returns an SexprItem representing its contents.
By default, the parser only reads the first S-expression, so if you want to parse a whole file of S-expressions, you need to call the parser with the parseMultipleSexprs value set to true.
SexprItem and Subclasses The SexprItem class is the base class for the possibly values in an S-expression.</description>
    </item>
    <item>
      <title>Mapping S-Expressions to Objects</title>
      <link>https://jfuncmachine.org/utilities/mapping/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://jfuncmachine.org/utilities/mapping/index.html</guid>
      <description>While S-expressions can alleviate some of the hassles of parsing, you still have to get the S-expression into a form you can work with. You need to be able, for example, to turn an S-expression representing a function definition into some form that you can eventually use to create a JFuncMachine MethodDef.
The org.jfuncmachine.sexprlang.translate package provides a way of annotating classes so that it is possible to map an S-expression directly onto those classes.</description>
    </item>
    <item>
      <title>Unification</title>
      <link>https://jfuncmachine.org/utilities/unification/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://jfuncmachine.org/utilities/unification/index.html</guid>
      <description>If you are making a language that uses type unification, the TypeHolder class may or may not be of some use. The idea is that a type holder can be empty (the type it holds is still unknown) and it can be unified with other type holders.
If it is unified with another type holder that is empty, then they are linked together. If either one of them is then unified with a type holder that contains a type, then they all will contain that type.</description>
    </item>
  </channel>
</rss>