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
    quot signal quot quot warn quot or quot error quot Both quot warn quot and quot error quot uses quot signal quot under the covers but do some other things as well A condition will always mimic Condition Each of these three methods can be called in three different ways First you can call them with a text argument In that case the signalled condition will be the default for that type The default for quot signal quot is Condition Default The default for quot warn quot is Condition Warning Default and the default for quot error quot is Condition Error Default A new mimic of the default condition will be created and a cell called text will be set to the text argument The second variation is to give an instance of an existing condition to one of the methods In that case that condition will be signalled unmodified Finally the third version gives a condition mimic and one or more keyword arguments with data to set on that condition In that case a mimic of the condition will be created and then cells with data set based on the arguments The way the condition system works is this When something happens a program can elect to signal a condition This can be done using quot signal quot quot warn quot or quot error quot Both quot warn quot and quot error quot use quot signal quot under the covers but do some other things as well A condition will always mimic Condition Each of these three methods can be called in three different ways First you can call them with a text argument In that case the signalled condition will be the default for that type The default for quot signal quot is Condition Default The default for

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


  • Guide:Aspects - IokeWiki
    only difference here is that after advice automatically gets a cell that is set to adviceResult that can 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 adviceResult that can be used inside the method source lang ioke X after foo method args source lang ioke X after foo method args Revision as

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

  • Pitfalls - IokeWiki
    away The return value of around advice is used but the return values of before and after advice is thrown away From the guide The return value of before and after advice doesn t matter but the return value of around advice will be interpreted as the new return value of the message send From the guide The return value of before and after advice doesn t matter but the

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

  • Guide:Code - IokeWiki
    how the argument handling to methods are implemented for example Since the call to quot method quot can be seen as a regular call to a macro the argument descriptions are actually just unevaluated message chains that are picked apart to tease out the argument names The same technique is applicable in any macro usage In many cases a macro will take code that is not wrapped up inside of a method macro or block These pieces of code are called message chains since their representation will be a raw Message mimic The chains are quite flexible since they can be taken apart modified and put together again They can also be unevaluated and used as data definitions of some kind That s how the argument handling to methods are implemented for example Since the call to quot method quot can be seen as a regular call to a macro the argument descriptions are actually just unevaluated message chains that are picked apart to tease out the argument names The same technique is applicable in any macro usage The term message chain fragment is also used to specifically mean a message chain that is meant to be put together with something and evaluated Picture a daisy chain that gets added at the end of another chain and then executed That s what happens if you execute something like code 1 2 3 map 2 code In this case the call to code code with the argument 2 will be a message chain fragment that will be put together with a new receiver before execution The term message chain fragment is also used to specifically mean a message chain that is meant to be put together with something and evaluated Picture a daisy chain that gets added at the end of

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

  • Guide:Code - IokeWiki
    the argument handling to methods are implemented for example Since the call to quot method quot can be seen as a regular call to a macro the argument descriptions are actually just unevaluated message chains that are picked apart to tease out the argument names The same technique is applicable in any macro usage In many cases a macro will take code that is not wrapped up inside of a method macro or block These pieces of code are called message chains since their representation will be to a raw Message mimic The chains are quite flexible since they can be taken apart modified and put together again They can also be unevaluated and used as data definitions of some kind That s how the argument handling to methods are implemented for example Since the call to quot method quot can be seen as a regular call to a macro the argument descriptions are actually just unevaluated message chains that are picked apart to tease out the argument names The same technique is applicable in any macro usage The term message chain fragment is also used to specifically mean a message chain that is meant to be put together with something and evaluated Picture a daisy chain that gets added at the end of another chain and then executed That s what happens if you execute something like code 1 2 3 map 2 code In this case the call to code code with the argument 2 will be a message chain fragment that will be put together with a new receiver before execution The term message chain fragment is also used to specifically mean a message chain that is meant to be put together with something and evaluated Picture a daisy chain that gets added at the end of

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

  • Guide:Code - IokeWiki
    arguments that should be evaluated All of that code turns out to be highly repetetive so Ioke contains a collection of syntax macros that make it easier to write these things These are collectively called destructuring syntax A common problem with macros is that you want to take several different combinations of arguments and do different things depending on how many you get Say you might want to take one code argument but also two optional arguments that should be evaluated All of that code turns out to be highly repetetive so Ioke contains a collection of syntax macros that make it easier to write these things These are collectively called destructuring syntax Let us say we have a macro that either code evaluatedArgument code or evaluatedArgument code evaluatedArgument The stuff that should happen is totally different for each of these cases With a regular macro the code would look something like this Let us say we have a macro that can be called with any of three types of argument list code evaluatedArgument code or evaluatedArgument code evaluatedArgument The stuff that should happen is totally different for each of these cases With a regular macro the code would look

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

  • Pitfalls - IokeWiki
    Newer edit to create a list in these contexts to create a list in these contexts fnx is activatable but lecrox is unactivatable Add an x to fn and you get the activatable version of fn fn is unactivatable with some exceptions Add an x to lecro and you get the un activatable version of lecto lecro is activatable Revision as of 08 51 17 April 2009 Retrieved from http

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

  • Pitfalls - IokeWiki
    Tumble Talk contribs m The operator is overloaded in List Dict and Enumerable Newer edit source lang ioke source lang ioke list list source source source lang ioke source lang ioke source source to create a list in these contexts to create a list in these contexts Revision as of 02 21 15 April 2009 Retrieved from http ioke org internal wiki index php Pitfalls Views Page Discussion View source

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



  •