Log In  


While reviewing the documentation, I came across the following issues:

    The draw state is reset each time a program is run. This is equivalent to calling:
    clip() camera() pal() color() fillp()

It seems that the result is that of color(6), instead of color().

    peek addr
    poke addr val

        Read and write one byte to an address in base ram.
        Legal addresses are 0x0..0x7fff
        Reading or writing outside causes a fault

Actually, reading outside the valid range silently returns zero.

    Glyph characters (normally typed with shift-A..Z) are stored in .p8 format as $A..$Z.

This seems outdated, as some Unicode characters are now used instead. Appears to have been reported in another thread already.

    Dividing by zero evaluates as the largest possible number: 0x7fff.ffff

If the first argument is negative, it evaluates to 0x8000.0001 instead (which is not the smallest possible number, but it makes sense)

    FILLP(0b0011010101101000.1) -- checkboard with transparent squares

A checkerboard would be 0b0011001111001100.1 actually.

There are mixed tabs/spaces in the two following lines:

    execute a PICO-8 cart headless and then quit
    < > to change the speed.

And finally, minor spelling issues:

  • "tremelo" -> "tremolo"
  • "hexedecimal" -> "hexadecimal" (2 occurrences)
  • "15ps" -> "15fps"

By the way, dset/dget could be deprecated since poke4/peek4 do more or less the same now…

P#47374 2017-12-14 09:34 ( Edited 2017-12-17 16:55)



The per-frame initialization should include palt().

And right now the entire manual is erroneously center-aligned. Icky. Easy fix though.

P#47439 2017-12-16 13:35


dset/dget are an abstraction specific to cartdata. poke4/peek4 can write/read a 32-bit value from any four bytes in the addressable memory region. I'm in favor of the major features of addressable memory having abstraction APIs. I'm also in favor of minor ones not having APIs for a fun sense of hiddenness, though some of these have started getting official documentation.

The online version of the manual has a <center> tag around it that just needs to be removed. The rest of the page is already set up to center a fixed width content region, if that was the original intent. (The contents of the <pre> tag are just the pico8.txt file.)

P#47483 2017-12-17 16:55

Log in to post a comment


New User | Account Help
:: New User
About | Contact | Updates | Terms of Use
Follow Lexaloffle:        
Generated 2018-03-18 00:24 | 0.214s | 1572k | Q:12