IRC Log - 2025-12-17 - ##forth

Channel: ##forth
Total messages: 31
Time range: 15:28:41 - 21:01:46
Most active: DKordic (13), ghodawalaaman_ (10), crc (4)
15:28:41 ##forth <ghodawalaaman_> Hello o/
15:38:01 ##forth <ghodawalaaman_> https://programming.dev/post/42507593
15:38:11 ##forth <ghodawalaaman_> failed attempt to create a forth compiler in c#
15:38:13 ##forth <ghodawalaaman_> :(
16:01:13 ##forth <DKordic> ghodawalaaman_: ``A failure to plan is a plan for failure. ''
16:01:32 ##forth <DKordic> Where is your problem statement?
16:02:31 ##forth <DKordic> Not even you know what should be done.
16:03:03 ##forth <ghodawalaaman_> DKordic: the problem is that I don't know how to parse it properly, I have done it so far but don't know if it's enough
16:04:29 ##forth <DKordic> Look up ""parse"" in (English) dictionary. I guess it is not your mother's tongue. Perhaps even better, a formalism... of a _formal langauge_!?
16:05:09 ##forth <ghodawalaaman_> yeah English is not my mother tongue
16:06:24 ##forth * DKordic .oO(Have anybody ever said C is a formal language? Liek PC is a computer... Android even less so. Cantor's Theorem... )
16:07:23 ##forth <ghodawalaaman_> okay I will try to explain where I am stuck. I parsed(tokenized/lexical analysis) almost everything but don't know to tokenize loops
16:07:41 ##forth <ghodawalaaman_> and other than that there is not syntax error checking in my code
16:10:40 ##forth <DKordic> That is why Forth is interesting. At least IMO. I don't give a sh.it about ""Operating System"" (UNIX), ""parsing"", ""compiler"", ""linker"", ""type""(( system )s).
16:11:03 ##forth <DKordic> It can be any programming language as lng as it's C!?
16:11:32 ##forth <DKordic> ghodawalaaman_: So, WTF is ""parsing""?
16:11:42 ##forth <ghodawalaaman_> tokenizing?
16:11:52 ##forth <ghodawalaaman_> lexical anlysis?
16:16:32 ##forth <DKordic> The world is not as simple as you (and your masters) can possibly decree.
16:56:51 ##forth <crc> forth parsing is mostly just separating on whitespace. (excluding things like s" or : which parse ahead in the input stream)
18:21:56 ##forth <jackdaniel> what about numbers?
18:22:48 ##forth <jackdaniel> (or strings)
18:25:31 ##forth <crc> strings are built up using words like s" which parse ahead in the input stream, numbers typically get checked if the input token isn't a word in the dictionary
18:28:39 ##forth <crc> things like definitions, loops, and conditionals are also implemented by words, not a predefined set of structures
19:06:53 ##forth <DKordic> AFAICU ""Form and Content in Computer Science"" (https://web.media.mit.edu/~minsky/papers/TuringLecture/TuringLecture.html) is relevant.
19:13:35 ##forth <DKordic> The essence of SyntaxError is inappropriate application of relevant Constructors.
19:15:20 ##forth <DKordic> I got SyntaxErro in both Haskell and Python for reasonable expressions. That is why I don't care much about them.
19:17:34 ##forth <DKordic> Effort put into ""C Type System"" is like M$ Word. A one-way street.
21:01:40 ##forth <KipIngram> This isn't Forth, but I can't resist sharing, because it's pretty much the first time I've EVER seen anyone get the material covered as RIGHT as he gets it. So many sacred cows slain...
21:01:46 ##forth <KipIngram> https://www.youtube.com/watch?v=XcY3ZtgYis0