Re: How to remove the dummy and see prev ?

Stefan,
The documentation is not always very clear, and many links are broken in thes site.
With the following command :

synopsis  -p Cxx -l JavaComments,JavaTags -o ../doc/STK_Index.h.syn ../include/STK_Index.h

I get the following error :

Traceback (most recent call last):
   File "/usr/bin/synopsis", line 181, in ?
     main()
   File "/usr/bin/synopsis", line 178, in main
     processor.process(AST.AST())
   File "/usr/lib/python2.3/site-packages/Synopsis/Processor.py", line 152, in process
     ast = self.processors[0].process(ast, **my_kwds)
   File "/usr/lib/python2.3/site-packages/Synopsis/Parsers/Cxx/Parser.py", line 38, in process
     from Synopsis.Parsers import Cpp
   File "/usr/lib/python2.3/site-packages/Synopsis/Parsers/Cpp/__init__.py", line 9, in ?
     from Parser import *
   File "/usr/lib/python2.3/site-packages/Synopsis/Parsers/Cpp/Parser.py", line 14, in ?
     import ucpp
ImportError: No module named ucpp
make[1]: *** [../doc/STK_Index.h.syn] Erreur 1
make: *** [syn] Erreur 2

I install  Synopsis-04-10-31

Serge
(I don't know python and I have not many time for learning a new language,
nor a new soft, is it possible to have an exemple of a  makefile for a large
project using only synopsis.py (and thus writing all options as strings)? )

Stefan Seefeld a écrit :
> 
> One of the things that changed after version 0.5 is the frontend
> used to instruct synopsis what to do (and how). The config file
> approach used before was replaced with a scripting interface,
> and the command line options to the 'synopsis' tool itself
> changed a little bit, too.
> Please have a look into the tutorial / the examples to see how
> to instruct synopsis to parse a C++ source file. The simplest
> way is via 'synopsis -p Cxx -o foo.h.syn foo.h'.
> See 'synopsis -h' for general help on options and 'synopsis -p Cxx -h'
> for Cxx parser specific help.
> 
> However, for all non-trivial use you may consider using the
> scripting interface (i.e. write 'synopsis.py' driver scripts),
> as expressing all the parameters through command line arguments 
> (i.e. strings !) doesn't scale very well.
> 
> This is all documented in the tutorial, which, incomplete as it is,
> provides however a good starting point.
> 
> HTH,
> 		Stefan