headers
Ray St. Marie | 27 May 2006 23:59
Picon

CF05 'copy'ies two blocks instead of one.

Hello all,
Ray here.

Reporting that the 2005 version of colorforth changes the word copy to
include the block used to document the code block, and moves that
documentation to the block one after the code block being copied.

copy ( n -- )
effect: copy the current block in the editor and the next one, stored
as the editor system variable blk and move to the blocks n and n+1,
leave the editor with the target block displayed.

This is new for colorforth. This makes colorforth into a two block
system. Work block seperated by the space to document that block.

The thing to be aware of is when you have code on a documentation
block. Why would you want to do this? It used to be convenient to
temporarily use the doc-block as a version of the current code. They
would be side by side. You could compare them. You still can,
obviously. You just use + and - and stay on even blocks and not use
the doc-block for code ever.

I often found it a convenience to use copy to double words that were
used many times. Take for example ' ; ' semi-colon. It is now
necassary to copy to blocks at the end of the currently coded blocks
to use this method. The convenience was that you could do this between
two empty doc-blocks nearer to your code.

Still, a simple versioning system could be made out of just using copy
the new way, and adding to the left hand keyboard the + and - keys
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jeff Fox | 28 May 2006 01:25

Re: CF05 'copy'ies two blocks instead of one.

I copy was changed to one block on the version we use
sometime, perhaps around new years.  I found copy to
be easier to use if it just copied one block too.

And the idea is that odd numbered blocks are shadow
comment blocks.  They can be loaded, but by convention
they are just comments.

We used colors to make colorful comments on some shadow
blocks, but I don't think there is any actual code
on odd numbered blocks.  Because there is red and green
and yellow and white these comment blocks might include
copies of the code being explained, or the explanation
might be colorful.

Now in okad2, in the cross compiler, in the target
code blocks, I did put some target chip source code
on odd numbered blocks.  But that's way above the
public domain part.

We hope to have a new 1k kernel next week for the
colorforth rewrite project.  And we are trying to
address the concerns that people have had with
booting and interfaces.

In fact Chuck made another change in 2006 buy
removing the support for green variables. and
green variables from his code.  I didn't report
it, but the patch is just a store into the kernel.
I have been more focused on the apps than the
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ray St. Marie | 28 May 2006 22:13
Picon

Re: CF05 'copy'ies two blocks instead of one.

Thanks Jeff!
Ray here,

Good to hear about the updates.
I know I speak for more then myself when I say that we appreciate your
contact with us interested parties outside of your company. Thank you
for passing on to us the updates that you and Chuck and your team
develop.

I truely enjoy passing the time playing with colorforths.

Most recently, I found this description of the P'' language here
http://en.wikipedia.org/wiki/P_prime_prime
and created a simple memory editor for colorforth using those ideas.
The keyboard keys allow you to navigate to any part of memory,
displayed in a number of ways on the screen, and using P'' primitives,
you can scroll thru the values or type them in directly.

It just goes to show that the concatenation of two of the simplest
systems ever developed, can be made to be very usefull, very quickly.
And by people with out formal computing knowledge.

Even if I'm the only one who ever uses these together, it is a successful
usage of a machine for the person using it. I can render any kind of
custom colorforth database with the P'' system.

On 5/27/06, Jeff Fox <fox <at> ultratechnology.com> wrote:
> I copy was changed to one block on the version we use
> sometime, perhaps around new years.  I found copy to
> be easier to use if it just copied one block too.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane