Guide:Introduction - Revision history

Admin: Reverted edits by Icotime (Talk) to last version by Olabini

2010-11-24T14:38:37Z

Reverted edits by Icotime (Talk) to last version by Olabini

Show changes

spambot_Icotime at 00:58, 24 November 2010

2010-11-24T00:58:04Z

Show changes

Olabini: /* Introduction */

2009-12-21T19:49:18Z

‎Introduction

spambot_Tumble: /* Vision */ minor grammar

2009-04-08T05:52:24Z

‎Vision: minor grammar

Olabini: /* Introduction */

2009-04-05T14:20:11Z

‎Introduction

Olabini: /* Introduction */

2009-01-27T08:10:27Z

‎Introduction

Cv: /* Building Ioke */

2009-01-27T07:46:09Z

‎Building Ioke

Cv: /* Getting started */

2009-01-27T07:44:05Z

‎Getting started

Cv: /* Introduction */

2009-01-26T02:54:13Z

‎Introduction

Cv: /* Introduction */

2009-01-26T02:52:12Z

‎Introduction

@@ Line 9: / Line 9: @@
 You're probably reading this guide at [http://ioke.org/guide.html ioke.org]. That is the official home of the project, although some of the project functionality is hosted at [http://ioke.kenai.com Kenai], where such things as mailing lists and a bug tracker is available. The canonical source repository for Ioke is on [http://github.org/olabini/ioke/tree/master GitHub].
