Turbo Rascal Syntax error, “;” expected but “BEGIN”

Turbo Rascal Syntax error, “;” expected but “BEGIN” (Turbo Rascal SE, TRSE) is a complete suite (IDE, compiler, programming language, image sprite level resource editor) intended for developing games/demos for the 8-bit 6502 line of computers (C64, C128, VIC-20, NES) with a focus on the Commodore 64. With the benefits of a modern IDE (error messages, code completion, syntax highlightning etc) and a bunch of fast built-in tools, it has never been easier to program for the Commodore 64.

TRSE runs on Windows 64-bit, Linux 64 bit and OS X. Development begain on feb 24th 2018. The TRSE framework contains a number of project examples for the C64, VIC-20, C128 and NES, including almost 40 runnable tutorials.

Join TRSE on facebook!

Resources (current version: 0.05)

What is Turbo Rascal Syntax error, “;” expected but “BEGIN”?

In a nutshell, Turbo Rascal Syntax error, “;” expected but “BEGIN” is a complete suite for developing for the Commodore 64 (And the C128, VIC-20, NES etc). It is written in Qt C++, and runs as a stand-alone application that contains various tools for developing and deploying projects for the MOS6502‚ô• processor. The TRSE suite includes the following stuff:

  • A semi-fully functional Pascal-like compiler that compiles to DASM assembler files.
  • A built-in assembler
  • A substantial amount of handy built-in assembler functions optimized for easy-to-use and fast C64 operations (typically memory operations, zero paging, copying, sprite handling, IRQs, clearing screen, drawing to screen)
  • Optimizer
  • RasLib, the Turbo Rascal C64 library¬† (Level rendering, scrolling, high-level stuff)
  • Multicolor/hires image editor with image importer
  • Document-style editor for images and source files with syntax highlighting and code completion.
  • Character editor (multicolor, regular color etc)
  • Sprite editor
  • Character-based movie editor
  • Disk support using Krill’s loader. Automatic creation of .d64 disks with files.
  • Cycle counter per line, displayed in the editor
  • Level editor with user defined data
  • Memory usage analyzer tool (creates an image of the memory map of the current project)
  • Automated decruncher for compressed data (images, levels, sound etc)

But.. why?

The author had a C64 as a kid, but never got the hang of understand proper programming until the x86-era of the 90’s. This is his way of mending the hole in is soul. In addition, he hopes that he’ll get filthy rich & famous off this project.


Free of charge. How the “rich” part will be achieved is still up for debate.