User Tools

Site Tools


future

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
future [2020/02/17 09:45] adminzfuture [2020/02/22 18:11] (current) jtwine
Line 4: Line 4:
 ===== Additional Intrinsic Statements ===== ===== Additional Intrinsic Statements =====
 By researching some more existing 9010A programs/code, I might be able to figure out some additional intrinsic statements that might be useful.  Might also consider breaking the intrinsics up into multiple smaller programs, so you do not take the hit on intrinsics that you do not use. By researching some more existing 9010A programs/code, I might be able to figure out some additional intrinsic statements that might be useful.  Might also consider breaking the intrinsics up into multiple smaller programs, so you do not take the hit on intrinsics that you do not use.
 +
 +
 +===== Poke (Write) Tables =====
 +There is a good amount of 9LC code out there that has to deal with filing a decent range of memory with different values.  This results in having to come lots of district ''Write'' statements which can get real tedious, real fast (not to mention error prone).
 +
 +So I am thinking of implementing a type of table construct that can be coded easily, and processed by the compiler into the necessary ''Write'' statements.  I am feeling that implementing the feature as a list of //runs// might work.  For example, if I wanted to fill memory from 0x1000 to 0x1008 I could do something like:
 +
 +<code c>
 +WriteTable( 0x1000, 1, 2, 3, 4, 5, 6, 7, 8 );
 +</code>
 +
 +Which would yield:
 +
 +<code c>
 +Write @ 0x1000 = 1;
 +Write @ 0x1001 = 2;
 +Write @ 0x1002 = 3;
 +Write @ 0x1003 = 4;
 +Write @ 0x1004 = 5;
 +Write @ 0x1005 = 6;
 +Write @ 0x1006 = 7;
 +Write @ 0x1007 = 8;
 +</code>
 +
 +''Note'': this has been implemented via the ''[[documentation|WriteEx]]'' statement.
  
 ===== Additional Semantic Checks ===== ===== Additional Semantic Checks =====
Line 40: Line 65:
  
 Maybe one day... Maybe one day...
 +
 +===== Method Call Syntax =====
 +One of the things I have been kicking around is the possibility of making 10LC look more like //method calls// in a language like C/C++/C#/Java/etc. instead of just like text script.  An example of the ''Write'' statement is:
 +<code c>
 +Write @ 0x1000 = 1234;
 +</code>
 +But would it be better or more appealing if the statement was written like:
 +<code c>
 +Write( 0x1000, 1234 );
 +</code>
 +Or maybe that would only be preferable to actual software developers/programmers and not those used to just script?
 +
future.1581954320.txt.gz · Last modified: 2020/02/17 09:45 by adminz