-The current version of Ioke is called [[Ioke E]]. The naming of Ioke will change regularly with major revisions. There are two different versions in play here. [[Ioke E]] is the name and version of the language and core libraries. The initial implementation for [[Ioke E]] is called <tt>ikj 0.3.0</tt>, and the version numbers are not interdependent. The next major version of Ioke will be called [[Ioke P]], and you can find information about it in the chapter on [[#Future_plans|future plans]].
+The current version of Ioke is called [[Ioke P]]. The naming of Ioke will change regularly with major revisions. There are two different versions in play here. [[Ioke P]] is the name and version of the language and core libraries. The initial implementation for [[Ioke P]] is called <tt>ikj 0.4.0</tt>, and the version numbers are not interdependent. The next major version of Ioke will be called [[Ioke F]], and you can find 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.
@@ Line 33: / Line 33: @@
 == 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 of Ioke is Ioke E ikj 0.3.0. Choose the latest download in the 0.3-series for this document to apply.
+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 of Ioke is Ioke P ikj 0.4.0. Choose the latest download in the 0.4-series for this document to apply.
 Once you have downloaded the distribution, you need to unpack it somewhere, and finally add the <tt>bin</tt> directory to your <tt>PATH</tt> environment variable. There is also a <tt>jar</tt> download that can be run directly. If you choose this option you don't get the benefits of having a home for Ioke, which in some cases might be inconvenient. Ioke can be run directly from the jar file, though.

@@ Line 23: / Line 23: @@
 There are many open problems in programming language design. Concurrency is one of them, performance another. These are two areas Ioke does not address. Instead, Ioke is a remodeling of the core concepts and ideas embodied in other programming languages.
-Are still Lisp and Smalltalk the most powerful languages around, or are there ways of providing more expressiveness without sacrificing understandability? Is there a way to combine all the lessons learned from languages like Ruby and Python, and patch them back into a Lisp and Smalltalk core? Is it possible to do this while taking some of the benefits of Io? Can a language be both small, regular, homoiconic, reflective and easy to understand? I hope that Ioke is just that.
+Are Lisp and Smalltalk still the most powerful languages around, or are there ways of providing more expressiveness without sacrificing understandability? Is there a way to combine all the lessons learned from languages like Ruby and Python, and patch them back into a Lisp and Smalltalk core? Is it possible to do this while taking some of the benefits of Io? Can a language be both small, regular, homoiconic, reflective and easy to understand? I hope that Ioke is just that.
 Simplicity doesn't mean lack of power. Small, simple, orthogonal functionality can be more powerful than larger, complicated abstractions that don't fit together.

@@ Line 9: / Line 9: @@
 You're probably reading this guide at [http://ioke.org/guide.html ioke.org]. That is the official home of the project, although some of the project functionality is hosted at [http://ioke.kenai.com Kenai], where such things as mailing lists and a bug tracker is available. The canonical source repository for Ioke is on [http://github.org/olabini/ioke/tree/master GitHub].
-The current version of Ioke is called [[Ioke S]]. The naming of Ioke will change regularly with major revisions. There are two different versions in play here. Ioke S is the name and version of the language and core libraries. The initial implementation for Ioke S is called <tt>ikj 0.2.0</tt>, and the version numbers are not interdependent. The next major version of Ioke will be called [[Ioke E]], and you can find information about it in the chapter on [[#Future_plans|future plans]].
+The current version of Ioke is called [[Ioke E]]. The naming of Ioke will change regularly with major revisions. There are two different versions in play here. [[Ioke E]] is the name and version of the language and core libraries. The initial implementation for [[Ioke E]] is called <tt>ikj 0.3.0</tt>, and the version numbers are not interdependent. The next major version of Ioke will be called [[Ioke P]], and you can find 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 S, 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 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.
 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.
@@ Line 33: / Line 33: @@
 == 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 of Ioke is Ioke S ikj 0.2.0. Choose the latest download in the 0.2-series for this document to apply.
+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 of Ioke is Ioke E ikj 0.3.0. Choose the latest download in the 0.3-series for this document to apply.
 Once you have downloaded the distribution, you need to unpack it somewhere, and finally add the <tt>bin</tt> directory to your <tt>PATH</tt> environment variable. There is also a <tt>jar</tt> download that can be run directly. If you choose this option you don't get the benefits of having a home for Ioke, which in some cases might be inconvenient. Ioke can be run directly from the jar file, though.

@@ Line 39: / Line 39: @@
 === Building Ioke ===
-If you'd like to build Ioke from source, make sure you have a recent version of the [http://java.sun.com/javase/downloads/index.jsp Java Development Kit] installed (1.5.0 or higher, preferrably 1.6.0) and [http://ant.apache.org Apache Ant]. You must have the <tt>ant</tt> script reachable from your <tt>PATH</tt> variable. Then, simply check out the source code from the [http://github.org/olabini/ioke/tree/master main repository], and built it using <tt>ant</tt>. That should run all the compilation steps and tests, and allow the <tt>bin/ioke</tt> script to run. Just proceed as if you had unpacked the distribution, adding the <tt>bin</tt> directory to the <tt>PATH</tt>.
+If you'd like to build Ioke from source, make sure you have a recent version of the [http://java.sun.com/javase/downloads/index.jsp Java Development Kit] installed (1.5.0 or higher, preferrably 1.6.0) and [http://ant.apache.org Apache Ant]. You must have the <tt>ant</tt> script reachable from your <tt>PATH</tt> variable. Then, simply check out the source code from the [http://github.org/olabini/ioke/tree/master main repository], and build it using <tt>ant</tt>. That should run all the compilation steps and tests, and allow the <tt>bin/ioke</tt> script to run. Just proceed as if you had unpacked the distribution, adding the <tt>bin</tt> directory to the <tt>PATH</tt>.
 === Running scripts ===

@@ Line 39: / Line 39: @@
 === Building Ioke ===
-If you'd like to build Ioke from source, make sure you have a recent version of the [http://java.sun.com/javase/downloads/index.jsp Java Development Kit] installed (1.5.0 or higher, preferrably 1.6.0) and [http://ant.apache.org Apache Ant]. You must have the <tt>ant</tt> script reachable from your <tt>PATH</tt> variable. Then, simply check out the source code from the [[main repository]], and built it using <tt>ant</tt>.
+If you'd like to build Ioke from source, make sure you have a recent version of the [http://java.sun.com/javase/downloads/index.jsp Java Development Kit] installed (1.5.0 or higher, preferrably 1.6.0) and [http://ant.apache.org Apache Ant]. You must have the <tt>ant</tt> script reachable from your <tt>PATH</tt> variable. Then, simply check out the source code from the [http://github.org/olabini/ioke/tree/master main repository], and built it using <tt>ant</tt>. That should run all the compilation steps and tests, and allow the <tt>bin/ioke</tt> script to run. Just proceed as if you had unpacked the distribution, adding the <tt>bin</tt> directory to the <tt>PATH</tt>.
 === Running scripts ===

← Older revision		Revision as of 07:44, 27 January 2009
Line 36:		Line 36:

	Once you have downloaded the distribution, you need to unpack it somewhere, and finally add the <tt>bin</tt> directory to your <tt>PATH</tt> environment variable. There is also a <tt>jar</tt> download that can be run directly. If you choose this option you don't get the benefits of having a home for Ioke, which in some cases might be inconvenient. Ioke can be run directly from the jar file, though.		Once you have downloaded the distribution, you need to unpack it somewhere, and finally add the <tt>bin</tt> directory to your <tt>PATH</tt> environment variable. There is also a <tt>jar</tt> download that can be run directly. If you choose this option you don't get the benefits of having a home for Ioke, which in some cases might be inconvenient. Ioke can be run directly from the jar file, though.
		+
		+	=== Building Ioke ===
		+
		+	If you'd like to build Ioke from source, make sure you have a recent version of the [http://java.sun.com/javase/downloads/index.jsp Java Development Kit] installed (1.5.0 or higher, preferrably 1.6.0) and [http://ant.apache.org Apache Ant]. You must have the <tt>ant</tt> script reachable from your <tt>PATH</tt> variable. Then, simply check out the source code from the [[main repository]], and built it using <tt>ant</tt>.

	=== Running scripts ===		=== Running scripts ===