Re: Parsing timestamps?

Mr. Fifo - self-proclaimed "Mark Twain of Forth"
- has no idea, that writing Forth code doesn't
mean to move bytes around "Back and Forth"
(where did I see that? Let's see... :D ).
>
Stack jugglery means wasting CPU cycles for
moving the bytes around - it's contrproductive.
Variables have been invented to be used. They're
useful, if you didn't notice, or if they didn't
tell you that in your college, or wherever.

>
Have you looked at my Roman digits?
There are two stack words DUP used in whole, meaning that you
use a stack item twice.
That is in a word `_row that isn't even essential to the whole
exercise.
The stack shuffling is probably a sign of bad code.

>
Well, that's exactly the point. If you can't write Forth, you'll end up
juggling stuff around - and yes, that results in unmaintainable Forth.

Like this example:
: timescan
   over swap chars + >r 0 tuck begin
     over r@ <
   while
     over c@ [char] : =
     if rot + 60 * swap 0 else 10 * over c@ [char] 0 - + then
     swap char+ swap
   repeat r> drop nip +
;
15 "byte shufflers" within single word,
and even 8 of them within a loop(!). So
byte threshing over and over again.
--