[Vala] wip/transform branch in git
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Several questions: 1) when could I expect ( if should I ) the wip/transform branch to be merged with master? 2) where should I report bugs (regressions) in wip/transform branch - to regular vala bugzilla? The idea of separate transformation from check() seems to be very attractive - it opens the possibility for vala library to be foundation of code refactoring tools / IDEs. Besides keeping out transformation from semantic analysis maybe would be reasonable to implement keeping in AST original representations of terminals non-terminals to be able to provide 100% reliable dump of parserd analyzed source code - this way implementing more advanced IDEs with refactoring capabilities with libvala should be much simpler, regards, T. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTqpbhAAoJEEji0kirYj2EUmsP/2krNTHV6zElMKQGi2mGX//l yfeAioedSLueYBzul7jMbdOkIlthgvnjOtMASYWgOfAF7LsLlrRRxLXzRt0uksjm ILzudR2i2hQ604S+CsgeHjduGIuYRhT3EIcdSEpg42hw6ErkL9lq2NB31T0CdJTg Ak67TATspVowI0MVL8WYLwxlq82QrpBNdaeanOZyDcFiTfozEafMWxj8z/pUAw4u C5fakak/1yyTiO4z661Vw3mGBrIrmSFk/pyHCIl5FlJLR5XrKCyEf9ff3z8woC12 RaAuGpcJosND/xPspvl+7jHvBxYA/8AZbHV0vVXwnP6woeNYlWcfVybMidam8GXm gl5exOXMhSlCorJxLCxFMNIppBnVVyEfw14hH1DhIK3cdgXo2ctiQF0R50IK3wIG j6p2uAuCZHAmxkCi5pbRD9Vi54FFRCatqMOeUp9D4UT/NGwU2L7V1Bb0ym5BqAm5 Zhnq9P0QInT5FykwPdxUxqTaDLLLo9wEdsziBcEnHy60lNNTviQX1E5fqcDeP05v 84cmZFAnwmLGbvcw9u+wwkgxnDGY1QHordvN1HgpgX/x+Yw23uBWX3zdgS0DM4G8 IUlAMVxYKrfV8wVLv3JeRfZJ/4HhVSxf8xXvaKpxuvkeYKm4a0ypCCQLkMS5YG5W 6WhDv+HGgYtXRJpMJnXY =7DKT -END PGP SIGNATURE- smime.p7s Description: S/MIME Cryptographic Signature ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] wip/transform branch in git
On 25/06/2014 11:31, Tadeusz Szczyrba wrote: Hello, Several questions: 1) when could I expect ( if should I ) the wip/transform branch to be merged with master? When it's ready :) 2) where should I report bugs (regressions) in wip/transform branch - to regular vala bugzilla? Since it's a wip branch there's no real place for reporting bugs. But maybe we can open a single bug for all the wip/transform bugs. Feel free to open it and list all your concerns there. The idea of separate transformation from check() seems to be very attractive - it opens the possibility for vala library to be foundation of code refactoring tools / IDEs. Besides keeping out transformation from semantic analysis maybe would be reasonable to implement keeping in AST original representations of terminals non-terminals to be able to provide 100% reliable dump of parserd analyzed source code - this way implementing more advanced IDEs with refactoring capabilities with libvala should be much simpler, The transormations are a runtime thing, that has nothing to do with IDE refactoring, which is already doable with libvala. Best regards, ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] wip/transform branch in git
-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- smime.p7s Description: S/MIME Cryptographic Signature ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] New tiny helper for unit testing
Looks very good! Keep going Date: Fri, 13 Jun 2014 15:58:02 +0900 From: yusuke.ishida@gmail.com To: vala-list@gnome.org Subject: [Vala] New tiny helper for unit testing Hi all, I've create a new tiny helper 'vtth' for unit testing. Please try it. https://github.com/y-ishida/vtth Features of vtth are as follows: - Only requires a file 'vtth.vala'. - Colored OK or NG are output at each assertion. - You can select actions at the assertion failed, wheter to abort or continue the program. - The simple (one line) report which contained counts of OK, NG and total of these is output. - Methods and parameters related the test case can be grouped into a class. Regards, Y.Ishida ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] wip/transform branch in git
On 25/06/2014 14:20, Tadeusz Szczyrba 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. Simply attach a patch to bugzilla. wip/transform is of course not ready, otherwise it would have been merged :) It's already working for most things, the last bug I hit was with dbus (e.g. try compiling rygel with wip/transform and you'll able to reproduce that). In other words, everything is set, many bugs have already been fixed, so it's only about fixing the remaining bugs that have been of course introduced by the massive refactoring. 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. wip/transform has nothing to do with that. It avoids losing information in the ast analysis - codegen step. It brings codegen stuff at the ast level AND moves ast transformations after the control flow analysis to avoid losing information in the control flow step. You can read a detailed overview here: http://valajournal.blogspot.com/2014/02/what-to-expect-from-wiptransform-branch.html ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
[Vala] cairo binding bug?
According to http://www.cairographics.org/manual/cairo-Paths.html, The path may be either the return value from one of cairo_copy_path() or cairo_copy_path_flat() or it may be constructed manually. But, trying to construct a path manually, i.e., var path = new Cairo.Path (); gives a compiler error: error: `Cairo.Path' does not have a default constructor Am I doing this the wrong way, or is this a binding bug? Nice day Nor Jaidi Tuah PRIVILEGED/CONFIDENTIAL information may be contained in this message. If you are neither the addressee (intended recipient) nor an authorised recipient of the addressee, and have received this message in error, please destroy this message (including attachments) and notify the sender immediately. STRICT PROHIBITION: This message, whether in part or in whole, should not be reviewed, retained, copied, reused, disclosed, distributed or used for any purpose whatsoever. Such unauthorised use may be unlawful and may contain material protected by the Official Secrets Act (Cap 153) of the Laws of Brunei Darussalam. DISCLAIMER: We/This Department/The Government of Brunei Darussalam, accept[s] no responsibility for loss or damage arising from the use of this message in any manner whatsoever. Our messages are checked for viruses but we do not accept liability for any viruses which may be transmitted in or with this message. ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] cairo binding bug?
Not a bug, Path is a compact class and haven't constructor. So when you'll have a Context, do this : Cairo.Context cr; .. Cairo.Path path = cr.copy_path(); regards ;) 2014-06-26 3:24 GMT+02:00 Nor Jaidi Tuah norjaidi.t...@ubd.edu.bn: According to http://www.cairographics.org/manual/cairo-Paths.html, The path may be either the return value from one of cairo_copy_path() or cairo_copy_path_flat() or it may be constructed manually. But, trying to construct a path manually, i.e., var path = new Cairo.Path (); gives a compiler error: error: `Cairo.Path' does not have a default constructor Am I doing this the wrong way, or is this a binding bug? Nice day Nor Jaidi Tuah PRIVILEGED/CONFIDENTIAL information may be contained in this message. If you are neither the addressee (intended recipient) nor an authorised recipient of the addressee, and have received this message in error, please destroy this message (including attachments) and notify the sender immediately. STRICT PROHIBITION: This message, whether in part or in whole, should not be reviewed, retained, copied, reused, disclosed, distributed or used for any purpose whatsoever. Such unauthorised use may be unlawful and may contain material protected by the Official Secrets Act (Cap 153) of the Laws of Brunei Darussalam. DISCLAIMER: We/This Department/The Government of Brunei Darussalam, accept[s] no responsibility for loss or damage arising from the use of this message in any manner whatsoever. Our messages are checked for viruses but we do not accept liability for any viruses which may be transmitted in or with this message. ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list ___ vala-list mailing list vala-list@gnome.org https://mail.gnome.org/mailman/listinfo/vala-list
