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:Core kinds - IokeWiki
    22 December 2009 view source Olabini Talk contribs Sequences Newer edit Sequence defines these methods and cells Sequence defines these methods and cells nowiki nowiki See code interpose code See code interpose code Revision as of 20 23 22 December 2009 Retrieved from http ioke org internal wiki index php Guide Core kinds Views Page Discussion View source History Personal tools 192 168 0 2 Talk for this IP Log

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


  • Guide:Core kinds - IokeWiki
    code next code will tell you whether there is anything more in the sequence to fetch Sequence is Enumerable once you call an Enumerable method on a Sequence it will be fully realized until no more is needed Sequence defines these methods and cells See code interpose code See code interleave code Combines two sequences into one It will first execute all elements of the first sequence then all the elements of the second source lang ioke 1 10 seq Sequence infinity mapped 2 take 12 should 2 4 6 8 10 12 14 16 18 20 0 2 source collected An alias of code mapped code dropped The sequence version of code drop code Creates a new sequence that will drop the requested amount of elements and then continue returning the elements from the sequence source lang ioke Sequence infinity dropped 5 take 5 should 6 7 8 9 10 source droppedWhile The sequence version of code dropWhile code Creates a new sequence that will drop while the given argument code returns true source lang ioke Sequence infinity droppedWhile 10 take 5 should 10 11 12 13 14 source filtered The sequence version of code filter code Will return a new sequence that filters all elements according to the argument code grepped The sequence version of code grep code Will return a new sequence that only yield the elements that match the argument indexed Takes two optional keyword arguments from and step These default to 0 and 1 respectively Will yield a list for each element where the first is the index and the second is the element infinity Returns a new sequence that goes from zero and continues forever It also takes from and step arguments that default to 0 and 1 interleave Returns a new sequence where

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

  • Guide:Core kinds - IokeWiki
    1 3 should 1 2 3 source You can also test membership nonmembership subset and superset relations using the mathematical operators source lang ioke membership 42 1 2 42 3 nonmembership 42 1 2 3 subset 2 1 2 3 proper subset bar foo foo bar quux superset 1 2 3 2 proper superset bar foo quux foo bar source Ranges and Pairs Both ranges and pairs tie two values together They also have literal syntax to create them since they are very useful in many circumstances Both ranges and pairs tie two values together They also have literal syntax to create them since they are very useful in many circumstances foo bar second bar foo bar second bar foo bar value bar source foo bar value bar source Tuples A Pair is a special case of wanting to tie two values together The general case of bundling several values together can be achieved by using Tuples If you give anything else than one argument to the empty method you will get back a Tuple You can also create a new tuple explicitly using the code tuple code method To extract elements out of the tuple the main way is using destructuring assignment It is also possible to use a named extractor to get a given index Tuples are by design not Enumerable This is a feature not a misfeature If you use tuples as something that should be enumerated over you re using the wrong data structure Also remember that Enumerable defines asTuple so anything enumerable can be turned into a tuple if needed source lang ioke t tuple 42 55 18 x y z t t third should 18 t 3 should 18 source As you can see english style names are defined for accessing elements These will only be available up to nine elements The underscore syntax for indexing will always be possible though Structs It is pretty common to want to describe a type of object with set elements that already provide support for structural equality and hash encoding Ioke structs provide this behavior You create a new one by calling the Struct method source lang ioke Person Struct first name sur name age source You can provide default values using keyword arguments instead source lang ioke Person Struct first name sur name age 1 source Creating a new version of a Struct can be done using the object as a function source lang ioke o Person Ola Bini source It is also possible to provide these values using keywords or even a mix source lang ioke s Person first name Sam sur name Aaron b Person sur name Guthrie Brian source All of these objects will implement nowiki nowiki hash asText notice and inspect Accessors and mutators also work You can get access to all the Struct attributes by calling code attributes code If you just want the names you can use code attributeNames code A Struct instance is also Sequenced over a combination of

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

  • Revision history of "Guide:Introspection and Reflection" - IokeWiki
    contribs 8 660 bytes cur last 23 38 25 January 2009 Cv Talk contribs 8 638 bytes Introspection and reflection cur last 23 27 25 January 2009 Cv Talk contribs 8 794 bytes Introspection and reflection cur last 23 17 25 January 2009 Cv Talk contribs 8 918 bytes New page Introspection and reflection Ioke supports quite fancy introspection and reflection capabilities In Ioke reflection includes the ability to change

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

  • Guide:Introspection and Reflection - IokeWiki
    The equivalent of code other documentation code The equivalent of code other documentation code Reflector other documentation other value Reflector other nowiki nowiki documentation other value The equivalent of code other documentation value code The equivalent of code other documentation value code Reflector other freeze other Reflector other nowiki nowiki freeze other The equivalent of code other freeze code The equivalent of code other freeze code Reflector other frozen other Reflector other nowiki nowiki frozen other The equivalent of code other frozen code The equivalent of code other frozen code Reflector other is other obj Reflector other nowiki nowiki is other obj The equivalent of code other is obj code The equivalent of code other is obj code Reflector other kind other kindName Reflector other nowiki nowiki kind other kindName The equivalent of code other kind kindName code The equivalent of code other kind kindName code Reflector other mimic other Reflector other nowiki nowiki mimic other The equivalent of code other mimic code The equivalent of code other mimic code Reflector other mimic other newMimic Reflector other nowiki nowiki mimic other newMimic The equivalent of code other mimic newMimic code The equivalent of code other mimic newMimic code Reflector other mimics other Reflector other nowiki nowiki mimics other The equivalent of code other mimics code The equivalent of code other mimics code Reflector other mimics other potMimic Reflector other nowiki nowiki mimics other potMimic The equivalent of code other mimics potMimic code The equivalent of code other mimics potMimic code Reflector other prependMimic other newMimic Reflector other nowiki nowiki prependMimic other newMimic The equivalent of code other prependMimic newMimic code The equivalent of code other prependMimic newMimic code Reflector other removeAllMimics other Reflector other nowiki nowiki removeAllMimics other The equivalent of code other removeAllMimics code The equivalent of code other

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

  • Guide:Introspection and Reflection - IokeWiki
    contribs Newer edit The equivalent of code other undefineCell name code The equivalent of code other undefineCell name code Reflector other uniqueHexId other Reflector other uniqueHexId other The equivalent of code other uniqueHexId code The equivalent of code other uniqueHexId code Revision as of 19 10 22 December 2009 Retrieved from http ioke org internal wiki index php Guide Introspection and Reflection Views Page Discussion View source History Personal tools

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

  • Guide:Introspection and Reflection - IokeWiki
    method activated Reflector In some cases you might work with an object that doesn t support the usual introspective methods For writing certain types of code it is just necessary to be able to break apart an object from the outside To be able to achieve this Ioke now has something called a Reflector which give access to several reflective operations from the outside The general pattern is that the name gets other prepended to it and takes the object to operate on as the first argument The available methods are Reflector other become other into The equivalent of code other become into code Reflector other cell other name The equivalent of code other cell name code Reflector other cell other name value The equivalent of code other cell name value code Reflector other cell other name The equivalent of code other cell name code Reflector other cellNames other The equivalent of code other cellNames code Reflector other cellOwner other name The equivalent of code other cellOwner name code Reflector other cellOwner other name The equivalent of code other cellOwner name code Reflector other cells other The equivalent of code other cells code Reflector other documentation other The equivalent of code other documentation code Reflector other documentation other value The equivalent of code other documentation value code Reflector other freeze other The equivalent of code other freeze code Reflector other frozen other The equivalent of code other frozen code Reflector other is other obj The equivalent of code other is obj code Reflector other kind other kindName The equivalent of code other kind kindName code Reflector other mimic other The equivalent of code other mimic code Reflector other mimic other newMimic The equivalent of code other mimic newMimic code Reflector other mimics other The equivalent of code other mimics code

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

  • Guide:Code - IokeWiki
    as the ground The current types of code can be divided into three different categories These are methods macros and blocks Native methods are all of the kind JavaMethod but can have any kind of semantics including semantics that look like macros Most native methods do have the same semantics as regular methods however The current types of code can be divided into three different categories These are methods macros and blocks Native methods are all of the kind NativeMethod but can have any kind of semantics including semantics that look like macros Most native methods do have the same semantics as regular methods however Methods Methods A lexical block is a regular kind of object that can be assigned to any cell just like other objects Lexical blocks mimic LexicalBlock and blocks don t have names In contrast to methods and macros no extra cells will be added to the activation context for a lexical block A lexical block is a regular kind of object that can be assigned to any cell just like other objects Lexical blocks mimic LexicalBlock and blocks don t have names In contrast to methods and macros no extra cells will be added to the activation context for a lexical block You can also do several kinds of functional composition of blocks Some of these combinations only make sense for predicates while others are more generally applicable They all expect to work with functions that are OK with only taking one argument though In the following examples f and g are general lexical blocks while p and q are predicates code f g code Will return a new block that is the equivalent of code g f arg code code f g code Will return a new block that is the equivalent of code

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



  •