pacc logo

To Do

The todo list is divided into blockers, items which are expected to be done before the next release, and laters, which are not expected to be in the next release. The next release will be pacc-0.1 (wokou).

Blockers

  • " does not work in character classes

Laters

  • complete support for void types: void start rule?
  • fix nested seq in guards and/or make nested seq work
  • fix check_redef() to not be O(n²)
  • investigate allocating evlis statically (we can calculate its maximum size, but this may be much larger than is typically used, so static allocation won't necessarily save space, but i suspect in practice it's a win almost all the time)
  • see if there's anything we can do about making * return a vector
  • report errors in terms of sugared syntax
  • implement s_free(). (We could use a flag in struct s_node to say if the text member came from malloc() or not.)
  • consider implementing rep-rules
  • autoconfiscation (later because I really want to make at least one more public release with my beautiful pristine makefile)
  • packages for (at least) Fedora and Debian
  • parser optimization
  • XXX cleanups
  • review
  • more research
  • permissions (since I won't actually distribute the Java parser yet)
  • worry a lot about memory management
  • don't run the evaluation code till pacc_result() is called
  • when -d is not specified, include fn prototypes so self-contained grammars don't need to

Ongoing

  • pore over the output of the compiler for improvements

Completed

Will be in the next release:

  • fix a bug in the code that creates feeding grammars
  • value inheritance, so a rule like S ← t:That { t } / ... can instead be written S ← That / ...
  • pacc_destroy() now frees all memory
  • fixed a bug where malloc size argument was not scaled (thanks glibc / valgrind!)
  • rule not reached is now a warning, not a fatal error

Were in the pacc-0.1 (wōkòu) release:

  • support all C99 character escapes
  • UTF-8 support in coordinates
  • memoize _pacc_coords()
  • bring pacc0.c up to date (character classes, right anchoring)
  • UTF-8 support in character classes
  • refactor Unicode reading code in any and cclass matchers
  • make → 5 work
  • warn about bad character classes
  • pacc_error() now returns an error string, instead of outputting it
  • there is a new pacc_pos() function
  • check that all rules are reached
  • YY_input() no longer takes a name parameter (but YY_wrap() does)
  • YY_error() returns a string that doesn't include the name
  • detect rules being redefined
  • expose ability to alter prefix
  • macro and variable to enable tracing
  • move all names into the pacc_ / _pacc_ namespaces
  • feed points are now marked with $; the -r option is gone
  • pacc0.c is now built from pacc.pacc
  • detect erroneous rebinding of names
  • Put ] first in a character class to match it; disallow empty class
  • basic documentation

Were in the pacc-0.0 (ronin) release:

  • minimal documentation
  • UTF-8 support in any matchers
  • anchor all grammars left and right
  • complete command line interface
  • implement --feed / partialization (this is my unique selling point)
  • scoping -- names in pacc grammars are supposed to scope statically over sequences, but that clearly isn't the case at the moment, otherwise test/pacc/scope1.pacc would compile!
  • add #line directives
  • detect left recursion
  • one instance of each type per union
  • dynamically allocate everything

Never forget

todo is Spanish for everything

Last updated: 2015-06-04 20:24:05 UTC

Donate

Support the development of pacc with a donation! We accept donations in BitCoin or via PayPal who handle almost any other form of payment.

News

Users

One thing that pacc has lacked all the way along is users. It turns out to be really hard to write decent code without those darned users probing the dark corners. Read More...

Default expressions

I finally got round to implementing a simple but highly useful feature in the language, which I'm calling default expressions. It's probably simplest to explain by showing the test case: Read More...

See more news articles

feed