On Sun, Jun 10, 2007 at 09:56:44PM +0200, Magnus Hagander wrote:
AFAIK, most other compilers delete their output if it's not valid. Is
there any particular reason why ecpg doesn't do this?
No, not really. Sometimes it comes handy to see what was already
processed, but you're right, it's not
On Mon, Jun 11, 2007 at 08:05:16AM +0200, Michael Meskes wrote:
On Sun, Jun 10, 2007 at 09:56:44PM +0200, Magnus Hagander wrote:
AFAIK, most other compilers delete their output if it's not valid. Is
there any particular reason why ecpg doesn't do this?
No, not really. Sometimes it comes
On Mon, Jun 11, 2007 at 10:03:57AM +0200, Magnus Hagander wrote:
If you find the other behaviour useful, perhaps add a commandline switch
that makes it leave the file around? Just make the
remove-the-file-on-failure default.
Should be fixed now. I don't think such a command line switch is
When working on the ecpg regression stuff things, it's the first time
I've actually used ecpg. And I notice now that it leaves incomplete and
broken files around when it fails. For example, I currently get:
parser.pgc:26: ERROR: syntax error at or near NULLS
when building. I have to
