So quiet in here?

[Jobbo]

It's very quiet in here these days.


Did all the interesting and insightful old school coding conversations move somewhere else?


Or did everyone stop when they could start leaving the house again?

[ross]

We have all converted to consistent languages.
A famous research institute told us this and we comply.

ASM seriously damages your brain.
It also makes your wiener shrink and falls off at some point.

[Jobbo]

In fairness some other threads might suggest the brain damage is very real!

[TCD]

So glad you mentioned it

[DanScott]

I've not directly written a line of Amiga code for about 2 years

[Karlos]

I don't know about quiet, but today it's definitely been laggy.

[arcanist]

This sub-forum always seemed a bit odd to me. You can quite reasonably do hardware programming in C. And system programming in assembly.

Learning the language, hardware, and operating system are entirely unrelated activities. And then we get to algorithms, which have nothing to do with any of those!

[freehand]

Originally Posted by Jobbo

It's very quiet in here these days.


Did all the interesting and insightful old school coding conversations move somewhere else?


Or did everyone stop when they could start leaving the house again?

Didn't you know ? Thomas Richter is trying to covert everyone to program in c and all todays & previous code ever written in assembler is junk.

It's rather sad to read his constant drivel day after day.

[Jobbo]

Oh no you don't!! Don't bring that stuff in here!!

I write my A500 stuff in C++ (with templates even!) and also assembler. So let that melt your brains. It's almost like you can actually do both!!

Disclaimer: My C++ is C with only sensible additions.

[Thorham]

Originally Posted by freehand

Thomas Richter is trying to covert everyone to program in c

How pedestrian. C# is much better.

[dmacoco]

"C# is much better"

I haven't coded since 30 years on my amiga.
I used C and 68k. What is the best solution to code in ASM today ?
- on an amiga with hd solution
- on my pc

[TCD]

Originally Posted by Karlos

I don't know about quiet, but today it's definitely been laggy.

Noticed that too yesterday (Anubis confirmed it) and reported it. Should be better today.

[meynaf]

Originally Posted by arcanist

You can quite reasonably do hardware programming in C.

No, no, don't do that. You must use the OS for absolutely everything.

Originally Posted by freehand

It's rather sad to read his constant drivel day after day.

It is even more sad attempting to reply.
And unfortunately he's not alone.

[hooverphonique]

Originally Posted by Jobbo

Oh no you don't!! Don't bring that stuff in here!

[Karlos]

Originally Posted by TCD

Noticed that too yesterday (Anubis confirmed it) and reported it. Should be better today.

It does seems snappier today.

[Karlos]

Originally Posted by Jobbo

Oh no you don't!! Don't bring that stuff in here!!

I write my A500 stuff in C++ (with templates even!) and also assembler. So let that melt your brains. It's almost like you can actually do both!!

I mean, who would've thought? As for templating, it's more useful than ever today, allowing you to replace things that needed gnarly function like macros to guide conditional compilation in days of yore.

Assembler is still relevant on 68K today though - I just wouldn't necessarily write an entire application in it, unless size was critically important.

[Jobbo]

What have I done! There’s two now!

[Bren McGuire]

everyone is too focused on fighting about whether it makes sense to code on assembler or what could have happened if commodore actually put a man on the moon had david pleasance's buyout went through thanks to the AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA chipset

[Quagliarulo]

I wish there was much more traffic in this subforum as well. I come straight here everytime I visit EAB.

Originally Posted by Jobbo

My C++ is C with only sensible additions.

Which ones?

[Jobbo]

Originally Posted by Quagliarulo

Which ones?

Not that much as it turns out:

- const all the things
- constexpr/inlines/templates where possible instead of defines
- template functions in some specific cases where the variants use different consts
- references rather than pointers
- enum classes for better type checking

Most of the code is otherwise very procedural.

I did use a class and operators to build a type that uses the rom FFP stuff, that's mostly useless because the FFP code is so slow, but it was interested to play with for testing out ideas.

I did make a class for a physics body to combine the state and the operations, but it might as well have been a struct and functions.

I'm using less than I thought tbh.