@asymetrix

I am also curious about tools, such as linting, PClint, cppcheck, clang reports etc... (I use pclint in Linux with Wine, and am considering their followup pclint-plus)

Beyond such tools, and potential styleguides (Misra, Cert C, JPL, etc), what about the idea of safety-first languages such as Rust?

_________________
All glory to the Hypnotoad!

And more to Hyperion,

What about releasing Driver APIs (DDKs for Driver Development Kits) for all types of hardware things, such USB drivers, etc?

For Graphics drivers, if one was made, how do we get the board/chip details into the pcigraphics.card database? If there an effort to remove that database from this binary compiled file so that new hardware can be added in some more generic way by "outsiders"?

_________________
All glory to the Hypnotoad!

@billt

We need security, we also need consistency in the way we do things, not a relaxed way - that leads just to basic human nature - chaos.

People are chaotic but computers are digital state machines, with fixed timed tasks.

If you don't follow proper rules and standards it effects maintainability, spend hours looking at someone else's ugly looking, poorly structured code will add thousands to the employers bills - and they wont even know.

UNSW has standards in coding / guidelines what they are allowed to use in the C language and also have automated computer systems that MARK and TEST submitted work for compliance - its that serious.

Rust is similar to C with few C++20 specific commands, its newer, more robust systems programming language, but how will it fair in being used as an operating system or services provider depends how its been coded.

I would like to have Rust for Amiga it would be great to try out, its not so popular at the moment and very expensive to train developers - as always its a risk reward system.

I do wish A-Eon provide better technical documentation, Hyperions wiki is a joke, just some code linked together.

Today new developers need full documentation on how the Amiga system works, not just the code but how all the different parts interact.

For example how does one support CUDA / OpenCL ? if someone had the documentation, what parts of the Amiga subsystem needs attention which parts are aware of such technology.

Unfortunately A-EONS motherboards are created using standard components likened to a store bought frozen mozzarella and cheese pizza - nothing fancy, common.

Commodore Amiga is a beautiful Computer Engineering Hardware platform.

The custom chips created a graphical & musical playground that is still unmatched today.

Trevor could easily try and find A 68k IP and create a 2+ GHz multi core processor, with help from a kickstarter, same with the custom chips.

When porting apps developers always forget about the architecture of the target hardware - are they using the memory correctly, maybe a re-code of the algorithm would be better on this hardware technology.

Today we are like builders mixing our own cement and carving our windows by chopping down trees with a knife.

Then trying to get ready made windows (pc/Linux software) chopping it to size with an axe to fit our crumbling homes. Only to find the wrong materials / sizes were used in the original window and major rework is required. Its a DIY job, it takes longer but we have to eat right ?

Sorry - I got diverted.

_________________
Download 499.26 Mbps, 659.94 Mbps Upload :)

A late to the game question, but others have not been answered so homefully this tread will get some new attention to those as well...

After watching the ExecSG presentation, I'm curious about if pthreads or other mass-use threadng mechanisms will be supported at some point, at least for "new" software. If I remember correctly, the forbid/permit things may have been a problem, but perhaps I remember something wrong about the threading issues. Ald the lack of fork and join had been issues for porting, is there opportunity to build those sorts of things in at this point, to make new ports easier?

_________________
All glory to the Hypnotoad!