What is Exodus - Revision history

Admin: /* What is Exodus? */

2016-11-08T08:02:02Z

What is Exodus?

← Older revision		Revision as of 08:02, 8 November 2016
Line 3:		Line 3:
	Exodus is a way to do traditional pick-basic programming in C++.		Exodus is a way to do traditional pick-basic programming in C++.

	It was conceived and created ~~by Steve Bush of NEOSYS Software~~ as a way to move classic pick/multivalue basic into a classic industry standard environment with the minimum of upheaval.		It was conceived and created as a way to move classic pick/multivalue basic into a classic industry standard environment with the minimum of upheaval.

	Many people would like to migrate their classic pick/mv based applications into industry standard environments however they have so much code that relies on the nuances of pick/mv, or their programmers are so used to pick-basic, that it is virtually impossible to move.		Many people would like to migrate their classic pick/mv based applications into industry standard environments however they have so much code that relies on the nuances of pick/mv, or their programmers are so used to pick-basic, that it is virtually impossible to move.

Steve: Reverted edits by Anecada (Talk) to last revision by Steve

2010-11-24T14:00:50Z

Reverted edits by Anecada (Talk) to last revision by Steve

← Older revision		Revision as of 14:00, 24 November 2010
Line 1:		Line 1:
	~~----~~
	<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
	~~----~~
	~~=[http://ynejynezex.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=~~
	~~----~~
	~~=[http://ynejynezex.co.cc CLICK HERE]=~~
	~~----~~
	~~</div>~~
	~~=[http://ogetehuvo.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=~~
	== What is Exodus? ==		== What is Exodus? ==

Line 50:		Line 41:
	== Twin syntaxes ==		== Twin syntaxes ==

	=== Classic Pick ~~&quot;~~Global function~~&quot;~~ style syntax ===		=== Classic Pick "Global function" style syntax ===

	print(oconv(extract(xyz,1,2,3),~~&quot;~~MD20~~&quot;~~)));		print(oconv(extract(xyz,1,2,3),"MD20")));

	This is standard Exodus C++ syntax. Only the representation of print as function ~~&quot;~~print()~~&quot;~~ instead of a command ~~&quot;~~print x~~&quot;~~, - and the trailing ; gives it away as C++.		This is standard Exodus C++ syntax. Only the representation of print as function "print()" instead of a command "print x", - and the trailing ; gives it away as C++.

	Pick programmers are used to this syntax and many will want to stay with this style for whatever reason.		Pick programmers are used to this syntax and many will want to stay with this style for whatever reason.

	It is a pity that C++ syntax doesnt allow the easy-to-write and easy-to-read pick-like array extract/replace like xxx~~&lt;~~1,2,3~~&gt;~~ or x~~&lt;~~3~~&gt;~~=~~&quot;~~x~~&quot;~~. A great shame but not a killer.		It is a pity that C++ syntax doesnt allow the easy-to-write and easy-to-read pick-like array extract/replace like xxx<1,2,3> or x<3>="x". A great shame but not a killer.

	=== Classic OO ~~&quot;~~Method Chaining~~&quot;~~ syntax ===		=== Classic OO "Method Chaining" syntax ===

	xyz(1,2,3).oconv(~~&quot;~~MD20~~&quot;~~).print();		xyz(1,2,3).oconv("MD20").print();

	or if you prefer ...		or if you prefer ...

	xyz.extract(1,2,3).oconv(~~&quot;~~MD20~~&quot;~~).print();		xyz.extract(1,2,3).oconv("MD20").print();

	This is standard Exodus C++ code.		This is standard Exodus C++ code.

	Variable xyz is one of Exodus' ~~&quot;~~var~~&quot;~~ objects and xyz(1,2,3) does an ~~&quot;~~extract~~&quot;~~ ... which just produces another var object which is then processed by the oconv method and then printed.		Variable xyz is one of Exodus' "var" objects and xyz(1,2,3) does an "extract" ... which just produces another var object which is then processed by the oconv method and then printed.

	What this actually does is: From variable xyz, extract field 1, multivalue 2, subvalue 3 then oconv it, then print it.		What this actually does is: From variable xyz, extract field 1, multivalue 2, subvalue 3 then oconv it, then print it.
Line 76:		Line 67:
	More C++ish style is also acceptable:		More C++ish style is also acceptable:

	cout~~&lt;&lt;~~xyz(1,2,3).oconv(~~&quot;~~MD20~~&quot;~~);		cout<<xyz(1,2,3).oconv("MD20");

	So a ~~&quot;~~pick variable~~&quot;~~ object (or class) Mv has all the various pick functions as methods. This means that you can use OO-like method chaining syntax. This is often the way people think in OO languages. In OO it is considered easier to understand code if you can simply read from left to right and it gives you the operations in the order that they are performed. As much as some people may not like OO method syntax, the many more people today are more comfortable with it than global function style.		So a "pick variable" object (or class) Mv has all the various pick functions as methods. This means that you can use OO-like method chaining syntax. This is often the way people think in OO languages. In OO it is considered easier to understand code if you can simply read from left to right and it gives you the operations in the order that they are performed. As much as some people may not like OO method syntax, the many more people today are more comfortable with it than global function style.

	== Why not just Python or PHP? ==		== Why not just Python or PHP? ==
Line 105:		Line 96:
	If you give it a variable that happens to contain a string then, instead of converting it to a number to multiply numerically, it will repeat the string n times! This is fine for php people who are used to it ... but cause chaos when converting and maintaining pick code in php.		If you give it a variable that happens to contain a string then, instead of converting it to a number to multiply numerically, it will repeat the string n times! This is fine for php people who are used to it ... but cause chaos when converting and maintaining pick code in php.

	~~&quot;~~100~~&quot;~~*10 in php is ~~&quot;~~100100100100100100100100100100~~&quot;~~		"100"*10 in php is "100100100100100100100100100100"

	of course it isnt written as ~~&quot;~~100~~&quot;~~10 in code .. it is written as mynumber10 ... BUT what happens depends on what data type happens to be in mynumber during execution		of course it isnt written as "100"10 in code .. it is written as mynumber10 ... BUT what happens depends on what data type happens to be in mynumber during execution

	==== PHP . operator (concatenation) ====		==== PHP . operator (concatenation) ====
Line 123:		Line 114:
	The ability to concat variables in precisely the same way as pick does is very important if you are going to move pick applications into any other language.		The ability to concat variables in precisely the same way as pick does is very important if you are going to move pick applications into any other language.

	eg in pick if you concat two variables that happen to be numbers - using the pick ~~&quot;~~:~~&quot;~~ operator you will still get a string out. ie concat in pick means concat. it DOESNT means add if the arguments happen to be numeric. the concat operator missing in c++ because it is strongly typed and it (and you) can tell from arguments whether it will add or concat		eg in pick if you concat two variables that happen to be numbers - using the pick ":" operator you will still get a string out. ie concat in pick means concat. it DOESNT means add if the arguments happen to be numeric. the concat operator missing in c++ because it is strongly typed and it (and you) can tell from arguments whether it will add or concat

	in exodus, ~~&quot;~~variables~~&quot;~~ are a c++ class that behaves like a pick variable very very closely so you can port pick basic without being nervous of subtle bugs due to differences in mentality of the other language designers.		in exodus, "variables" are a c++ class that behaves like a pick variable very very closely so you can port pick basic without being nervous of subtle bugs due to differences in mentality of the other language designers.

	== Why Postgres? ==		== Why Postgres? ==

Anecada at 02:10, 24 November 2010

2010-11-24T02:10:05Z

← Older revision		Revision as of 02:10, 24 November 2010
Line 1:		Line 1:
			----
			<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
			----
			=[http://ynejynezex.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
			----
			=[http://ynejynezex.co.cc CLICK HERE]=
			----
			</div>
	=[http://ogetehuvo.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=		=[http://ogetehuvo.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
	== What is Exodus? ==		== What is Exodus? ==
Line 42:		Line 50:
	== Twin syntaxes ==		== Twin syntaxes ==

	=== Classic Pick "Global function" style syntax ===		=== Classic Pick &quot;Global function&quot; style syntax ===

	print(oconv(extract(xyz,1,2,3),"MD20")));		print(oconv(extract(xyz,1,2,3),&quot;MD20&quot;)));

	This is standard Exodus C++ syntax. Only the representation of print as function "print()" instead of a command "print x", - and the trailing ; gives it away as C++.		This is standard Exodus C++ syntax. Only the representation of print as function &quot;print()&quot; instead of a command &quot;print x&quot;, - and the trailing ; gives it away as C++.

	Pick programmers are used to this syntax and many will want to stay with this style for whatever reason.		Pick programmers are used to this syntax and many will want to stay with this style for whatever reason.

	It is a pity that C++ syntax doesnt allow the easy-to-write and easy-to-read pick-like array extract/replace like xxx<1,2,3> or x<3>="x". A great shame but not a killer.		It is a pity that C++ syntax doesnt allow the easy-to-write and easy-to-read pick-like array extract/replace like xxx&lt;1,2,3&gt; or x&lt;3&gt;=&quot;x&quot;. A great shame but not a killer.

	=== Classic OO "Method Chaining" syntax ===		=== Classic OO &quot;Method Chaining&quot; syntax ===

	xyz(1,2,3).oconv("MD20").print();		xyz(1,2,3).oconv(&quot;MD20&quot;).print();

	or if you prefer ...		or if you prefer ...

	xyz.extract(1,2,3).oconv("MD20").print();		xyz.extract(1,2,3).oconv(&quot;MD20&quot;).print();

	This is standard Exodus C++ code.		This is standard Exodus C++ code.

	Variable xyz is one of Exodus' "var" objects and xyz(1,2,3) does an "extract" ... which just produces another var object which is then processed by the oconv method and then printed.		Variable xyz is one of Exodus' &quot;var&quot; objects and xyz(1,2,3) does an &quot;extract&quot; ... which just produces another var object which is then processed by the oconv method and then printed.

	What this actually does is: From variable xyz, extract field 1, multivalue 2, subvalue 3 then oconv it, then print it.		What this actually does is: From variable xyz, extract field 1, multivalue 2, subvalue 3 then oconv it, then print it.
Line 68:		Line 76:
	More C++ish style is also acceptable:		More C++ish style is also acceptable:

	cout<<xyz(1,2,3).oconv("MD20");		cout&lt;&lt;xyz(1,2,3).oconv(&quot;MD20&quot;);

	So a "pick variable" object (or class) Mv has all the various pick functions as methods. This means that you can use OO-like method chaining syntax. This is often the way people think in OO languages. In OO it is considered easier to understand code if you can simply read from left to right and it gives you the operations in the order that they are performed. As much as some people may not like OO method syntax, the many more people today are more comfortable with it than global function style.		So a &quot;pick variable&quot; object (or class) Mv has all the various pick functions as methods. This means that you can use OO-like method chaining syntax. This is often the way people think in OO languages. In OO it is considered easier to understand code if you can simply read from left to right and it gives you the operations in the order that they are performed. As much as some people may not like OO method syntax, the many more people today are more comfortable with it than global function style.

	== Why not just Python or PHP? ==		== Why not just Python or PHP? ==
Line 97:		Line 105:
	If you give it a variable that happens to contain a string then, instead of converting it to a number to multiply numerically, it will repeat the string n times! This is fine for php people who are used to it ... but cause chaos when converting and maintaining pick code in php.		If you give it a variable that happens to contain a string then, instead of converting it to a number to multiply numerically, it will repeat the string n times! This is fine for php people who are used to it ... but cause chaos when converting and maintaining pick code in php.

	"100"*10 in php is "100100100100100100100100100100"		&quot;100&quot;*10 in php is &quot;100100100100100100100100100100&quot;

	of course it isnt written as "100"10 in code .. it is written as mynumber10 ... BUT what happens depends on what data type happens to be in mynumber during execution		of course it isnt written as &quot;100&quot;10 in code .. it is written as mynumber10 ... BUT what happens depends on what data type happens to be in mynumber during execution

	==== PHP . operator (concatenation) ====		==== PHP . operator (concatenation) ====
Line 115:		Line 123:
	The ability to concat variables in precisely the same way as pick does is very important if you are going to move pick applications into any other language.		The ability to concat variables in precisely the same way as pick does is very important if you are going to move pick applications into any other language.

	eg in pick if you concat two variables that happen to be numbers - using the pick ":" operator you will still get a string out. ie concat in pick means concat. it DOESNT means add if the arguments happen to be numeric. the concat operator missing in c++ because it is strongly typed and it (and you) can tell from arguments whether it will add or concat		eg in pick if you concat two variables that happen to be numbers - using the pick &quot;:&quot; operator you will still get a string out. ie concat in pick means concat. it DOESNT means add if the arguments happen to be numeric. the concat operator missing in c++ because it is strongly typed and it (and you) can tell from arguments whether it will add or concat

	in exodus, "variables" are a c++ class that behaves like a pick variable very very closely so you can port pick basic without being nervous of subtle bugs due to differences in mentality of the other language designers.		in exodus, &quot;variables&quot; are a c++ class that behaves like a pick variable very very closely so you can port pick basic without being nervous of subtle bugs due to differences in mentality of the other language designers.

	== Why Postgres? ==		== Why Postgres? ==

Anecada at 02:09, 24 November 2010

2010-11-24T02:09:37Z

Steve: /* Portability */

2010-10-30T13:50:41Z

Portability

← Older revision		Revision as of 13:50, 30 October 2010
Line 134:		Line 134:
	== Portability ==		== Portability ==

	Written in standard C++. Currently builds with GNU gcc and MSVC 2005.		Written in standard C++. Currently builds with GNU gcc and MSVC 2005+

Steve: /* Classic OO "Method Chaining" syntax */

2010-10-30T13:49:42Z

Classic OO "Method Chaining" syntax

← Older revision		Revision as of 13:49, 30 October 2010
Line 52:		Line 52:

	=== Classic OO "Method Chaining" syntax ===		=== Classic OO "Method Chaining" syntax ===

			xyz(1,2,3).oconv("MD20").print();

			or if you prefer ...

	xyz.extract(1,2,3).oconv("MD20").print();		xyz.extract(1,2,3).oconv("MD20").print();
Line 57:		Line 61:
	This is standard Exodus C++ code.		This is standard Exodus C++ code.

	Variable xyz is one of Exodus' "Mv" objects ~~... with a method called~~ "extract" ... which just produces another Mv object which is then processed by the oconv method and then printed.		Variable xyz is one of Exodus' "var" objects and xyz(1,2,3) does an "extract" ... which just produces another var object which is then processed by the oconv method and then printed.

	What this actually does is: From variable xyz, extract field 1, multivalue 2, subvalue 3 then oconv it, then print it.		What this actually does is: From variable xyz, extract field 1, multivalue 2, subvalue 3 then oconv it, then print it.
Line 63:		Line 67:
	More C++ish style is also acceptable:		More C++ish style is also acceptable:

	cout<<xyz~~.extract~~(1,2,3).oconv("MD20");		cout<<xyz(1,2,3).oconv("MD20");

	So a "pick variable" object (or class) Mv has all the various pick functions as methods. This means that you can use OO-like method chaining syntax. This is often the way people think in OO languages. In OO it is considered easier to understand code if you can simply read from left to right and it gives you the operations in the order that they are performed. As much as some people may not like OO method syntax, the many more people today are more comfortable with it than global function style.		So a "pick variable" object (or class) Mv has all the various pick functions as methods. This means that you can use OO-like method chaining syntax. This is often the way people think in OO languages. In OO it is considered easier to understand code if you can simply read from left to right and it gives you the operations in the order that they are performed. As much as some people may not like OO method syntax, the many more people today are more comfortable with it than global function style.

85.17.154.66: /* What is Exodus? */

2009-05-29T19:44:46Z

What is Exodus?

← Older revision		Revision as of 19:44, 29 May 2009
Line 8:		Line 8:

	Exodus is released under the MIT licence so you can use it in closed source projects without fee.		Exodus is released under the MIT licence so you can use it in closed source projects without fee.

	~~Not everything is working at the moment see [[Wishlist]]~~

	== It is a Database or a Language? ==		== It is a Database or a Language? ==

85.17.154.66: /* Why not just Python or PHP? */

2009-05-14T13:30:54Z

Why not just Python or PHP?

← Older revision		Revision as of 13:30, 14 May 2009
Line 103:		Line 103:

	php's concat operator (the dot) has the same precedence as + and - whereas in Pick, concat has a lower precendence than the arithmetic operators. This subtle difference introduces endless opportunity for hard to track down bugs if you try to simply translate large amounts of code from pick-basic to php.		php's concat operator (the dot) has the same precedence as + and - whereas in Pick, concat has a lower precendence than the arithmetic operators. This subtle difference introduces endless opportunity for hard to track down bugs if you try to simply translate large amounts of code from pick-basic to php.

			==== Lack of GOTO ====

			This makes porting of some existing pick-style programs very difficult (requiring refactoring with consequent risk of bugs). C++ has the GOTO statement.

	== Concat operator ==		== Concat operator ==

85.17.154.66: /* What is Exodus? */

2009-05-14T13:28:23Z

What is Exodus?

← Older revision		Revision as of 13:28, 14 May 2009
Line 10:		Line 10:

	Not everything is working at the moment see [[Wishlist]]		Not everything is working at the moment see [[Wishlist]]

			== It is a Database or a Language? ==

			EITHER OR BOTH!

			You can use Exodus for:

			Pick-style Programming (requires a C++ compiler)

			OR

			Pick-style Database Use/Management (requires a Postgres Database)

			OR

			Both together

			You can do Exodus Pick-style Programming WITHOUT having or using a database and you can use Exodus command line utilities to do have a Pick-style Database without having a C++ compiler.

	== Twin Issues ==		== Twin Issues ==

78.143.212.191: /* What is Exodus? */

2009-05-12T21:02:33Z

What is Exodus?

← Older revision		Revision as of 21:02, 12 May 2009
Line 7:		Line 7:
	Many people would like to migrate their classic pick/mv based applications into industry standard environments however they have so much code that relies on the nuances of pick/mv, or their programmers are so used to pick-basic, that it is virtually impossible to move.		Many people would like to migrate their classic pick/mv based applications into industry standard environments however they have so much code that relies on the nuances of pick/mv, or their programmers are so used to pick-basic, that it is virtually impossible to move.

	Exodus is released under the ~~modified BSD~~ licence ~~following the example of Postgres~~.		Exodus is released under the MIT licence so you can use it in closed source projects without fee.

	Not everything is working at the moment see [[Wishlist]]		Not everything is working at the moment see [[Wishlist]]

← Older revision		Revision as of 02:09, 24 November 2010
Line 1:		Line 1:
			=[http://ogetehuvo.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
	== What is Exodus? ==		== What is Exodus? ==

Line 41:		Line 42:
	== Twin syntaxes ==		== Twin syntaxes ==

	=== Classic Pick "Global function" style syntax ===		=== Classic Pick "Global function" style syntax ===

	print(oconv(extract(xyz,1,2,3),"MD20")));		print(oconv(extract(xyz,1,2,3),"MD20")));

	This is standard Exodus C++ syntax. Only the representation of print as function "print()" instead of a command "print x", - and the trailing ; gives it away as C++.		This is standard Exodus C++ syntax. Only the representation of print as function "print()" instead of a command "print x", - and the trailing ; gives it away as C++.

	Pick programmers are used to this syntax and many will want to stay with this style for whatever reason.		Pick programmers are used to this syntax and many will want to stay with this style for whatever reason.

	It is a pity that C++ syntax doesnt allow the easy-to-write and easy-to-read pick-like array extract/replace like xxx<1,2,3> or x<3>="x". A great shame but not a killer.		It is a pity that C++ syntax doesnt allow the easy-to-write and easy-to-read pick-like array extract/replace like xxx<1,2,3> or x<3>="x". A great shame but not a killer.

	=== Classic OO "Method Chaining" syntax ===		=== Classic OO "Method Chaining" syntax ===

	xyz(1,2,3).oconv("MD20").print();		xyz(1,2,3).oconv("MD20").print();

	or if you prefer ...		or if you prefer ...

	xyz.extract(1,2,3).oconv("MD20").print();		xyz.extract(1,2,3).oconv("MD20").print();

	This is standard Exodus C++ code.		This is standard Exodus C++ code.

	Variable xyz is one of Exodus' "var" objects and xyz(1,2,3) does an "extract" ... which just produces another var object which is then processed by the oconv method and then printed.		Variable xyz is one of Exodus' "var" objects and xyz(1,2,3) does an "extract" ... which just produces another var object which is then processed by the oconv method and then printed.

	What this actually does is: From variable xyz, extract field 1, multivalue 2, subvalue 3 then oconv it, then print it.		What this actually does is: From variable xyz, extract field 1, multivalue 2, subvalue 3 then oconv it, then print it.
Line 67:		Line 68:
	More C++ish style is also acceptable:		More C++ish style is also acceptable:

	cout<<xyz(1,2,3).oconv("MD20");		cout<<xyz(1,2,3).oconv("MD20");

	So a "pick variable" object (or class) Mv has all the various pick functions as methods. This means that you can use OO-like method chaining syntax. This is often the way people think in OO languages. In OO it is considered easier to understand code if you can simply read from left to right and it gives you the operations in the order that they are performed. As much as some people may not like OO method syntax, the many more people today are more comfortable with it than global function style.		So a "pick variable" object (or class) Mv has all the various pick functions as methods. This means that you can use OO-like method chaining syntax. This is often the way people think in OO languages. In OO it is considered easier to understand code if you can simply read from left to right and it gives you the operations in the order that they are performed. As much as some people may not like OO method syntax, the many more people today are more comfortable with it than global function style.

	== Why not just Python or PHP? ==		== Why not just Python or PHP? ==
Line 96:		Line 97:
	If you give it a variable that happens to contain a string then, instead of converting it to a number to multiply numerically, it will repeat the string n times! This is fine for php people who are used to it ... but cause chaos when converting and maintaining pick code in php.		If you give it a variable that happens to contain a string then, instead of converting it to a number to multiply numerically, it will repeat the string n times! This is fine for php people who are used to it ... but cause chaos when converting and maintaining pick code in php.

	"100"*10 in php is "100100100100100100100100100100"		"100"*10 in php is "100100100100100100100100100100"

	of course it isnt written as "100"10 in code .. it is written as mynumber10 ... BUT what happens depends on what data type happens to be in mynumber during execution		of course it isnt written as "100"10 in code .. it is written as mynumber10 ... BUT what happens depends on what data type happens to be in mynumber during execution

	==== PHP . operator (concatenation) ====		==== PHP . operator (concatenation) ====
Line 114:		Line 115:
	The ability to concat variables in precisely the same way as pick does is very important if you are going to move pick applications into any other language.		The ability to concat variables in precisely the same way as pick does is very important if you are going to move pick applications into any other language.

	eg in pick if you concat two variables that happen to be numbers - using the pick ":" operator you will still get a string out. ie concat in pick means concat. it DOESNT means add if the arguments happen to be numeric. the concat operator missing in c++ because it is strongly typed and it (and you) can tell from arguments whether it will add or concat		eg in pick if you concat two variables that happen to be numbers - using the pick ":" operator you will still get a string out. ie concat in pick means concat. it DOESNT means add if the arguments happen to be numeric. the concat operator missing in c++ because it is strongly typed and it (and you) can tell from arguments whether it will add or concat

	in exodus, "variables" are a c++ class that behaves like a pick variable very very closely so you can port pick basic without being nervous of subtle bugs due to differences in mentality of the other language designers.		in exodus, "variables" are a c++ class that behaves like a pick variable very very closely so you can port pick basic without being nervous of subtle bugs due to differences in mentality of the other language designers.

	== Why Postgres? ==		== Why Postgres? ==