I'll think about it. I haven't done Pascal in ages, so this would require some preparation, as the only Pascal compiler I own is the one that came with MPW, and I never really used it at the time. I basically started on the Mac using C, reading documentation in Pascal.

To add to this, for anyone watching: Look up ASTs (abstract syntax trees) which is a tree-like structure that organizes the grammars for the language you are writing. As OP wrote in the video under enums, grammars can include identifiers (variables, functions, etc.), operators, int literals, etc. To implement an AST, Djikstra's Shunting Yard Algorithm makes use of stacks to implement a tree-like structure. This, in turn, can be extremely useful when you want your program to correctly process expressions that may utilize order of operations (ex. 1+2*4 vs (1+2)*4). It arranges everything in Reverse Polish notation for analysis.

Regexes work, but are a bit much just for analyzing character classes, and can't be used for full-on parsing, as they don't handle nested constructs like parentheses. You'd also want some sort of "streaming" regex parser to not have to get all regexes matched first, and then create objects from them. But my main reason was that I didn't want to use external dependencies like a regex parser library that viewers might not have.

The original Mac in '84 used Pascal, but they pretty quickly started supporting C in the late 80ies, and by the mid-90ies, C++ was what most apps were written in. Most used existing frameworks like PowerPlant and TCL, or small indie frameworks like MacZoop instead of hand-rolling their own though.

Glad you like the videos!

@@mastersofthevoid tx, I am in session 6, I was very much curious to know how bytecode can be generated in assembly direct from the nodes if u detail.

@@amitdubey9384 You recursively call each operation's arguments in the tree to generate an instruction. A value (like a number) is just a PUSH_IMMEDIATE_INT instruction pushing that number. Once you've pushed both arguments, you generate code for the actual instruction (e.g. ADD_INTS), which pops both of its arguments and pushes the result.

I don't know the exact solution, but you need a version of CodeWarrior that matches your version of MacOS. Also, not all emulators support debugging, so if you're emulating MacOS, trying a different (newer?) version of the emulator might help too.

HyperCard was my absolute favorite thing in the universe when I was 10 or 11.

I've only done a little Python so far, and I'm not sure I'd be qualified to make a video about that. But I think Macstodon (68000 Mac Mastodon client) was written in Python, might be worth checking in with the developer who wrote that.

Metrowerks dropped the ball, were slow to port CW and their frameworks (PowerPlant etc) to OSX and slow to embrace the new platform. ProjectBuilder was pretty awful by comparison but it was free. MW could have remained the premier development envisioned but they just didn’t care.

@@kirishima638 yeah. It’s too bad. They were owning it for a good while.

It probably didn't help that they got bought by Motorola, who then sold the Intel compiler to Borland, so when Apple switched to Intel, they couldn't follow along. CodeWarrior still exists as an embedded compiler for Freescale (fka Motorola's CPU division) CPUs though.

@@mastersofthevoid yes that’s right! Didn’t they also sell the intel compiler right before Apple announced the switch?

It's an archive of a live stream. That's how it went.

They aren't Macs, so I have no idea, sorry.

@@mastersofthevoid Psyq make executable psx files

I don't know for sure, but it could just be a ResEdit-style resource fork containing the PPob resources separately (if it's an app for MacOS X, then probably just moved into the data fork). You'd just need a copy of CodeWarrior. If it's Carbon, you probably need one of the later MacOS X versions of CodeWarrior. These files don't need to be compiled, they are copied into the application's resource fork (or a special Resources file) and used by PowerPlant to know what a window should look like.

@@mastersofthevoid which version of os x should I use? Also which codewarrior version will be good? Thanks for the answer.

@@creeper2671 You need a PowerPC version of macOS (and a machine/emulator to run it under). That's what those versions of CodeWarrior were for. Or at the least an Intel version of MacOS that still supports the Rosetta I PowerPC emulator. Carbon apps may also run on late MacOS 9 releases, so if you already have that, you can try it on there, too.

@@mastersofthevoid I kinda worked

Thanks for the added detail :D

That's a cool idea. I'll keep it in mind.

Amazing! I only knew that some people used the bits of MacOS API that were (sort of secretly) included with QuickTime for Windows, wasn't aware other people re-implemented their own version. Would love to see that code put up on GitHub somewhere :D

@@mastersofthevoid I will do this and send you a link. I don't understand the whole thing but I have the sources and maybe I could learn something as well. It could maybe be improved and would allow old os9 apps to run in windows which would be cool.

Oh yeah, I'm not talking about the file format (I'm aware, I wrote stackimport), I'm talking about the user interface. Most programming languages require you to write code to remember state, so most developers forget a lot of "secondary" state when a document is closed. It feels like someone is constantly re-shuffling your files and icons when compared to the real world, where statefulness is the default and work is required for stuff to move.

Hopefully in the Inside Macintosh books, and Dave Mark's "Learn C on the Macintosh" and stuff like that :D

Yeah, I took a C class in college and trying to do my assignments in CodeWarrior was the hardest part of the class. Always ended up having to go to the lab and redo everything on a PC.

one actually had to study and read books then for knowledge... life before youtube ;)

There is a another video later in this playlist that goes into "if" statements.

Sorry, I just realized, I don't think I ever did "if" statements. An "if" statement is basically the same as the "while" loop in Part 8, just that instead of jumping back up for another loop, you jump down to the start of the "else" statement when the condition _doesn't_ match. And at the end of the "if" section, you need an (un-conditional) jump so you skip the "else" section's statements. The hardest part here is that by the time you write the jump statements, you don't know how far to jump yet. So you need to write out the instruction with a 0 jump offset, remember its address, and once you've written all the code out, you need to replace the 0 jump offset with the actual number of instructions.

They’re working on something cool with AI too.

LiveCode is too much like a programming language. It has forgotten a lot of what made HyperCard unique, IMO.

@@mastersofthevoid I never used hyoercard, so i cannot compare.

Because Apple was going out of business and Steve Jobs shut down every project that wasn't needed to release the iMac and save the company from dying, I guess 😢

@@mastersofthevoid Despite shutting down hypecard being sad, saving of Apple was successful, the Most valuable company in the world.....

Microsoft invested in it because of Office. I think that helped save it. We corporate Evangel Lists with Guy Kawasaki would not let Apple die!

I use SheepShaver.

We might have haunted the same AOL Keyword: HyperCard. 😃

Wikipedia seems to disagree with both of us, in a way :D en.wikipedia.org/wiki/Parameter_(computer_programming)

Mainly, I was there when this stuff was new :D

I'll have to see if I still have a copy of the files. But in general, make sure you build a code resource, set its _resource_ type to XCMD or XFCN (for 68000 or "fat" externals, or xcmd and xfcn for PowerPC-only ones), not the file type, give it the name you want it to be available under in HyperCard. Fat XCMDs build the two architectures separately, then use the "merge" linker to combine them.