Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: Stoked Date: Wed, 11 Nov 2015 20:49:42 -0800 Organization: A noiseless patient Spider Lines: 29 Message-ID: <87fv0brfdl.fsf@nightsong.com> References: <284a0c81-1d04-406d-a84b-39d4617375f3@googlegroups.com> <87egg1wu31.fsf@nightsong.com> <87a8qpwl3x.fsf@nightsong.com> <87611dwio9.fsf@nightsong.com> <871tc1wg1b.fsf@nightsong.com> <87pozluhfj.fsf@nightsong.com> <87lha9ufhc.fsf@nightsong.com> <878u68vngr.fsf@nightsong.com> <87mvuotbz3.fsf@nightsong.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="1a9f5856d25720e42c135b990c70bebb"; logging-data="24533"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19A/tvVNGKyLFpyubnUirh0" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:zUzZywEzl3XZP4cyRP8Q0kHYYvM= sha1:PE+U1/ffFitn+jC9pFAm0cmP1uI= Xref: csiph.com comp.lang.forth:43489 rickman writes: > And you need to create a file system to support that. I see no value > in this since it completely lacks all the normal mechanisms of > support... unless you want to reinvent all those wheels as well. What normal mechanisms? I was imagining the same stuff that existed in F83 and Polyforth, very traditional. I admittedly have never used either of those, but have always wondered what the experience was like. > Then when you work with an MCU that only has 64 kB of flash you have > to revert to using a PC host. The cpu of immediate interest is the MSP430FR6989 which has 128K of FRAM, but I take your point: small MCU's can't really support this approach while bigger (e.g. rPi level) boards can handle full blown OS's, so there's only a narrow middle range where the concept has any plausible appeal. >> The Forth development environment, external assembler, etc. that you >> want on the host instead of the target. > What development environment? You are putting words in my mouth. > Check out Mecrisp. I don't think there's a way to modify and rebuild Mecrisp from source without using tools outside of Mecrisp itself. The historical Forths were capable of total self-bootstrapping. I think that's an incredibly cool characteristic. Whether that's of much practical benefit, I don't know, but how can any red-blooded programmer not want to check out such a system if it exists?