SPINFORTH might be on GITHUB
prof_braino
Posts: 4,313
Some folks asked about the version of forth constructed from spin tokens. SPINFORTH was Sal's first forth for the prop, and uses spin tokens. It turned out to go in a different direction than Sal's needs, but its still interesting. The google code repository has been exported to github.
https://github.com/prof-braino/spinforth
Take it out for a spin, and see where it takes you. Cheers!
Propforth is the continuation of this project, and will be exported to github shortly.
https://github.com/prof-braino/spinforth
Take it out for a spin, and see where it takes you. Cheers!
Propforth is the continuation of this project, and will be exported to github shortly.
Comments
I guess I'm doing something other than expected. Anyone know how to get the downloads page into github?
I should get an email today telling me if it worked or not.
Surely the "Export to github" button on the page you linked to above does the job.
The "Export to github" button on the page is what created the result you saw. It only took the wiki pages, it did not touch the downloads pages, which contain the zip archive of the enitre source, and the individual source files listed in the google code downloads section.
The thing that is different is that likely the export expects source only under the source tab, which we didn't do, as that wasn't how we we working at the time.
It looks like I have to "un-export" the project, and arrange things how the tool requires, and re-do the export. The instructions say:
' If you need to "un-move" a project, you can go back to the /adminAdvanced page at a later time and click "Publish". This will restore your project to its original state, before the move. '
Unfortunately, I find no "Publish" to click. This may be too big a PITA spend time on.
The source files and archive are now in the source section, and are displayed, the wiki pages are in the wiki subdirectory.
Please give this a look if you are considering a tool that uses spin byte codes.
Don't forget to add README.md and LICENCE.md files.
You should not have zip files in the repo. There is a download zip button on the page already.
That is some horrific assembler in NewForth.spin !
Is there any further reference to the SPIN bytcodes (other than in the verrious alternitive SPINcompilers, SPIN interpreters, and the original SPIN interpreter)?
A while back there was a thread where folks decoded the spin interpreter, and chip confirmed and corrected bits until we got a complete picture. But all that was over my head, I didn't join in until the hard parts were done.
--> Getting-started-with-Spinix-Thread
The instructions suggested to re-name them to get them out of the way, rather than risk deleting the wrong stuff. Once I figure out what I'm doing I will delete the rejects.
What is the MD extension on the readme anyway? I always use txt for text files. I'll move the readme and the liscence material into appropriate files in a bit, and use my notes to properly set up propforth5.5 and propforth6.0 repositories. The idea is to have the new archive similar as possible to the original, and this stuff was already setup but different. Aslo I don't want to invest too much time. It see less than 1 download per week, and I don't think anybody has actually asked any questions yet.
The main thing about spinforth is it demonstrates how re-using the spin byte codes DOESN'T work out so well for other tools. The design desicions that make spin work well tend to hinder forth etc. When we can change the byte codes and the way the processor work (as in FPGA) this becomes interesting again, but the result becomes incompatible with the physical prop 1 chips.
The assembler is a bit intense, never worked through it. When Sal gets going, he really gets going; and he determined this would not meet his needs and moved on. But it might provideperspectives for other folks that have other needs.
MD is Markdown. I think it's a great way to write simple documentation and, in fact, I've written all of PropWare's custom documentation with it. "Markdown is a text-to-HTML conversion tool for web writers." The idea is that HTML is a bit tedious for a human to read, so markdown was created as an alternative with a tiny subset of the features. It's meant to be equally legible in it's raw form and in it's displayed HTML form. Here's a great place to play around with it and learn the syntax.
Markdown is a text file. Same like HTML or early word processor formats like WordStar. Just an easy way to make simple documents.