2024-12-19 00:59:59 <xentrac     > 
ACTION is stupid enough to need an atlas

2024-12-19 01:46:01 <KipIngram   > I bet atlas publishers HATE Google Earth.
2024-12-19 01:47:27 <thrig       > atlas shrugged
2024-12-19 01:49:40 <xentrac     > Google Maps, the one weird trick
2024-12-19 14:55:30 <pgimeno     > by the way, in the end what I did for the Juppy to get a <> operator was: : <> XOR ;
2024-12-19 14:58:25 <veltas      > That doesn't work
2024-12-19 14:58:53 <veltas      > Unless you're just comparing flag values
2024-12-19 15:00:09 <veltas      > : <> = 0= ;
2024-12-19 15:02:33 <veltas      > And  : 0= IF 0 ELSE -1 THEN ;  : = - 0= ;  if you need it
2024-12-19 15:10:51 <zelgomer    > why doesn't it work?
2024-12-19 15:11:16 <zelgomer    > i feel dumb for asking but i'm struggling to think of an example where it breaks
2024-12-19 15:15:56 <xentrac     > : <> xor ; seems okay to me if you only care about the truthiness of the return value. the case where it starts having problems is where you do something like dup 3 <> 4 <> or
2024-12-19 15:16:17 <xentrac     > because AFAIK no standard Forth has ||, just |
2024-12-19 15:21:04 <zelgomer    > oh yeah
2024-12-19 15:21:34 <zelgomer    > it's too early here for this
2024-12-19 15:26:49 <veltas      > Yeah it's just concern about retaining the right 'true' value or 1 or -1
2024-12-19 15:26:56 <veltas      > of* 1
2024-12-19 15:30:54 <pgimeno     > xentrac: you have a point, but actually with or it works, it breaks with and
2024-12-19 15:31:52 <pgimeno     > something like: dup 3 <> over 4 <> and wouldn't work as expected
2024-12-19 15:38:42 <xentrac     > oh, doh, thanks for the correction
2024-12-19 21:06:29 <GreaseMonkey> oh right that 0= definition should come in handy
2024-12-19 21:06:47 <GreaseMonkey> i somehow have if/else/then implemented
2024-12-19 21:19:18 <zelgomer    > "somehow" ?
2024-12-19 23:26:30 <zelgomer    > forth-standard.org is down again. forth is cancelled this year.
2024-12-19 23:27:46 <zelgomer    > can someone just remind me -- i've never actually bothered to implement a proper quit and abort. which one is supposed to clear the parameter stack and which one is supposed to clear the return stack?
2024-12-19 23:28:00 <zelgomer    > i imagine abort clears the return
2024-12-19 23:32:04 <zelgomer    > ok the forth-79 doc i have says quit clears the return stack and abort clears both (presumably a side effect of also calling quit)
2024-12-19 23:32:16 <zelgomer    > this makes more sense, quit should never have anywhere to return to
2024-12-19 23:36:46 <zelgomer    > it works. incredible.