>. The main challenge would be to translate (iirc) LOAD <block#> to
something compatible with your new loader. The

> first thing that occurred to me is to write each block to a separate
file using a naming convention that includes the

> block number, then write a LOAD word that uses that naming convention.

Many years ago I solved this problem by temporarily redefining LOAD to
do a listing that would go to a file. It would start listing each
screen by putting in a comment with the screen number from which the
screen came so that if necessary one could reconstruct the crime. The
contents of the shadow screen were commented and placed on the line with
the source or tabbed in and interleaved with the source on alternating
lines. THRU and load map blocks would all function predictably. Along
with LOAD, the obvious solution needed to be implemented for conditional
loads so that the appropriate load file would be generated.

By the way, along with the legacy, modularity and portability I'd like
to add two thoughts about screens. I always liked having shadows that I
could blink to or put up on a second screen. Also, programmers who were
beginning to learn their craft (trade? practice?) would find that
they needed to trim their idea to fit into 16 x 64 and I like to think
it must have helped some. Of course in the old PolyForth source there
was at least one idea that was left on the stack and picked up a few
screens later.

________________________________

From: swiftx-bounce_at_forth.com [mailto:swiftx-bounce_at_forth.com] On Behalf
Of Wil Blake
Sent: Wednesday, February 11, 2009 7:27 AM
To: swiftx_at_forth.com
Subject: [swiftx] Re: PolyFORTH 8086 L3

Hello,

I checked a Forth Dimensions article reference and articles "Toward
Eliminating Forth Screens" 7-3(p7)
<http://www.forth.org/fd/FD-V07N3.pdf> and "Screenless Forth" 8-5(p13)
<http://www.forth.org/fd/FD-V08N5.pdf> described file loaders for F-83.
I would guess that similar articles may apply to PolyForth- I just
cannot find them.
Apparently several Forth Dimensions letters debated the merit of screens
versus files, and I remain old enough to recall spirited discussions on
the issue. Developers loyal to specific (usually multiple programming
language, syntax directed) editors preferred the ability to work with
text files while developers working exclusively in Forth and Forth
Assembler preferred the legacy, modularity, and portability of screens..
-Wil Blake

On 2/11/2009 9:32 AM, Nigel Bond wrote:

Hi Howard,

Thanks for the reply.

Bizarrely I'm migrating BACK to PF8086 for an 8051 project that uses
chipFORTH (Forerunner of SwiftX, runs under PF8086)

I'd like to have new code in an ASCII file.

I'll roll up my sleeves and write an ascii file loader.

Many Thanks & Best Regards

Nije

        -----Original Message-----
        From: swiftx-bounce_at_forth.com [mailto:swiftx-bounce_at_forth.com]On
Behalf Of Howard Lee Harkness
        Sent: 09 February 2009 12:38
        To: swiftx_at_forth.com
        Subject: [swiftx] Re: PolyFORTH 8086 L3

        When I first used PolyForth 86, back in the 80's, one of the
first things I did was write an ASCII file loader, for which many of my
fellow Forthers chided me, but it made things significantly easier in
several ways. For starters, it was easier to make backups, transfer code
from one machine to another, and use the old PolyTron VCS code/version
management tools. Plus, I didn't have to teach a strange new editor to
the technicians who had to modify the data tables -- they could use the
DOS editor they already knew.

        I would not expect it to be any more difficult to write a tool
that would translate blocks to ASCII files. The main challenge would be
to translate (iirc) LOAD <block#> to something compatible with your new
loader. The first thing that occurred to me is to write each block to a
separate file using a naming convention that includes the block number,
then write a LOAD word that uses that naming convention.

        e.g., LOAD 23 would load a file "23.4th", or something similar.
Or, since an extension isn't really needed, the file could simply be
"24".

        I would not expect that to take more than a day or two to write.

        Happy Forthing! I have to admit a bit of jealousy, since the
last Forth I got to write for a living was a few years ago, for GE in
Longview, TX. Except for a timing error in my personal life, I might
still be there; it was one of the most enjoyable jobs I ever had.
Nowadays, I'm programming in C++, and consider myself extremely
fortunate to have a job at all in the current economy.

        On Mon, Feb 9, 2009 at 4:03 AM, Nigel Bond <nigel_at_techwiz.co.uk>
wrote:

        Hi,

        When migrating to SwiftX I was convinced I would miss blocks. I
did not.

        I'm now needed to get back into pF8086 L3 and I'm wondering ....

        Has anyone got any code/suggestions for loading text source
files in pF8086?
        (Running in DOS, or DOS under W95/98/ME)

        Is anyone old enough to know what I'm talking about?

        Any comments most appreciated.

        Nigel Bond
        Engineer
        TIC Irrigation Controls Ltd.
        Devon. UK.

----------------------------------------------------------------------
        swiftx_at_forth.com The SwiftX programming discussion
email list
        To unsubscribe, send subject "unsubscribe" to
swiftx-request_at_forth.com
        For list command help, send subject "help" to
swiftx-request_at_forth.com
        Message archives are located at
http://www.forth.com/archive/swiftx

----------------------------------------------------------------------
        This list is a forum for SwiftX users. For product support and
bug
        reports, please send email to support_at_forth.com

----------------------------------------------------------------------

        --
        Howard Lee Harkness
        Pro-Count, Inc.
        214 269-1171

----------------------------------------------------------------------
swiftx_at_forth.com The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe" to swiftx-request_at_forth.com
For list command help, send subject "help" to swiftx-request_at_forth.com
Message archives are located at http://www.forth.com/archive/swiftx
----------------------------------------------------------------------
This list is a forum for SwiftX users. For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Wed Feb 11 2009 - 14:55:32 PST