Re: doing exercises for starting forth, kinda discouraging, some are easy and some seem text not prepare me for....

Newsgroups	comp.lang.forth
From	Albert van der Horst <albert@spenarnc.xs4all.nl>
Subject	Re: doing exercises for starting forth, kinda discouraging, some are easy and some seem text not prepare me for....
Date	2012-07-20 15:02 +0000
Message-ID	<m7gsgf.3ih@spenarnc.xs4all.nl> (permalink)
Organization	Dutch Forth Workshop
References	<2a5baeb8-2c72-41a6-8648-d52842405f18@n16g2000vbn.googlegroups.com> <wbOdnWwHX40ca5rNnZ2dnUVZ8lSdnZ2d@supernews.com> <m7f79o.4zm@spenarnc.xs4all.nl> <AoSdnRyPuOGE15XNnZ2dnUVZ8vWdnZ2d@supernews.com>

Show all headers | View raw

In article <AoSdnRyPuOGE15XNnZ2dnUVZ8vWdnZ2d@supernews.com>,
Andrew Haley  <andrew29@littlepinkcloud.invalid> wrote:
>Albert van der Horst <albert@spenarnc.xs4all.nl> wrote:
>> In article <wbOdnWwHX40ca5rNnZ2dnUVZ8lSdnZ2d@supernews.com>,
>> Andrew Haley  <andrew29@littlepinkcloud.invalid> wrote:
>>>Albert van der Horst <albert@spenarnc.xs4all.nl> wrote:
>>>> In article <ju7ifu02cet@enews2.newsguy.com>, WJ <w_a_x_man@yahoo.com> wrote:
>>>>>Anton Ertl wrote:
>>>>>
>>>>>> BTW, the source code for ;S and ?BRANCH is:
>>>>>>
>>>>>> ;s   ( R:w -- )              gforth  semis
>>>>>> ""The primitive compiled by @code{EXIT}.""
>>>>>> #ifdef NO_IP
>>>>>> INST_TAIL;
>>>>>> goto *(void *)w;
>>>>>> #else
>>>>>> SET_IP((Xt *)w);
>>>>>> #endif
>>>>>>
>>>>>> condbranch(?branch,f --,f83  question_branch,
>>>>>> ,if (f==0) {
>>>>>> ,:
>>>>>>  0= dup 0=          \ !f f
>>>>>>  r> tuck cell+      \ !f branchoffset f IP+
>>>>>>  and -rot @ and or  \ f&IP+|!f&branch
>>>>>>  >r ;)
>>>>>>
>>>>>> There's some m4 in this, some Vmgen, some C, and some Forth.
>>>>>
>>>>>KISS
>>>>>
>>>>>(Keep it simple, stupid.)
>>>>
>>>> I can confirm that m4 is sometimes just the best solution for
>>>> a problem. To generate ciforth's I use m4 to massage assembler
>>>> files.
>>>
>>>Sure, but if your Forth was written in Forth you wouldn't have to do
>>>any of this stuff.
>>
>> A fair comparison would be to require that the result is a windows
>> executable, and the Forth code is acceptable to 4 Forth compilers on
>> Windows.
>> Then I definitely need a whole slew of m4 code.
>
>I don't really understand why this is a goal.  If your Forth could
>build itself, why would you want to build it on some other Forth?  I
>dont think I've ever heard of a Forth in Forth that builds itself on
>*any* Forth.

It was pretty easy to port ciforth to OSX. You would magically assume
that you already have your Forth on OSX in order to bootstrap it.
If you OTOH cross build the OSX Forth on a working MS Windows Forth
then you have to study the layout of the executables on OSX.
I use the built in knowledge of the OSX system tools.

No free lunch here.

>
>Andrew.

Groetjes Albert

--
-- 
Albert van der Horst, UTRECHT,THE NETHERLANDS
Economic growth -- being exponential -- ultimately falters.
albert@spe&ar&c.xs4all.nl &=n http://home.hccnet.nl/a.w.m.van.der.horst

Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

csiph-web