Re: CamelForth x86 32-bit for Linux

2010-09-06T19:45:04-04:00

peter wrote ...Garry Lancaster http://www.worldofspectrum.org/z88forever/camelforth/rom-camel.html has a pretty useful implementation of camelforth with block and file support. It will be a good base for getting file and block support into camelforth /x86.I'd like to add my thanks for the link as well. Although there are many PC Forths already available that have these features, it would be really nice to have file and block support in CamelForth/8086 - a simple, clean Forth which I'm already familiar with!

Re: CamelForth x86 32-bit for Linux

2010-09-06T19:26:07-04:00

Brad R wrote ...NFA>CFA is a word unique to CamelForth; it's not an ANS word. And LATEST is also not an ANS word; it appears in many Forth implementations, but possibly with different meanings. So technically the MSP430 assembler is not an ANS Forth Program (it relies upon non-standard words).It's been a long time since I ran the 8086 CamelForth, but as I recall, I loaded the validation suite by redirecting the DOS standard input. The problem is returning to the command line interpreter when that is done. CamelForth was originally envisioned as an embedded Forth, so INCLUDE-FILE was never added. I'd think that would be a useful addition to the Linux implementation. (It would also be useful for the DOS implementation, but who is using DOS anymore?)I discovered that NFA>CFA and LATEST weren't ANS words during my investigations, and I guess I can understand why. But they've been in several Forths I've used, some also nominally ANS Forth programs. Assemblers, by necessity, have to operate at a pretty low level of Forth, so this kind of incompatibility is probably unavoidable.I was finally able to compile the MSP430 assembler under Win32Forth. Along the way, I discovered that there were some typos in the downloaded source code (I just downloaded another copy to verify that this was still the case). Specifically:
line 251, is: 8040 2)OPCODE SUB.B " should be: 8040 2_OPCODE SUB.B, " (underscore after 2, comma after SUB.B) line 302, is: : #-1, ( -- u ) 3 @S+ ; -1 ( 0FFFFh) =SRC content should be: : #-1, ( -- u ) 3 @S+, ; -1 ( 0FFFFh) =SRC content (comma after @S+) line 371 is: IHERE OVER - 2/ FC00 OR OVER @ AND SWAP ! complete IF, jump should be: IHERE OVER - 2/ FC00 OR OVER @ AND SWAP ! ; complete IF, jump (semicolon to complete definition) line 378 is: IHERE OVER - 2/ FC00 OR OVER @ AND SWAP ! finish JNZ, should be: IHERE OVER - 2/ FC00 OR OVER @ AND SWAP ! finish JNZ, (semicolon to complete definition)
I found correlates to LATEST and NFA>CFA under Win32Forth - ADP and N>CFAPTR. Since Win32Forth is a very large Forth (they haven't left much out), the dictionary space is divided into 3 parts - ADP is the current application dictionary pointer. N>CFAPTR is just a less clear renaming of the NFA>CFA function, as far as I could tell.I also remembered that

Re: Bazaar Version Control

2010-09-06T18:04:23-04:00

I wasn't feeling forgotten Brad! But I decided to do some experimenting on my own. What follows is a message I was in the middle of composing.I've been playing with Bazaar (using both the command line and Bazaar Explorer) and Launchpad. It turns out that the project on Launchpad is more egalitarian than I had assumed. I still want to be added as a developer, but there's a lot you can do, even without developer status. I'll detail my experiences here as a form of documentation and in case it may help someone else.I went to the CamelForth repository on Launchpad, logged in (I'm Frogman, btw), and clicked on the "Branches." link. There I saw a "Register a branch" link. I figured I'd give it a shot and that I wouldn't be authorized for anything I wasn't supposed to do (better to seek forgiveness than permission!). Low and behold, I was able to create a "lp:~jporubek/camelforth/contrib" branch, where "jporubek" is my Launchpad login name and "contrib" was the name I gave to the branch. At this point, the branch was empty.Then I created a local copy of the repository on my computer using "bzr branch lp:camelforth". Note that this creates a camelforth subdirectory under the directory your in when you execute the above command. Up to this point, all you need is a generic account in Launchpad.To push things back to Launchpad, you need to set up an electronic signature to prove your identity. You can use an OpenPGP key or an SSH key. I chose the latter. By the way, Launchpad provides pretty good and comprehensive help for all these steps. So I created and uploaded my public SSH key and I was ready to continue.Even though I hadn't made any additions or changes yet, I wanted to try pushing my "contrib" branch back to Launchpad just to see how it worked. From within the camelforth subdirectory created when you set up the local repository above, type "bzr launchpad-login userid". Now you wouldn't think this step needs any more explanation, but I was stuck here for a while until I figured out that "launchpad-login" is part of the actual command (not a place holder) and that "userid" IS a place holder for your Launchpad login name. Since I was in the camelforth directory, what got pushed was the original camelforth branch (the push wouldn't work from another directory - I got a "Not a branch" error when I tried).Next I pulled my branch back with a "bzr branch lp:~jporubek/camelforth/contrib" and it created a "contrib" subdirectory in my local copy of the camelforth branch. From here I switched to Bazaar Explorer to manipulate the contrib branch. I deleted the camelforth subdirectories I wasn't likely to be doing anything with, committed the changes to my local repository and pushed back to Launchpad. That's where I'm at now. I haven't added anything yet but I think I now know how.

Re: CamelForth x86 32-bit for Linux

2010-09-05T21:22:22-04:00

Thanks for that link -- that's a port I wasn't aware of! I've added a link in the sidebar under "Offsite Downloads." (I guess I need a new category for these on the Links page, as well.)

Re: Bazaar Version Control

2010-09-05T21:00:21-04:00

I haven't forgotten you, John, but I'm still trying to figure out how to add you as a developer in Launchpad. I think it's time that I went through the full Launchpad tutorial....last time I only learned enough to learn how to push a Bazaar repository there.

Re: CamelForth x86 32-bit for Linux

2010-09-01T12:00:27-04:00

Garry Lancaster http://www.worldofspectrum.org/z88forever/camelforth/rom-camel.html has a pretty useful implementation of camelforth with block and file support. It will be a good base for getting file and block support into camelforth /x86.

Re: CamelForth x86 32-bit for Linux

2010-08-29T08:58:18-04:00

NFA>CFA is a word unique to CamelForth; it's not an ANS word. And LATEST is also not an ANS word; it appears in many Forth implementations, but possibly with different meanings. So technically the MSP430 assembler is not an ANS Forth Program (it relies upon non-standard words).It's been a long time since I ran the 8086 CamelForth, but as I recall, I loaded the validation suite by redirecting the DOS standard input. The problem is returning to the command line interpreter when that is done. CamelForth was originally envisioned as an embedded Forth, so INCLUDE-FILE was never added. I'd think that would be a useful addition to the Linux implementation. (It would also be useful for the DOS implementation, but who is using DOS anymore?)

Re: Bazaar Version Control

2010-08-29T08:48:38-04:00

Yes, sorry, I do check the forums every day, but for the last few months my work schedule has bordered on insane -- not to mention the DDoS attacks on this site and some others I run -- so I haven't been able to devote much time to CamelForth development.Re. your procedural question, I've never managed a group open-source project, so I don't know the best organization. I've used version control personally, and as part of a small development team, and on one project as part of a larger team -- but on that latter project I've been just a contributor, and repository management was someone else's reponsibility.(Interestingly, I've just been reading a blog post from Eric S. Raymond where this question is briefly addressed.)I know that in the interest of least effort (a.k.a. laziness), I'm inclined to edit the main branch on my machine and push those changes directly to the repository. With only a few contributors, and with small incremental changes, that can work. But I'd think drastic or wildly experimental changes shouldn't go in the main branch.I'm open to suggestions on this. And I'm certainly happy to set up a separate branch for any contributor.

Re: CamelForth x86 32-bit for Linux

2010-08-28T21:04:05-04:00

I have compiled and run it also. It could be really useful. I'd like to run BSquare's MSP430 assembler on a PC as a cross-assembler. Does anyone know how I could "download" the assembler to CamelForth/8086? It seems like it shouldn't be too difficult in a Linux environment, but I can't figure out how to do it.I tried loading the file into Win32Forth and Gforth, but the former choked on "LATEST" and the later choked on "NFA>CFA" in "DOESCODE>", the very first colon definition! It shouldn't be too hard to fix either problem, but it's a little frustrating that three ANS Forth implementations should be so incompatible.I know CamelForth/8086 should be compatible, but I have the file load / download problem.

CamelForth : Forum / posts

Re: CamelForth x86 32-bit for Linux

Re: CamelForth x86 32-bit for Linux

Re: Bazaar Version Control

Re: CamelForth x86 32-bit for Linux

Re: Bazaar Version Control

Re: CamelForth x86 32-bit for Linux

Re: CamelForth x86 32-bit for Linux

Re: Bazaar Version Control

Re: CamelForth x86 32-bit for Linux