> -Ursprüngliche Nachricht-
> Von: Gabriel Dos Reis [SMTP:[EMAIL PROTECTED]
>
> "Giovanni Bajo" <[EMAIL PROTECTED]> writes:
> | Ebke, Hans-Christian <[EMAIL PROTECTED]> wrote:
> |
> | > I have to write this in Outlook, so I don't even try to get the
> quoting
> | > right. Sorry. :-(
>
"Giovanni Bajo" <[EMAIL PROTECTED]> writes:
| Ebke, Hans-Christian <[EMAIL PROTECTED]> wrote:
|
| > I have to write this in Outlook, so I don't even try to get the quoting
| > right. Sorry. :-(
|
| http://jump.to/outlook-quotefix
|
| > But it would break applications relying on the old format
Ebke, Hans-Christian <[EMAIL PROTECTED]> wrote:
> I have to write this in Outlook, so I don't even try to get the quoting
> right. Sorry. :-(
http://jump.to/outlook-quotefix
> But it would break applications relying on the old format.
There is no format either. dump-tree is *very* specific of
cc.gnu.org
> Betreff: Re: extension to -fdump-tree-*-raw
>
> @54 string_cst type: @61 strg: "wrong
> type:\n\0\0\xaf\x03\x03foo\"bar" lngt: 19
>
> This would not need a different special option.
>
But it would break applications relying on the
Ebke, Hans-Christian <[EMAIL PROTECTED]> wrote:
> So to resolve that problem I took the gcc 4.0.1 source code and patched
> tree.h and tree-dump.c. The patched version introduces two new options for
> -fdump-tree: The "parseable" option which produces unambiguous and easier
to
> parse but otherwis
Hi,
wanting to obtain gcc's parse tree I found the -fdump-tree option.
Specifically the -fdump-tree-original-raw output contains all of the
information I need. When I tried to write a parser for the tree dump I
noticed, however that the output might contain ambiguities which can't be
resolved an
