00:47 <cmtptr> make me!

00:56 <tabemann_> hey guys

01:07 <john_cephalopoda> Hey tabemann

01:41 <veltas> Found this interesting https://www.youtube.com/watch?v=BpgmG--UD-Y

01:45 <veltas> badcfe: The standard has two kinds of words, words that are generally expected to appear on all conventional forths, and words that try to wrap behaviour that's less consistent but still generally desired

01:45 <veltas> If you read the rationale you will get some idea usually of which the word is

01:45 <veltas> So why a standard might be useful to you will obviously impact whether you care about which each kind of word is

01:51 <veltas> I don't think anyone should dismiss the standard outright, I think there's a lot of usefulness in there. At the same time I wouldn't approve of any zealotry over the standard, but I don't tend to see that.

01:54 <veltas> As an implementor, if you create a forth that is even superficially compatible with another forth, then it means you can test your code easier on different environments

01:54 <veltas> One way to do that is to stick close to the standard and use a mostly standard-compliant forth

01:55 <veltas> Not always practical, other ways to do this, but you get the idea. It depends on your problem

18:46 <lispmacs> hi, I was wondering how to check for integer overflow, specifically during a multiplication operation. seems like this is not built into forth. Is there some way to check the flag on x86?

18:50 <lispmacs> or some other way this problem is dealt with?

18:54 <lispmacs> maybe FLAGS register can be accessed in some way...

18:55 <cmtptr> you're asking about ans, i would expect them not to expose platform-specific registers

19:03 <cmtptr> s/you're/if you're/

19:12 <lispmacs> looks like gforth has a bunch of register related words defined. Maybe they are documented in the source

19:39 <MrMobius> lispmacs, is it too big to fit in a double?

19:40 <lispmacs> MrMobius: as far as a specific problem: I was doing the Forth Application Techniques problem where you have to create a class ( using : <name> create ) for a 2array

19:41 <lispmacs> user passes in number of rows and columns

19:42 <lispmacs> instance behavior is to take in a row and col number and return the address of that array element

19:43 <lispmacs> anyway, the definition behavior involves multipling the row and col to figure out how much to allot, so just had me wondering how one could check for multiplication overflow/carry

19:59 <MrMobius> maybe there's a cleverer way but I would promote to double and compare

20:09 <veltas> lispmacs: This is something that almost all programming languages are painfully lacking in, standard forth included

20:09 <veltas> Regarding integer flags

20:10 <veltas> It's weird when you find there is something easier to do in assembly, but most clever uses of arithmetic or extensions of arithmetic seem to be easier in assembly

20:11 <veltas> In my forth I am meaning to add integer flag support, it will probably simplify certain e.g. double/mixed colon definitions

20:15 <TangentDelta> Heh...

20:16 <TangentDelta> My brain always goes straight to trying to solve problems with clever arithmetic and logical functions, which is quite bulky and annoying on modern programming languages.