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".
  • Guide:Java integration - IokeWiki
    view source Olabini Talk contribs Newer edit Java integration Java classes can be accessed by their full name separated with colon instead of dots Java classes can be accessed by their full name separated with colon instead of dots Revision as of 14 56 5 April 2009 Retrieved from http ioke org internal wiki index php Guide Java integration Views Page Discussion View source History Personal tools 192 168 0

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


  • Guide:Java integration - IokeWiki
    at most one class and then returns a new class that is magic in that it will proxy back all calls to the Ioke object if it defines a method with the corresponding name This scheme works for most things but there are some things to keep in mind too The most important one is that if you override a method that is overloaded in Java land it is the responsibility of the Ioke method to handle all the overloads Using it is very simple source lang ioke IokeRunnable integrate java lang Runnable IokeRunnable run method running println java lang Thread new IokeRunnable new source Note that you have to use the code new code method to create new instances of this object In this way it behaves exactly like regular objects in Java integration And just in the same way doing mimic will not copy the internal Java object just the outwards Ioke object Integration takes care of handling coercion of arguments and return values into what Java expects Coercing lexical blocks to interfaces Ioke contains a mechanism that will automatically try to coerce anything code like into an interface or abstract class if no other matching overload can

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

  • Guide:Java integration - IokeWiki
    for regular Java methods In general working with Java native arrays work exactly like you would expect The main difference is how you create them For working with native arrays of primitive types you can use the primitive type names which are java byte java short java char java int java long java float and java double When setting or getting values from these arrays they will work exactly like the coercions for regular Java methods Finally Java native arrays implement each and mimic Mixins Enumerable which means that most things you expect to be able to do with them will work correctly Finally Java native arrays implement each and mimic Mixins Enumerable which means that most things you expect to be able to do with them will work correctly Adding jar files to the CLASSPATH Adding jar files to the CLASSPATH If you dynamically want to add new jar files to the CLASSPATH you can do that using use There are two ways of doing it you can either be implicit or explicit depending on if the module name is unique to a jar file or not If you dynamically want to add new jar files to the CLASSPATH

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

  • Guide:Java integration - IokeWiki
    null will always be changed into nil This means that if you wrap a Java object do some modifications to it and then let it go through a Java call what you will get back is probably not the wrapped version of that object Of course later on if you try to call a method on the object you will still use the wrapped data The return value from a Java invocation will never be modified except that null will always be changed into nil and Java booleans will be transformed into Ioke booleans This means that if you wrap a Java object do some modifications to it and then let it go through a Java call what you will get back is probably not the wrapped version of that object Of course later on if you try to call a method on the object you will still use the wrapped data The general rule for overloading is that overloaded methods will be sorted from the most specific to the most general The general rule for overloading is that overloaded methods will be sorted from the most specific to the most general Casts Casts Ioke Java integration supporting casts in the same way as Java does The main difference is that the cast will be evaluated at runtime not compile time The name to cast to will be unevaluated Valid names are either Object String any Java class name where dots are separated with colons and a few special ones to handle primitive values These names are int integer long short char character float double and boolean Casting looks like this Ioke Java integration supporting casts in the same way as Java does The main difference is that the cast will be evaluated at runtime not compile time The name to cast to will be unevaluated Valid names are either Object String any Java class name where dots are separated with colons and a few special ones to handle primitive values These names are byte int integer long short char character float double and boolean Casting looks like this source lang ioke source lang ioke foo LinkedList new foo LinkedList new source source Java native arrays In general working with Java native arrays work exactly like you would expect The main difference is how you create them For working with native arrays of primitive types you can use the primitive type names which are java byte java short java char java int java long java float and java double When setting or getting values from these arrays they will work exactly like the coercions for regular Java methods You can either create a new empty array or you can initialize it based on an existing Ioke list source lang ioke x java short 5 new x java short from 1 2 3 4 5 source The first version creates a JavaArrayProxyCreator with dimension one and length 5 The call to new will generate the actual array from this You can

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

  • Guide:Java integration - IokeWiki
    separated with colon instead of dots source lang ioke h java util HashMap new source You can invoke methods as expected althou Newer edit Revision as of 14 33 5 April 2009 Retrieved from http ioke org internal wiki index php Guide Java integration Views Page Discussion View source History Personal tools 192 168 0 2 Talk for this IP Log in News About Ioke Guide Download Project page CI

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

  • Future plans - IokeWiki
    Ioke P respectively Exactly what they 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 versions of Ioke will be called Ioke P and Ioke E respectively Exactly what they will contain we ll have to see but feel free to add your requests and ideas

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

  • Guide:What is missing - IokeWiki
    Ioke S is not finished Several things are missing before it s complete The core mechanics of the language I m feeling fairly confident in but the core libraries are generally only partially implemented They are much more complete than for the Ioke 0 release but there still exist large holes in it Ioke E is not a finished Ioke version I seriously doubt Ioke will ever be complete The core mechanics of the language I m feeling fairly confident in but the core libraries are generally only partially implemented They are much more complete than for the Ioke S release but there still exist large holes in it Another major part maybe even THE major part is Java integration At the moment it is not possible to call or interact with Java libraries That need to happen and it will happen after the S release Concurrency will also be part of the work after the S release Concurrency support is missing and so is any kind of advanced IO Package management and other libraries like that is now starting to become necessary Finally alternative implementations for other platforms is also in the pipeline to happen sooner or later There

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

  • Guide:Objects - IokeWiki
    special in that this is the place where all top level kinds are defined If you want to create a top level kind you should put it in Ground If you take a look in Ground you will see that it contains cells for Text Dict List Base Origin itself and many other Ioke doesn t have any global state at all but Ground is as close as it gets Ground should in most cases not be mimicked directly As mentioned above Ground is the default ground context for evaluation Ground IokeGround and JavaGround and IokeGround mimics Base and DefaultBehavior IokeGround is special in that this is the place where all top level kinds are defined If you want to create a top level kind you should put it in IokeGround If you take a look in IokeGround you will see that it contains cells for Text Dict List Base Origin itself and many other Ioke doesn t have any global state at all but IokeGround is as close as it gets IokeGround and Ground should in most cases not be mimicked directly JavaGround is the place where all Java integration support is integrated into Ioke Origin Origin Revision as

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



  •