<div dir="ltr">Thanks for your information. However, what I intend to work on is a Swift-to-JS translator, which I guess probably need to stick with the upstream anyway. I think that make the output a bit more parsing-friendly will not harm, will it?<div><br></div><div>Moreover, if you do not suggest parse the dumped AST, is there any recommended way to reuse the compiler’s front-end?</div><div><br></div><div>Thank you,</div><div>Minsheng</div></div><br><div class="gmail_quote"><div dir="ltr">Dmitri Gribenko <<a href="mailto:gribozavr@gmail.com">gribozavr@gmail.com</a>>于2016年5月9日周一 上午9:10写道：<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sun, May 8, 2016 at 8:22 PM, Minsheng Liu via swift-dev<br>
<<a href="mailto:swift-dev@swift.org" target="_blank">swift-dev@swift.org</a>> wrote:<br>
> Hi,<br>
><br>
> I notice that currently the dumped AST contains a parsing-unfriendly “decl”<br>
> attribute like this:<br>
>> decl=fib.(file).func decl.b@fib.swift:4:9<br>
<br>
Dumped AST is not meant to be machine parseable. The format is<br>
subject to change (and it does frequently change). Please don't parse<br>
it, your tools will break with new compiler releases.<br>
<br>
Dmitri<br>
<br>
--<br>
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if<br>
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <<a href="mailto:gribozavr@gmail.com" target="_blank">gribozavr@gmail.com</a>>*/<br>
</blockquote></div>