+is encountered while there are no open braces. This implies that
+an input like
+.nf
+GiNaC> class A {
+ > }
+ > ;
+.fi
+is misinterpreted to be complete after the closing brace.
+Instead you have to write
+.nf
+GiNaC> class A {
+ > };
+.fi
+
+.SS SPECIAL COMMANDS
+
+Lines starting with a dot mark special GiNaC-cint commands. Instead of
+.BR "\fB.cmd\fB"
+you can also write
+.BR "\fB//GiNaC-cint.cmd\fB"
+to be compatible with programs that will be compiled later.
+This is mostly useful for the
+.BR "\fB.function\fB"
+declaration.
+
+Lines starting with #! (for #!/path/ginaccint) are ignored.
+
+
+.IP "\fB.cint\fR"
+Switch to cint's interactive mode.
+
+.IP "\fB.function\fR"
+
+Allow a function definition in interactive mode. GiNaC-cint must be
+put into a special mode in order to define a function. After that any
+function definition in valid C++ syntax may be typed in. It becomes
+immediatly available for usage.
+
+.IP "\fB.help\fB"
+
+List a short summary of available commands.
+
+.IP "\fB.quit\fR"
+Exit from GiNaC-cint. Same as
+.BR ".bye" ,
+.BR ".exit" ,
+.BR ".q" ,
+.BR "bye;" ,
+.BR "exit; " or
+.BR "quit;" .
+
+.IP "\fB.read filename\fB"
+
+Read a file from disk and execute it in GiNaC-cint
+(recursive call is possible).
+
+.IP "\fB.redirect [filename]\fB"