-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 25.06.2014 11:37, Luca Bruno wrote: So I will answer from another side: what is the indicator, that wip is or is not ready? So today's evening I'll open bug for WIP/Transform bugs in vala bugzilla. And maybe should I ask next question: when one prepares patch for particular bug where should it be sent to? Or maybe send git pull requests? In Vala hacking I haven't found clear answer for that question above. How is it possible directly when the parser, lexer and semantical analysis loose information ( white-spaces, comments, '@' operator, loops shape etc.) ? wip branch now also doesn't solve all of these, but anyway it seems to be the step in right direction. It is possible to get the indication where particular terminals / non-terminals begin and end in source files, but the refactoring after semantic analysis seems to be not always straightforward operating fully on AST. T. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTqr6RAAoJEEji0kirYj2EhvwP/iXKLZRpYMEhV7RXAmKG2KQ9 nt344EwZDHBVxzry/VKSRX60Nxo/mhpA7ISNfxAkYwpbTpJWysofvY5ZChjrkHko +0IxWh3y6Z2mt0qlmdueDePheu1EBVBtxA+mzV595ShXNk5vW6StAKtR9H/GG9m5 NeVCtCbbvnpq8q4uqGSile/meV8QNq8viH9Q4s7lOPlNkYlovwAZHbpsm2hjUnfw cL2HUojUuZuLQNJox7SByE95zdgpzT/X9ITx2ZlRdlfordBqTcYltqJ2A870fHvH USEuyYmU4GViPLVz0EDruchZa0Sm2TDlI8XvRnAPaVh8XSLIPtL4yhuAiwaOrXcW QewVx/x2rV7m30QUimPNt6gtX0vTQ5a1ZXXE0jAkDTvwU+6AWeG9MU/JV/zG3Z19 X9jPuWEUj+rDkL3hGWL9+O8YurckQCON31gep3OLd4NW9iSvCWFfHGzX/+VysGzB L7J2krabzq3HQbTqQLINlj8sUoVNE2489NLaQRf27Gnb2mID3NGE1M4NsZqTR3hG rM+WDhQOqk1VevKQuUszNJsqTau79MD4+nhCkglnHwGAumpD/3ApoLOEpEGAuXBO sVguL52DcYg3zYQvOyx7FVrFjA7MnvW/c5Zxyzz8ZFvAagCofyR9PGU+1fJrW2Mm rIrf+aRHr2GubBAU4aTe =zeyJ -----END PGP SIGNATURE-----
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature