<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.1" -->
<?xml-stylesheet href="http://sdp.soapi.com/lib/styles/feed.css" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://sdp.soapi.com/feed.php">
        <title>SDP ptpscript</title>
        <description></description>
        <link>http://sdp.soapi.com/</link>
        <image rdf:resource="http://sdp.soapi.com/lib/images/favicon.ico" />
       <dc:date>2009-08-25T05:23:02+01:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://sdp.soapi.com/ptpscript:basic_syntax?rev=1169633752"/>
                <rdf:li rdf:resource="http://sdp.soapi.com/ptpscript:commands?rev=1169633752"/>
                <rdf:li rdf:resource="http://sdp.soapi.com/ptpscript:constants?rev=1169633752"/>
                <rdf:li rdf:resource="http://sdp.soapi.com/ptpscript:directives?rev=1169633752"/>
                <rdf:li rdf:resource="http://sdp.soapi.com/ptpscript:errors?rev=1169633752"/>
                <rdf:li rdf:resource="http://sdp.soapi.com/ptpscript:expressions?rev=1169633752"/>
                <rdf:li rdf:resource="http://sdp.soapi.com/ptpscript:functions?rev=1169633752"/>
                <rdf:li rdf:resource="http://sdp.soapi.com/ptpscript:history?rev=1169633752"/>
                <rdf:li rdf:resource="http://sdp.soapi.com/ptpscript:operators?rev=1169633752"/>
                <rdf:li rdf:resource="http://sdp.soapi.com/ptpscript:types?rev=1169633752"/>
                <rdf:li rdf:resource="http://sdp.soapi.com/ptpscript:variables?rev=1169633752"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://sdp.soapi.com/lib/images/favicon.ico">
        <title>SDP</title>
        <link>http://sdp.soapi.com/</link>
        <url>http://sdp.soapi.com/lib/images/favicon.ico</url>
    </image>
    <item rdf:about="http://sdp.soapi.com/ptpscript:basic_syntax?rev=1169633752">
        <dc:format>text/html</dc:format>
        <dc:date>2007-01-24T10:15:52+01:00</dc:date>
        <title>Basic syntax</title>
        <link>http://sdp.soapi.com/ptpscript:basic_syntax?rev=1169633752</link>
        <description> All PTPScript code is contained within placeholders. Everything outside of the placeholders is ignored by the PTP engine, and everything inside is evaluated as PTPScript code.  At the most basic level, it may only be necessary to display the values ...</description>
    </item>
    <item rdf:about="http://sdp.soapi.com/ptpscript:commands?rev=1169633752">
        <dc:format>text/html</dc:format>
        <dc:date>2007-01-24T10:15:52+01:00</dc:date>
        <title>Commands</title>
        <link>http://sdp.soapi.com/ptpscript:commands?rev=1169633752</link>
        <description> In addition to expressions, PTPScript also has several useful commands. Commands have to be the first non-whitespace part of a placeholder - no terms or operators are allowed in front of them. The remaining part of the placeholder expression is eval...</description>
    </item>
    <item rdf:about="http://sdp.soapi.com/ptpscript:constants?rev=1169633752">
        <dc:format>text/html</dc:format>
        <dc:date>2007-01-24T10:15:52+01:00</dc:date>
        <title>Constants</title>
        <link>http://sdp.soapi.com/ptpscript:constants?rev=1169633752</link>
        <description> Constants in PTPScript are the same as Variables in terms of use, except for a couple of differences. Firstly, they are case-insensitive, and secondly, they are read-only. Apart from that, the naming conventions are the same, and the usage is the sa...</description>
    </item>
    <item rdf:about="http://sdp.soapi.com/ptpscript:directives?rev=1169633752">
        <dc:format>text/html</dc:format>
        <dc:date>2007-01-24T10:15:52+01:00</dc:date>
        <title>Directives</title>
        <link>http://sdp.soapi.com/ptpscript:directives?rev=1169633752</link>
        <description> A Directive is a core language setting, which can be changed by using the Use command. Once a Directive has been set, the behaviour of PTPScript will change accordingly, until another Directive in the same group is set.  For example: &amp;#123; use Natu...</description>
    </item>
    <item rdf:about="http://sdp.soapi.com/ptpscript:errors?rev=1169633752">
        <dc:format>text/html</dc:format>
        <dc:date>2007-01-24T10:15:52+01:00</dc:date>
        <title>Errors</title>
        <link>http://sdp.soapi.com/ptpscript:errors?rev=1169633752</link>
        <description> There is no way to handle errors through PTPScript - appropriate errors will be flagged in the PHP backend and should be handled by the PHP programmer. However, there are a few notes worth making.  When an error is flagged, the template file that th...</description>
    </item>
    <item rdf:about="http://sdp.soapi.com/ptpscript:expressions?rev=1169633752">
        <dc:format>text/html</dc:format>
        <dc:date>2007-01-24T10:15:52+01:00</dc:date>
        <title>Expressions</title>
        <link>http://sdp.soapi.com/ptpscript:expressions?rev=1169633752</link>
        <description> PTPScript code is built completely from expressions. An expression is a combination of Numbers, Strings, Operators (including grouping symbols such as brackets/parentheses), Variables, Constants, and Functions. These terms are evaluated according to...</description>
    </item>
    <item rdf:about="http://sdp.soapi.com/ptpscript:functions?rev=1169633752">
        <dc:format>text/html</dc:format>
        <dc:date>2007-01-24T10:15:52+01:00</dc:date>
        <title>Functions</title>
        <link>http://sdp.soapi.com/ptpscript:functions?rev=1169633752</link>
        <description> PTPScript comes with a number of built-in functions, and these can easily be added to by the backend PHP programmer (or standard functions can be removed, or changed). A function is a PHP process rather than a PTPScript one. Although the same functi...</description>
    </item>
    <item rdf:about="http://sdp.soapi.com/ptpscript:history?rev=1169633752">
        <dc:format>text/html</dc:format>
        <dc:date>2007-01-24T10:15:52+01:00</dc:date>
        <title>History</title>
        <link>http://sdp.soapi.com/ptpscript:history?rev=1169633752</link>
        <description> SOAPI itself dates back several years now. The first SOAPI code was put together sometime in 2000, although it wasn&amp;#039;t until 2001 that it was given the name SOAPI. (For those that care, SOAPI stands for Smart Object API. It did originally stand ...</description>
    </item>
    <item rdf:about="http://sdp.soapi.com/ptpscript:operators?rev=1169633752">
        <dc:format>text/html</dc:format>
        <dc:date>2007-01-24T10:15:52+01:00</dc:date>
        <title>Operators</title>
        <link>http://sdp.soapi.com/ptpscript:operators?rev=1169633752</link>
        <description> An Operator can be thought of as an instruction that modifies one or more terms (values, or expressions - technically called &amp;quot;operands&amp;quot;), in order to produce another value. This operation is itself an expression.  For example: &amp;#123; 4 + 5...</description>
    </item>
    <item rdf:about="http://sdp.soapi.com/ptpscript:types?rev=1169633752">
        <dc:format>text/html</dc:format>
        <dc:date>2007-01-24T10:15:52+01:00</dc:date>
        <title>Types</title>
        <link>http://sdp.soapi.com/ptpscript:types?rev=1169633752</link>
        <description> PTPScript supports the following data types:   Boolean  Number (split into Integer and Float)  String  Array   The documentation will also use the word Mixed to refer to a value that could be more than one type.   To see the type of a value, use the...</description>
    </item>
    <item rdf:about="http://sdp.soapi.com/ptpscript:variables?rev=1169633752">
        <dc:format>text/html</dc:format>
        <dc:date>2007-01-24T10:15:52+01:00</dc:date>
        <title>Variables</title>
        <link>http://sdp.soapi.com/ptpscript:variables?rev=1169633752</link>
        <description> In PTPScript, Variables are simply represented by names. No prefix characters are required, and the Variable name is case-sensitive.  A valid variable name starts with a letter or an underscore, and is followed by any number of letters, numbers, and...</description>
    </item>
</rdf:RDF>
