danwinslow

Because I am talking about a larger effort, not just about the specific code you are talking about.

Oh of course. Avery can hold his own- I doubt the steady pressure of my steely gaze would have any effect if he didn't want to do so on his own Twas just a suggestion.

Maybe we do....

Do we have the OS dumped out anywhere? Maybe @phaeron would add 1400XL as an Altirra emulation.....

Well, we carefully preserve, archive and organize the software products and games. Why doesn't someone start a similar github - "The Atari Source Code Preservation Project" so to speak. Then people can donate source code to it for items of mainline interest as are being discussed here. Then we don't have to remember if person x has source code y and hope they are still alive.

I think this is correct. And, that's a beautiful system.

It would be unusual to not be able to use GCC. What OS are you on? If you are on windows, you should be able to use MinGW: http://mingw-w64.org/doku.php

When the C code is written correctly, CC65 is a very powerful platform that also allows really good integration with assembly and control over memory layout. By 'correctly' I mean 'not like a usual C program'. See ilmenit's tutorials on this site. You do get some benefits from being 1 step up from bare assembler, but as mentioned it's still going to be pretty technical. It has to be.

I'm not qualified to say, exactly, but I've read in threads here that Atari skimped on components and/or didn't do something right on some models. That and interference from the memory operations, etc. Maybe RF is just inherently noisier and lower quality too, not sure.

the signal from the RF is crappy to start with, at least in my experience with NTSC ataris. You can get converters, I think, but they will just show you the fuzz and lines in the original signals at a much higher resolution.

Wow, that's cool. Amazing. How long does it take to render?

I misunderstood then. Missed the linking *

Not the wiki about bresenhams. The above is what I meant, although I don't see where Sanny mentioned it. I'll take your word for it.

Looks great.

Nice. I recall an old thread about the fastest line drawing algorithm that also had code examples, but I can't find it before my ADHD kicks in.

If TGI is performant enough, that'd sure work.

The TGI support for CC65 isn't the greatest as I recall (although it may have been updated since I last saw it). I can't remember if there's OS support for plot and drawto, but I think not, and that probably wouldn't be the fastest either. I always plotted directly by writing to screen memory, and for drawto I dropped in a fast line algorithm. You can find them in asm or native C with a bit of googling or searching here. *edit* Actually, I think I recall that there are some graphic libraries that other people have done that you could find.

You can always write to screen memory? If I understand your point correctly.

Mad Pascal is probably the closest, although if you mean 'safe' to include no pointers, then not it either. Safety usually costs some amount of either complexity, speed or memory. The 8 bit is so constrained it's usually not worth it. Java can tell you that 'no pointers' by itself does not equal safe. I come from an Ada background, a famously 'safe' language, and programmers generally hated it because of what it wouldn't let you do. It happens to still be my favorite language, but nowadays everybody uses Javascript, which I don't event consider a full language and is so bizarrely unsafe it reminds me of C, although at least C has a coherent syntax. Ah, progress.

Funk - I find your complaining boring. The world is not about you. If you don't like this language, then just don't post. If it's no good, it will die on it's own. Why don't YOU bring this 'fresh wind'? You can do do at least little programs. greeting

i agree.

Me too. 1 for me. Thanks

you don't need to type it all those embedded asm() calls just because you need the variable linkages. You can see C symbols just fine in your .s files, just do the correct externs and .imports. That said, sounds like pps might be on to something.

Nice!

Please don't quit on my opinion - I am often wrong If you are trying to save code space rather than execution time, then yeah maybe it's not needed. But if you want to use your simple_io as a basis to work in a familiar environment or convert something that is written to use those calls, then setting them up to call the CIO handlers won't really add much code, and you can probably reduce the code space used by conio.h functions somewhat by setting up your own, specifically optimized, CIO calls.