search for: fibinc

...I > > submit a test case (it would have to be a C file that links in the > > parser)? > > Sure, that sounds good. I'd definitely prefer that it be tested before it > goes into CVS. Perhaps adding something to llvm/examples would be a good > way to go. I made a 'FibInC' example that uses my little c-wrapper (which in turn uses this). I can submit all of those when they are cleaned up (and linking correctly - more on that later). > One suggestion, you might change the API to be something like this: > > ParseAsmString(const char *, Module *) > &...

...ffers for flex when we are > * done reading our input! > */ > yy_delete_buffer(YY_CURRENT_BUFFER); > return EOF; > } > > Which should take care of it. Ok, that makes sense. > I made a 'FibInC' example that uses my little c-wrapper (which in turn > uses this). I can submit all of those when they are cleaned up (and > linking correctly - more on that later). cool, ok. >> One suggestion, you might change the API to be something like this: >> >> ParseAsmString...

On Fri, 13 May 2005, Alexander Friedman wrote: >>> This requires being able to parse strings. The LLVM 'Parser.h' interface >>> (and implementation) has the built in assumptions that it will always be >>> parsing from the file system. Would you guys accept a patch that makes >>> it more general (ie, parse from file or string)? >> >> Yes,

> > This requires being able to parse strings. The LLVM 'Parser.h' interface > > (and implementation) has the built in assumptions that it will always be > > parsing from the file system. Would you guys accept a patch that makes > > it more general (ie, parse from file or string)? > > Yes, that's a generally useful thing to have, I'd like to see it