X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;ds=inline;f=src%2Fedu%2Fberkeley%2Fsbp%2Fpackage.html;h=e8863d0057dca99ce02165dc605cdc21e9388914;hb=c404939a6dfed4dcfdca5ede08db99b3e5ef0c91;hp=6dd748e2f9930d3137e9c23308c29dc8ca050b50;hpb=cd8ef445dd069efec7d47ab1df0c1f93caa2beac;p=sbp.git
diff --git a/src/edu/berkeley/sbp/package.html b/src/edu/berkeley/sbp/package.html
index 6dd748e..e8863d0 100644
--- a/src/edu/berkeley/sbp/package.html
+++ b/src/edu/berkeley/sbp/package.html
@@ -5,7 +5,8 @@
APIs and all other packages are subject to change in future
releases.
Be sure to read doc/jargon.txt and the description below.
+ href=#package_description>description below; there is also a
+ faq a the end of this document.
+I get the error java.lang.Error: multiple non-dropped elements + in sequence, what does this mean? +
+ ++Note: this question deals with the +package edu.berkeley.sbp.meta, which is not considered +stable. +
+ ++When using the class edu.berkeley.sbp.meta.Grammar, you must +supply an instance of Grammar.Bindings; this instance tells +SBP how to create a parse tree for an expression using the parse trees +of its subexpressions. +
+ ++SBP has no trouble determining what to do when parsing an expression +that drops all of its subexpressions, or all but one -- for example: +
+ ++... in this example, only C is "non-dropped". In this case, +the result of parsing A is simply the result of parsing +C. +
+ ++However, if we were to leave more than one element un-dropped, SBP +needs to know how to form a single tree out of the two non-dropped +subtrees. There are two ways to do this. The simplest is to provide +a tag -- a string which becomes the common parent of the two subtrees: +
+ ++If you are using AnnotationGrammarBindings, you can also deal +with this situation by declaring a method/inner-class whose name +matches the nonterminal (Expr) and has appropriate +annotations. This is fairly advanced stuff, and the code it uses +isn't quite as mature as the rest of the code. +
+ + ++ +Bug reports are especially appreciated when you submit them as a test +case (here's the +grammar and some +examples). + +This way we can add your bug report as part of the regression suite, +and be sure we never release a new version in which the bug has crept +back in! + +
+ + +