Unorganised notes about programming in Exodus - Revision history

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

2010-11-24T13:59:27Z

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

2010-11-24T02:08:59Z

2010-10-31T17:51:13Z

C++ exodus

← Older revision		Revision as of 17:51, 31 October 2010
Line 1:		Line 1:
	The following is just a scrap pad of ideas to be incorporated in documentation		The following is just a scrap pad of ideas to be incorporated in documentation

			== new syntax possibility ==

			Some will hate this. Some will love it.

			//mass declaration and mass initialisation.
			var abc,xyz,qwe;
			abc=xyz=qwe="";

	== C++ exodus ==		== C++ exodus ==

2010-10-25T19:25:30Z

← Older revision		Revision as of 19:25, 25 October 2010
Line 64:		Line 64:
	most languages allow interfacing at the C/C++ level so exodus can be used for this directly without depending on any interfaces.		most languages allow interfacing at the C/C++ level so exodus can be used for this directly without depending on any interfaces.

	=== ~~fieldstorer and~~		== fieldstorer ==

	fieldstorer (but not fieldstore) is an “statement-like” or “mutator” function which modifies the existing string instead of creating a new one. It can be implemented internally to be MUCH faster than xx=fieldstore(xx,”*”,2,2,”ii”) which first produces a new string and destroys the old one.		fieldstorer (but not fieldstore) is an “statement-like” or “mutator” function which modifies the existing string instead of creating a new one. It can be implemented internally to be MUCH faster than xx=fieldstore(xx,”*”,2,2,”ii”) which first produces a new string and destroys the old one.

2010-10-25T19:19:39Z

Massive String Text

← Older revision		Revision as of 19:19, 25 October 2010
Line 187:		Line 187:
	Compile-time string concatenation is useful since long text can be created on multiple lines without requiring any concatenation operator		Compile-time string concatenation is useful since long text can be created on multiple lines without requiring any concatenation operator

			<pre>
	var xx= "line1 line1 line1 line1"		var xx= "line1 line1 line1 line1"
	"\nline2 line2 line2 line2"		"\nline2 line2 line2 line2"
Line 192:		Line 193:
	"\nline4 line4 line4 line4"		"\nline4 line4 line4 line4"
	"\nline5 line5 line5 line5";		"\nline5 line5 line5 line5";
			</pre>

	You can only use Exodus ^ concatenation operator when either the left or the right bit is an Exodus variable (or the result of an operation on an Exodus variable)		You can only use Exodus ^ concatenation operator when either the left or the right bit is an Exodus variable (or the result of an operation on an Exodus variable)

2010-10-25T19:19:02Z

Massive String Text

@@ Line 184: / Line 184: @@
   var xx="word1" "word2" "word3";
 Compile-time string concatenation is useful since long text can be created on multiple lines without requiring any concatenation operator
@@ Line 203: / Line 192: @@
 	"\nline4 line4 line4 line4"
 	"\nline5 line5 line5 line5";

2010-10-25T19:16:23Z

@@ Line 87: / Line 87: @@
-=== substr and splice ===
+== substr and splice ==
 It is with great sadness that I announce the death of multivalue/pick basic's beautifully concise square bracket syntax [x,y] since it is not available with two parameters in the family of c-like languages.
@@ Line 124: / Line 124: @@
-=== OS level command shell ===
+== OS level command shell ==
 the bash command line shell treats various characters specially including " ' ( ) < > $ ! and others. You must escape/prefix them by \ to stop bash from messing with them.
@@ Line 143: / Line 143: @@
 exodus allows the use {} can be used for () brackets if at the end of the command

2010-10-17T20:15:52Z

OS level command shell

@@ Line 64: / Line 64: @@
 most languages allow interfacing at the C/C++ level so exodus can be used for this directly without depending on any interfaces.
-== OS level command shell ==
+=== fieldstorer and
 the bash command line shell treats various characters specially including " ' ( ) < > $ ! and others. You must escape/prefix them by \ to stop bash from messing with them.

2010-10-17T20:10:53Z

← Older revision		Revision as of 20:10, 17 October 2010
Line 1:		Line 1:
	~~== c++ exodus ==~~		The following is just a scrap pad of ideas to be incorporated in documentation

	~~Following is VERY RANDOM~~ and ~~just ideas~~ to be ~~documented nicely later on~~.		== C++ exodus ==

			#Just because you can write C in C++ doesnt mean you should! Dont include C libraries and you wont be able to.
			#Just because you can write C++ in Exodus programs doesnt mean you should! Dont include C++ libraries and you wont be able to.

	if you are only familiar with c then c++ has some improvements for examples like you can declare your variables at the point they are used (and not at the top of the routine like c)		if you are only familiar with c then c++ has some improvements for examples like you can declare your variables at the point they are used (and not at the top of the routine like c)

2010-10-17T20:06:40Z

many functions and subroutines per file

← Older revision		Revision as of 20:06, 17 October 2010
Line 41:		Line 41:
	=== many functions and subroutines per file ===		=== many functions and subroutines per file ===

	pick only allows one function or subroutine per file. c++ is happy with many. editing and compiling groups of associated subroutines and functions in a single file makes it easier to manage your source code base.		pick only allows one function or subroutine per file. c++ is happy with many.

			in some cases, editing and compiling groups of associated subroutines and functions in a single file makes it easier to manage your source code base.

	=== faster conditional expressions ===		=== faster conditional expressions ===