Return Type | Method | Usage |
void | RBSetup(Marquee2Arguments mark, String... args) | Open the command-line specified database and output file |
String |
getDatabaseInputFile() |
return the name of the database file |
String |
getOutputFileName() |
return the name of the RB output file |
DB |
getDB() |
return the DB object produced by reading the database |
void | openOut(String filename) | direct RB output to the given file |
void | openOut(PrintStream o) | direct RB output to the given PrintStream |
void | closeOut() | close the opened RB PrintStream or file |
PrintStream |
getOut() |
return the PrintStream object of RB |
String | getDatabase() | return the filename of the current database |
String | getOutputFileName() | return the file name of the current output file |
void | p(String format, Object... args) | print(format,arguments) no line eject |
void | l(String format, Object... args) | println(format, arguments) with line eject |
void |
l() |
print blank line |
void |
l(int n) |
print n blank lines |
> java myRBProgram X.Y.pl [outputfile]
That is, an RB program takes a database file as input (X is the name of the file, Y is the name of its schema, pl
designates a MDELite database), and optionally the name of the output
file. As we'll see shortly, the output file name is computed from
the input file name, and the computation is specified in the RBSetup
method. For debugging purposes, I specify an explicit output file
(say "out.txt") to avoid output file proliferation. The basic
template of a RB program is:---demo---
}
:::test/RunningBear/TestData/x1.classes.pl:::
Here is the desired output::::test/RunningBear/Correct/x1.txt:::
The extra code that is added to the template above to generate this is:---rest---
By invoking method genclass with argument true, separate .java files are produced per class. That's about it.