more foreign to C++ like eg. ::OPEN or #OPEN would be.
I hope this makes sense. :)
Roberto Bonvallet írta:
> Károly Kiripolszky <[EMAIL PROTECTED]> wrote:
> > I've found a brute-force solution. In the preprocessing phase I simply
> > strip out the comments (things insi
Helo again!
When I came up with this idea on how to parse C files with ease, I was
at home and I only have access to the sources in subject in the
office. So I've tried the previously posted algorithm on the actual
source today and I realized my originally example data I've ran the
test with was s
http://kiri.csing.hu/stack/python/bloppy-0.2.zip
Test data now also contains brackets in literal strings.
Claudio Grondi írta:
> Károly Kiripolszky wrote:
> > You're right, thank you for the comment! I will look after how to
> > avoid this.
> And after you have resolved
nted lines from the analyzis as I only have to cope with
production code.
Claudio Grondi írta:
> Károly Kiripolszky wrote:
> > You're right, thank you for the comment! I will look after how to
> > avoid this.
> And after you have resolved this 'small' ;-) detail
You're right, thank you for the comment! I will look after how to
avoid this.
Marc 'BlackJack' Rintsch írta:
> In <[EMAIL PROTECTED]>,
> karoly.kiripolszky wrote:
>
> > and the great thing is that the algorithm can be used with any
> > language that structures the code with brackets, like PHP and
Marc 'BlackJack' Rintsch írta:
> In <[EMAIL PROTECTED]>,
> karoly.kiripolszky wrote:
>
> > and the great thing is that the algorithm can be used with any
> > language that structures the code with brackets, like PHP and many
> > others.
>
> But it fails if brackets appear in comments or literal st
Thx for responding, Szabolcs! I've already tried that, but couldn't
manage to get it to work. The source I tried to parse is a huge MSVC
7.1 solution containing about 38 projects, and I believe the code is
so complex that it has too many different dependencies and GCC just
can't handle them. Btw I'
