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 "Guide:Control flow" - IokeWiki
    Talk contribs m 16 078 bytes Iteration cur last 08 07 26 January 2009 Olabini Talk contribs 16 077 bytes cur last 23 14 25 January 2009 Cv Talk contribs 16 100 bytes cur last 23 13 25 January 2009 Cv Talk contribs 89 493 bytes New page Control flow Ioke has some standard control flow operators like most other languages In Ioke all of these are regular method calls

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

  • Guide:Control flow - IokeWiki
    lt gt and gt implemented in terms of the spaceship operator There are two other common operators in Ioke The first which can also be called the match operator It s only implemented for Regexp right now The operator also exists but implements matching slightly differently for all different types of objects It is the basis for the case expression The contract of comparison operators is that they should return a true value not necessarily the true if the comparison is true and otherwise return either false or nil The contract for should be matching or not matching It is among other things used in Ranges to see if something is included in that range or not The contract for should be matching or not matching It is among other things used in Ranges to see if something is included in that range or not Iteration Iteration Ioke supports most of the expected control flow operations for iteration The one thing that is missing is the for loop Since the for loop encourages low level stepping and can be replaced by other kinds of operations I don t see any reason in having it in Ioke In fact the for statement in Ruby is generally considered bad form too And if someone really wants a for loop it s really easy to implement For now I m reserving the name if I would like to add comprehensions at some point Ioke supports most of the expected control flow operations for iteration The one thing that is missing is the for loop Since the for loop encourages low level stepping and can be replaced by other kinds of operations I don t see any reason in having it in Ioke In fact the for statement in Ruby is generally considered bad

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

  • Guide:Assignment - IokeWiki
    simple assignment All of these assignment processes together make it really easy to take control over assignment while still making it very obvious and natural in most cases All of these assignment processes together make it really easy to take control over assignment while still making it very obvious and natural in most cases Destructuring assignment The easiest example of destructuring assignment looks like this source lang ioke x y 42 44 source Note that the parenthesis are necessary both on the left hand and right hand side This will assign x to 42 and y to 44 in the current context following the assignment rules given above This assignment will happen in parallel which means you can do the obvious swapping of values in one operation source lang ioke x y y x source This also works for more than two simultaneous assignments The right hand side of an expression like this is expected to be a regular value that can be converted into a tuple This include all Enumerable objects since asTuple is defined there That means you can also do something like this source lang ioke x y 42 44 source If the destructurings doesn t match up this is an error Something like source lang ioke x y 42 44 46 source will signal a condition code Condition Error DestructuringMismatch code This might not always be convenient Say you don t care about the rest of the arguments and want to extract the two first elements no matter what you can do that by ignoring the rest this is done with the underscore source lang ioke x y 1 100 source You can also use the underscore to ignore specific locations in other places These will only ignore one element though source lang ioke x y

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

  • Guide:Objects - IokeWiki
    Mixins are generally not grounded in Base and doesn t contain most of the things you would expect from an object DefaultBehavior contain almost all the general methods you use when programming Ioke It contains the internal methods to create values from literals and most other functionality specified in this document In short DefaultBehavior is the work horse and you should have a pretty good reason to not have it in the mimic chain of an object Since Ground mimics DefaultBehavior any object you create from Origin will have DefaultBehavior in its mimic chain The actual implementation of DefaultBehavior is divided into several smaller mixins that are all mixed in to DefaultBehavior These give more focused pieces of behavior They are in alphabetical order http ioke org dok kinds DefaultBehavior Aspects html code DefaultBehavior Aspects code http ioke org dok kinds DefaultBehavior Assignment html code DefaultBehavior Assignment code http ioke org dok kinds DefaultBehavior BaseBehavior html code DefaultBehavior BaseBehavior code http ioke org dok kinds DefaultBehavior Boolean html code DefaultBehavior Boolean code http ioke org dok kinds DefaultBehavior Case html code DefaultBehavior Case code http ioke org dok kinds DefaultBehavior Conditions html code DefaultBehavior Conditions code http ioke org dok kinds DefaultBehavior Definitions html code DefaultBehavior Definitions code http ioke org dok kinds DefaultBehavior FlowControl html code DefaultBehavior FlowControl code http ioke org dok kinds DefaultBehavior Internal html code DefaultBehavior Internal code http ioke org dok kinds DefaultBehavior Literals html code DefaultBehavior Literals code http ioke org dok kinds DefaultBehavior Reflection html code DefaultBehavior Reflection code The recommended way to add new global behavior to Ioke is to either add a cell to one of these or create a new mixin and mix it in to the appropriate place If you re adding new flow control features mixing these in code DefaultBehavior FlowControl code might be appropriate for example nil true false nil true false The three values nil true and false are the only values that are considered kinds even though they start with lower case letters They are not like the other kinds in the other important way either these values can not be mimicked and you will get a condition if you try it The reason is that Ioke s basic boolean system revolves around these values It is not entirely certrain that these values will forever be the only boolean values but for now they are nil should be used to represent the absence of a value including the absence of a reasonable return value false is the quintessential false value and true is the quintessential true value The value true isn t strictly necessary since any value except for nil and false are true This notion of truthness mimics Ruby The cells nil true and false are defined in Ground and they can actually be overridden or changed but I don t recommend it I can guarantee lots of chaos and non working programs from doing it More info on how these values interact can

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

  • Revision history of "Guide:Syntax" - IokeWiki
    12 27 March 2009 Olabini Talk contribs 19 008 bytes Text cur last 15 09 22 March 2009 Delitescere Talk contribs 19 003 bytes Text cur last 15 07 22 March 2009 Delitescere Talk contribs m 18 956 bytes Syntax cur last 09 33 10 March 2009 Olabini Talk contribs 18 956 bytes Regular expressions cur last 10 59 8 February 2009 Mdobmeier Talk contribs 18 965 bytes Execution model cur last 08 24 26 January 2009 Olabini Talk contribs 22 023 bytes cur last 03 08 26 January 2009 Cv Talk contribs 22 017 bytes Syntax cur last 02 43 26 January 2009 Cv Talk contribs 22 049 bytes Execution model cur last 02 41 26 January 2009 Cv Talk contribs 21 987 bytes Execution model cur last 00 50 26 January 2009 Cv Talk contribs 21 946 bytes Syntax cur last 00 46 26 January 2009 Cv Talk contribs 21 965 bytes Syntax cur last 00 19 26 January 2009 Cv Talk contribs 21 987 bytes New page Syntax Ioke has no keywords or statements Everything is an expression composed of a chain of messages A piece of code is represented as a chain of messages that links

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

  • Guide:Syntax - IokeWiki
    gt lt gt lt gt gt lt gt gt gt gt amp amp amp amp amp amp amp amp gt lt gt gt gt gt gt amp gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt amp amp gt amp amp gt gt amp gt amp gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt amp gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt lt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt amp amp gt amp amp gt gt gt gt gt gt gt gt gt gt gt gt gt gt amp amp amp lt lt gt gt and and nand nand amp nor amp amp or or xor xor nor lt lt gt gt lt lt import return return Current revision Retrieved from http ioke org internal wiki index php Guide Syntax Views Page Discussion View source History Personal tools 192 168 0 2 Talk for this

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

  • Guide:Syntax - IokeWiki
    also a potential place for Number Complex at the same layer as Number Real although complex numbers are not currently implemented There are also plans for implementing a unit system further down the line Ioke supports arbitrarily sized numbers It also contains a numerical tower that can be more closely explored in the reference documentation The numerical tower is based in Number Number Real mimics Number Number Rational mimics Number Real and so does Number Decimal Finally Number Integer and Number Ratio both mimics Number Rational The interesting parts of this tower is Number Integer which corresponds to integers Number Ratio which is any ratio between two integers and Number Decimal which corresponds to decimal numbers These are arbitrarily sized and exact There are no floats or doubles in Ioke There is also a potential place for Number Complex at the same layer as Number Real although complex numbers are not currently implemented There are also plans for implementing a unit system further down the line Number Infinity represents the singleton infinity object Literal integers can be written using either decimal or hexadecimal notation Hexadecimal notation begins with 0x or 0X and are then followed by one or more hexadecimal

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

  • Guide:Introduction - IokeWiki
    information about it in the chapter on Future plans future plans This programming guide together with the reference for your current version should be the complete document needed to understand Ioke E how to program in it how to understand the names and concepts used and also give an initial inkling on what I think is good taste This programming guide together with the reference for your current version should be the complete document needed to understand Ioke P how to program in it how to understand the names and concepts used and also give an initial inkling on what I think is good taste Note that I will use many names that aren t necessarily the same as the ones traditional programming languages use These names will be made clear sooner or later in this document but it might help some to jump forward to Objects Objects skim that bit and then start over once words like Origin cell and mimic make sense Note that I will use many names that aren t necessarily the same as the ones traditional programming languages use These names will be made clear sooner or later in this document but it might help some to jump forward to Objects Objects skim that bit and then start over once words like Origin cell and mimic make sense Getting started Getting started Ioke is very easy to get started with The first step is to download a package Which one you choose depends on what platform you re on and whether you want to build Ioke yourself or just start using it This guide will only cover using a prebuilt version Go to the http ioke org download html download page and grab one of the distributions At the time of writing the full version

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



  •