In article <38D08B07.7587F6E4@ij.net>, Matt Giwer <jul### [at] ijnet> 
wrote:

> 	Maybe you have not looked around? There are enough free ones out
> there that I could make an 18-wheeler and have spares. Ain't a
> dime's worth of difference among them in my never humble opinion. 

I know there are a lot of free parser frameworks/libraries, I would 
prefer to use a fairly standardized one like Flex/Bison or write one of 
my own which I could understand. I plan on looking into Flex and Bison 
to see if they have what I need.


> > While those might be good for people who want rapid development, I am
> > not sure they would apply in my case. I do think there is a set of
> > Bison/Flex(or is it Flexx?) tools for CodeWarrior, but I have never 
> > used
> > that kind of thing.
> 
> 	Not quite the same thing. In the days of patchpanels it was
> considered a daunting task just to parse words (trailing
> whitespace) properly. That turned out to be simple. Praise the
> lord and pass the card deck. 

Not quite the same thing as what? They are parser tools...I need a 
parser, and I would prefer to know how they work in some detail first.


> 	Converting infix to postfix notation to machine language turned
> out to be easy also. Doing so efficiently turned out to be a
> bitch and half. How many passes does your compiler make? 

Which compiler, the one I develop in C/C++ on? I really have no idea. 
And what does this have to do with C-SDL?


> > Actually, I don't have it. All the books I have are a couple standard
> > "learn C++" books:
> > Teach Yourself C++ in 21 Days(got this when I took C++ at school)
> > Programming with C++
> > Rescued by C++
> > C++ Primer Plus(this one is actually my favorite, I rarely use the
> > others)
> > And a couple C and Java books, and one Pascal book(also from a class I
> > took at school).
> 
> 	That is something else entirely. The theory and practice of
> compilers vice parsers (which are more like tokenizers in BASIC)
> is something else entirely. Think about it. Everything you write
> has to get to machine code instructions. 

Something else entirely from *what*? I listed the books I had, said they 
were mostly for learning the languages, and said I don't have any books 
on parsers or other algorithms.
And compilers don't interest me, nothing I do goes to machine code 
instructions except as data(and I can ignore the fact that my C++ code 
is converted to machine code), the only thing my program would do is 
convert C-SDL to POV-Script.


> > I don't have any books on algorithms or programming theory. I don't 
> > have much money to buy them either... :-(

> 	No library?

No good ones nearby, unfortunately. I don't live in a remote, 
unpopulated area, but we are a relatively long way from that kind of 
thing. And no transportation other than my parents, although I will be 
taking drivers training in June.

-- 
Chris Huff
e-mail: chr### [at] yahoocom
Web page: http://chrishuff.dhs.org/

Post a reply to this message