wow, I don't know. You must be clear on something here. Are you planning
to debug the compiler or the generated DLL ?
Debug the DLL, that is buily by the compiler, but written in a custom
language.
The question then is how that works (i.e how exaclty the -g option works).
How do you compile
wow, I don't know. You must be clear on something here. Are you planning to
debug the compiler or the generated DLL ?
My idea of events is that you have a grammar for that script language. Now
you write a compiler to parse source code written in that language and
generate a DLL . Is this correct?
Or, perhaps I'm attacking this wrong. Maybe it what I really need to be
doing is trying to figure out how to write a new gcc front-end.
On 1/11/07, Sandon Racowsky <[EMAIL PROTECTED]> wrote:
So if I'm understanding you correctly, I need create something along the
lines of a C macro that append
So if I'm understanding you correctly, I need create something along the
lines of a C macro that appends line numbers around blocks of bison actions
while simultaneously creating my own debugging profile db, so that when I
encounter the C line numbers, I can reference the original source by doing
oooh.. complicated situation :) The bison generated C parser uses #line
compiler directives to point to the line in the .y file while debugging. i.e.,
if you have a file like grammar.y and generate grammar.tab.c using bison,
and try to debug grammar.tab.c, the debugger can point to corresponding
l
On 11 Jan 2007, at 19:44, Jachyra wrote:
If I use bison to essentially parse my
language and generate C code (which gets compiled to a windows
binary), and
then create a debugger that attaches to the DLL that was compiled
in debug
mode (for the sake of argument, lets say I'm just using dbg)
I hope everyone will forgive me for my ignorance, but I have only recently
begun to start learning bison.
The project that I'm working on requires me to build a custom scripting
languague, that will actually compile to a windows DLL, and must have an
integrated debugger. I have been able to work
On 2 Jan 2007, at 23:04, Bill Lear wrote:
I have written a rather extensive parser in C++, using Bison 2.3,
basing it on the example, calc++, provided with the Bison
distribution.
I would like to be able to recover from simple errors in the input
file by making note of them, providing a warn