Re: File parser

"Rune Strand" <[EMAIL PROTECTED]> writes: Thanks. This shows definate promise. I've already tailored it for what I need, and it appears to be working. -- "Society in every state is a blessing, but Government, even in its best state, is but a necessary evil; in its worst state, an intolerable

Re: File parser

infidel wrote: >Angelic Devil wrote: > > ... >Some time ago I was toying around with writing a tool in python to >parse our VB6 code (the original idea was to write our own .NET >conversion tool because the Wizard that comes with VS.NET sucks hard on >some things). I tried various parsing tool

Re: File parser

Angelic Devil wrote: > I'm building a file parser but I have a problem I'm not sure how to > solve. The files this will parse have the potential to be huge > (multiple GBs). There are distinct sections of the file that I > want to read into separate dictionaries to perform different > operations

Re: File parser

Take a closer look at SimpleParse/mxTextTools We have used these to parse log files of several 100 MB with simple and complex grammars up to 250+ productions. Highly recommended. /Jean Brouwers PS) For an introduction see also this story

Re: File parser

It's not clear to me from your posting what possible order the tags may be inn. Assuming you will always END a section before beginning an new, eg. it's always: A some A-section lines. END A B some B-section lines. END B etc. And never: A some A-section lines. B some B-section lines. END B

Re: File parser

Angelic Devil <[EMAIL PROTECTED]> wrote: > BAR > END BAR > > FOOBAR > END FOOBAR man csplit -- William Park <[EMAIL PROTECTED]>, Toronto, Canada ThinFlash: Linux thin-client on USB key (flash) drive http://home.eol.ca/~parkw/thinflash.html BashDiff: Super Bash shell h