archive-org.com » ORG » I » IOKE.ORG

Total: 746

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Revision history of "Java integration planning" - IokeWiki
    bytes cur last 18 42 10 February 2009 Olabini Talk contribs 4 298 bytes cur last 15 19 8 February 2009 Olabini Talk contribs 2 209 bytes cur last 15 12 7 February 2009 Olabini Talk contribs 1 645 bytes cur last 20 02 26 January 2009 Olabini Talk contribs 640 bytes New page this information is NOT up to date How to handle Java interop How to handle calling

    Original URL path: https://ioke.org/wiki/index.php?title=Java_integration_planning&action=history (2016-02-13)
    Open archived version from archive

  • Java integration planning - IokeWiki
    Class gt AbstractCollection gt Class AbstractCollection Class gt Object gt Class Object Class gt Serializable gt Class Serializable Class gt Cloneable gt Class Cloneable Class gt Iterable gt Class Iterable Class gt Collection gt Class Collection Class gt List gt Class List Class gt RandomAccess gt Class RandomAccess Class lt pre gt pre This is slightly simplified too but the basic idea is that Class has to be part of the same inheritance chain because there only exists one namespace in Ioke This is slightly simplified too but the basic idea is that Class has to be part of the same inheritance chain because there only exists one namespace in Ioke And that is why there is a need to have these methods named differently So for example say that you want to invoke the lt code gt toString lt code gt method on lt code gt java util HashMap lt code gt To do that you do it like this lt code gt java util HashMap class toString lt code gt Note that you can actually use the lt code gt class lt code gt methods on instances of a class too The result will be the same as if the receiver had been that class instead of the instance And that is why there is a need to have these methods named differently So for example say that you want to invoke the code toString code method on code java util HashMap code To do that you do it like this code java util HashMap class toString code Note that you can actually use the code class code methods on instances of a class too The result will be the same as if the receiver had been that class instead of the instance Fields Fields Accessing Java fields can be done by prepending the field name with lt code gt field lt code gt The exact mechanics of this is that a Java field will result in one or two Ioke methods That means that the fields are not represented as cells directly on the object If the field is not final a setter will be also be generated for it The setter follows the same rules as invocations of regular methods with regards to casting and choice of unpacking of arguments Accessing Java fields can be done by prepending the field name with code field code The exact mechanics of this is that a Java field will result in one or two Ioke methods That means that the fields are not represented as cells directly on the object If the field is not final a setter will be also be generated for it The setter follows the same rules as invocations of regular methods with regards to casting and choice of unpacking of arguments There is a slight gotcha with this scheme If you try to set a field that is final you will end up overwriting the accessor for that field so it s important to

    Original URL path: https://ioke.org/wiki/index.php?title=Java_integration_planning&diff=prev&oldid=407 (2016-02-13)
    Open archived version from archive

  • Java integration planning - IokeWiki
    Personal tools 192 168 0 2 Talk for this IP Log in News About Ioke Guide Download Project page CI Reference Resources Wiki Wiki Main Page Recent changes Search Toolbox What links here Related changes Special pages Printable version Permanent

    Original URL path: https://ioke.org/wiki/index.php/Java_integration_planning (2016-02-13)
    Open archived version from archive

  • Revision history of "Future plans" - IokeWiki
    Ioke E is now real not future cur last 14 31 5 April 2009 Olabini Talk contribs 269 bytes Future plans cur last 20 26 26 January 2009 Cv Talk contribs 269 bytes point to TODO list instead of keeping duplicate cur last 02 58 26 January 2009 Cv Talk contribs 385 bytes New page Future plans I have many plans for the future of Ioke The next major versions

    Original URL path: https://ioke.org/wiki/index.php?title=Future_plans&action=history (2016-02-13)
    Open archived version from archive

  • Future plans - IokeWiki
    F Exactly what it will contain we ll have to see but feel free to add your requests and ideas to Todo our TODO list I have many plans for the future of Ioke The next major version of Ioke will be called Ioke F Exactly what it will contain we ll have to see but feel free to add your requests and ideas to Todo our TODO list Current

    Original URL path: https://ioke.org/wiki/index.php?title=Future_plans&diff=prev&oldid=406 (2016-02-13)
    Open archived version from archive

  • Revision history of "Guide:Aspects" - IokeWiki
    17 April 2009 Tumble Talk contribs m 6 026 bytes Aspects cur last 07 57 26 January 2009 Olabini Talk contribs 6 023 bytes cur last 02 45 26 January 2009 Cv Talk contribs 6 019 bytes Aspects cur last 23 18 25 January 2009 Cv Talk contribs 6 023 bytes New page Aspects In many circumstances you might want to do several different things in a specific method That

    Original URL path: https://ioke.org/wiki/index.php?title=Guide:Aspects&action=history (2016-02-13)
    Open archived version from archive

  • Guide:Aspects - IokeWiki
    called call message name quot println lt source gt called call message name println source This code doesn t do anything strange at all This code doesn t do anything strange at all Next up we have after advice The only difference here is that after advice automatically gets a cell that is set to aspectResult that can be used inside the method Next up we have after advice The only difference here is that after advice automatically gets a cell that is set to aspectResult that can be used inside the method lt source lang quot ioke quot gt X after foo lt lt method args source lang ioke X after foo method args quot foo resulted in aspectResult quot println lt source gt foo resulted in aspectResult println source Remember that the result value of before and after advice doesn t count It is thrown away But these methods can still affect things by side effects They can also be used for validation A condition signalled inside of an advice would have the same effect as if done in the method itself namely interrupting the flow of control Remember that the result value of before and after advice doesn t count It is thrown away But these methods can still affect things by side effects They can also be used for validation A condition signalled inside of an advice would have the same effect as if done in the method itself namely interrupting the flow of control The final advice is around advice These are different in two ways First they get access to a cell called aspectCall which can be used to invoke the real cell and the next chain of advice of course The second difference is that the result of the around advice will be the return value from the cell So you can imagine the around advice executing instead of the original code If you forget to invoke it the original cell won t be invoked at all The final advice is around advice These are different in two ways First they get access to a cell called aspectCall which can be used to invoke the real cell and the next chain of advice of course The second difference is that the result of the around advice will be the return value from the cell So you can imagine the around advice executing instead of the original code If you forget to invoke it the original cell won t be invoked at all lt source lang quot ioke quot gt X around non existant lt lt method source lang ioke X around non existant method 42 42 X around foo lt lt method arg1 arg2 X around foo method arg1 arg2 quot before quot println before println res aspectCall arg2 arg1 res aspectCall arg2 arg1 quot got res quot println got res println 42 lt source gt 42 source The first piece of code show that you can actually use an around advice around

    Original URL path: https://ioke.org/wiki/index.php?title=Guide:Aspects&diff=prev&oldid=405 (2016-02-13)
    Open archived version from archive

  • Revision history of "Guide:Assignment" - IokeWiki
    bytes Assignment cur last 08 02 26 January 2009 Olabini Talk contribs 11 152 bytes cur last 08 02 26 January 2009 Olabini Talk contribs 11 151 bytes cur last 23 07 25 January 2009 Cv Talk contribs 11 196 bytes New page Assignment Superficially Ioke s assignment model is quite simple But there exists some subtleties too One of the main reasons for this is that assigning a cell

    Original URL path: https://ioke.org/wiki/index.php?title=Guide:Assignment&action=history (2016-02-13)
    Open archived version from archive



  •