Buffy,
I am not using Lex/Yacc
Actually, the is no hardcoding for grammer. Grammer is (will be) stored in the knowledge base. This is one of the methods that have enabled me to use compiled code instead of interpreted. As far as the code is concerned, any structure is allowed, at least until it is analyzed for syntax.
The structure of the code should not be an issue as far as implementation goes, the input/output are what I need a windows interface to. The only issue might be the language - IBM PLI. Right now I simply read a file representing user input and write the output to a file.
But implementation is only one of the issues I want to address soon. I really need a good syntax checker/analyzer for the user input and for the generation of the knowledge base. I say generation of the knowledgebase because the knowledgebase file is more than a list of simple sentences, it also has the sentence structure and fields all laid out to reduce computation time on startup.
The other major area actually is the grammer. I was hoping to get the syntax analyzer program so that I wouldn't have to manually set the fields within the knowledgebase for the sentences that contain the rules for grammer. The 115? sentences in the test knowledgebase were quite tedious
Scott|8-)>
