On 3/15/07, Fran=E7ois du Vignaud <fra...@ya...> wrote:
>
> Hi Roman,
>
> I have retried using the latest cvs snapshot and it return the same resul=
ts.
> Have you succeeded to reproduce the bug on your side ?
> best regards,
Yes I am. Unfortunately nothing could be done :-(. From time to time
I check option to add another back-end to pygccxml. On Linux I found a
way to get information from source files without gccxml invocation. On
Windows I saw next options:
1. bsckit - MSVC compiler generates "browse source code" files. It
also supplies a library which provides API. The problem with this
approach
is that information is not complete. There is no function argument
types, function exception specification and few other pieces of
critical
information.
2. pdb files - program debug information files. There is API to work
with them, but it is toooooooooo complex and also lacks some critical
information.
3. Use Visual Studio automation to extract information from the source file=
s
( http://msdn2.microsoft.com/en-us/library/envdte.codeclass(VS.80).aspx =
)
I read in the MSVC 8.0 team blog that they use their compiler to
extract information from source files. Using PyWin32 we can work with
MS Visual Studio via COM interface.
4. It is possible to use some other parser( doxygen, SWIG, SIP, synopsys )
5. Your suggestion here...
>From this list I think (3) is the most promising approach and it
should not be too difficult to implement and check it. The problem is
that at home I don't have Windows machine, otherwise I would already
implement it.
It also worse to take a look on http://synopsis.fresco.org/. It uses
Wave - fully complaint C++ preprocessor, but the documentation for the
project almost does not exists.
I'll be glad to know your opinion and suggestions.
--=20
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/
|
