Dear AmForthers,
I tend to disagree on some of this ...
What you argue for is a "architecture and project-specific"
"reduced" refcard. At least this is, what I understand.
I have used the refcard extensively in the beginnings of my
AmForth journey. And I would argue any time, that the refcard
Hello Tristan, Erich and AmForthers around the world.
Tristan, I really like the direction you have gone in. Coupling the build
process with the local refcard really is a solution that I can put my
support behind. When push comes to shove what really matters to the end
user? The words that have be
Hello Mark, Erich, AmForthers,
I made some more modifications to the perl reference card script so
that it will write out an AVR8 build specific reference card in
html. Below are example outputs for the stock UNO build and
a custom build
https://tjnw.co.uk//amforth-6.92/appl/arduino/uno.html
http
Hello Mark, Erich, AmForthers,
Yes, I completely agree the format of my refcard excerpt has some
issues. I just wanted to show that, with the hard work done by the
perl script, all of the documentation data fields for AVR8 built-in
words with compliant doc headers are readily available for
output
Hello Tristan, Erich and fellow lurking AmForthers (I really do like this
intro Tristan) :)
It really does seem that you may have caught the tiger by the tail Tristan.
For better or for worse even!
For the better (hey, you caught the tiger) :
I think your layout really goes a long way toward docu
Hello Mark, Erich, AmForthers,
I agreed with Mark's comment below
>> It seems that the intent of the refcard was to document the things that
>> are compiled into the system.
and commented
> For me, the scope of the/each refcard is defined by the
> distribution build for each architecture (AV
Hello Mark, Erich, AmForthers,
Mark - I have chopped and reordered selected parts of your message to
form my reply. I hope this is OK.
> It seems that the intent of the refcard was to document the things that
> are compiled into the system.
+1
For me, the scope of the/each refcard is defined by
On Sat, Aug 1, 2020 at 10:50 PM Erich Wälde wrote:
> thread hijacked intentionally.
>
'Thar be pirates!
>
> today I spent some time trying to understand the "make-refcard*"
> scripts in some detail.
>
> The script works roughly like this:
>
>
> - the first three lines are comments expected to
thread hijacked intentionally.
Hello Mark,
dear AmForthers,
today I spent some time trying to understand the "make-refcard*"
scripts in some detail.
The script works roughly like this:
- it reads the .asm files in "one" "hard coded" directory
("../common/words").
- for every file the functio
