Відео

I wish I had this ~40 years ago, but I didn't even have a drive and this would probably take weeks to do with tapes =)

I've been waiting for this one. Excellent video and presentation, as always! A quick story. I had a C128 and then an Amiga 500 back in the day. I got myself the Manx Aztec C compiler for the Amiga and was heavy into learning C. I was in the 8th grade then. I went to my friend's house and he showed me one of his new computer magazines that had a review of C64 C compilers. I read the article and couldn't believe my eyes that the compilation times were on the order of 45 MINUTES! I had to read it twice to make sure I didn't misunderstand something. Fast forward to around 2006 when I start using a C64 emulator for my Mac. I found some disk images online for a C64 C compiler (I don't remember which one) and decide to try it out remembering the crazy compilation times. Sure enough, it was around 45 minutes! I've written several compilers, including two C compilers (one using lex-yacc, the other, a fully hand coded lexical analyzer, recursive descent parser). I've often wondered where it's spending its time. After watching this video, I suspect Super C has organized its I/O operations much more efficiently than whatever the other compiler has.

Pretty cool. I could have gotten a head-start on my programming career if I had known about this (and had known what C was.) Good that the pointers are 16-bit. But without malloc() you're only going to be able to get so far...

Data Becker was one of the largest publisher for computer books in Germany back im the days. And the starting screen is colored as the German flag: 🇩🇪😁 Old memories ….

I got a copy of that C manual at home. And the discs should be somewhere too. :-) And I do mean a copy.. discs was copies too.. but they was coppied back in the day.. maybe around 1990. So thats all forgotten.

Every video I watch makes me say "I wish I had seen this 30 years ago."

cumbersome but functional with interesting nuances and abilities.

This is excellent! Love it. You'd think C would be the native language of a Commodore 64 since C is the first letter in it

I'd like to see some benchmarks of the code produced by this compiler vs Commodore BASIC code. The compiled code should be faster but I'd like to see some proof.

Thanks for this video - I always wanted to try Super C on the C64, but I just found it too confusing and difficult. Your video is really clear - great work! I would love to see the 128 version, and see how that RAM disk function works - also, to confirm that you can't compile programs to be executed without Super C (that would have been a major limitation back them!), and also to see if it takes advantage of the other video modes on the C128.

Where are you from? I've never heard this pronunciation of "available" ("avable")

I've just seen it by chance. These are memories of my childhood. The programme is from Data Becker. They were based in my home town Düsseldorf. As a child, I wanted to work there when I had grown up. 😂 Thank you very much for that!!

Very cool to see early C development tools and how clunky it was. The unix command line tools and whole shell abstraction was very smart and it really stood the test of time. Wonder how it could look like if we would have BASIC terminals. Anyway, if you looking for ideas I would love to see any 3d related content, whether it would be some legacy software, games or maybe writing program displaying cube.

Would love to explore this a bit more

Do you know if Super-C come with a library that support lightweight threads? How about fork()?

I like the editor, and the tiny shell for commanding the environment. Its defiantly worth a DL and try with the emulator.

I am not sure why the UI gives me vibes of Textomat Plus (I never found out what it actually was and how to use it)

This is superb stuff. Would be nice if there are some hacks providing REU use. Please do Laser BASIC and White Lightning (Forth), by Ocean/Oasis.

Thanks for a great review of this product. Do you have any experience with Blazin Forth?

Wow! It's unbelievable what the developers could do with 64K.

“Glacial” I love it. I use several CPU and drive access pigs. When using these, I nearly always run Vice on my M2. It has more than enough oomph to run them @ 800-1000X. Makes for far faster coding breaks, and much faster getting back to what broke your code this time. In one machine I have the capabilities that would have cost countless thousands back in the day. Don’t code much this time of year, but love seeing your new content. Thanks

This is very interesting and I love the C64 but I'm also very happy that programming is not that complicated today.

Looks really interesting. I need to get my 1541's working.

You would need several thousand dollars for a C-compiler that did this back in the mid-1980s. How times have changed.

The developers have engineered a masterpiece, squeezing every drop of performance out of the available hardware. I played with GEOS for a short time before switching over to the Amiga1000.

How I wish these kinds of video tutorials were available when I tried to program in the 1980s.

Absolutely amazing video… newish subscriber here, but this is awesome!! Much love from 🇬🇧

Love the archeology and shocked that they actually included all of that code with the mouse. Different times, back then. I thought you were going to remove all of the JMPs and JSRs and use all relative branching such that it is loadable anywhere, so I can only give you a 9.5 (out of 10). Just kidding, your channel is awesome, thank you!

Brilliant video through which, I dived back into those C64's BASIC instructions that you handle very well, but I almost forgot. If I could double-click on the like button, I would do it. Sadly UA-cam prevents this!

Cool video, thanks.

Why are there so many C64 programs that start at 32768 or 49152 instead of just barely past all BASIC space? What if someone chose 3000 or 4000 even? I understand that 32768 and 49152 are ^2s. But's so significant about them that they're popular starting points? For example, LodeRunner starts at 679(dec.). How does a programmer decide to start at that location instead of anywhere else, even though that's not a ^2?

Why was the 1351 source code on that disk messy and in 80-column mode when the 64 doesn't have 80-column mode except virtually in BASIC lines, and why can't TMP just handle those as-is if those were already made for the 64?

"So we're gonna read that value of the button out of memory." Huh, that's weird. Why would we want our reading to be destructive?

So why start the program out with numbers that you don't like and then change them, instead of just starting it out with numbers that you do like?

"It goes behind the border," haha! Interesting that there are even location-related memory locations "back there" I always thought that in order to have border space for things to "go behind" on this machine, we had to turn on border widening (enable scrolling to have a cut-off look or just be more functional in general).

"So now lets put into place some code to make an _actual_ program." You just did already.

Ha, how do you make sure your save "@..." doesn't create a splat file if you were to be using real Commodore hardware instead of the VICE? FFR, I recommend not teaching people "@" in case they use the real deal; have them scratch and save instead.

Why start this BASIC program with 50K, and then why start the ML program at a point right above BASIC instead of starting it a lot farther away in the first place?

After over 4 decades, want an idea of how to save a little effort with this stuff now? Try not adding a space wherever spaces aren't necessary, such as right after a line number and a command.

"...With the GEOS operating system..." * "...With GEOS." * "...With the Graphics Environment Operating System."

Good video! I had this mouse on my C64.

Great video again. Thank you.

Very good presentation. Its also a ground for doing the application part in assembly, which is my cup of tea. That would make it a one-file deal.

how does this mouse technically / logically work? is it too much to ask for a rundown of the assembler source code ?

I stared at the book and the screen for hours trying to do assembly programming as an 8 year old. I wish I could have seen this 40 years ago.

You can’t thank US enough for watching these videos?!? I can’t thank you enough for making them!

It that one identical to the Amiga mouse?

Your content is brilliant and also your way of delivering it! Thank you very much for taking time to upload these videos. I for one really appreciate it. PS stick to Laser Genius - that's my favourite ;)

You are very knowledgeable

You are very knowledgeable.