Jump to content
Have You Played Atari Today?
2600|5200|7800|Lynx|Jaguar|Forums|Store

danwinslow

Members
 View Profile  See their activity

  • Posts

    3,023

  • Joined

  • Last visited

 Content Type 

Everything posted by danwinslow

  1. danwinslow
    I wrote a few simple games in Valforth on the Atari. One of my thoughts about Forth is that it's not really a 'language to write a program in'. It's more of an 'engine to define a language to write a program in'. In essence, it's kind of like using assembler - you build all of your own language constructs. If you do it in an haphazard, informal way, you'll probably hit a wall at a certain level of complexity. That's why you need to define your words in a consistent, highly factored, loosely coupled way...just like language designers do when designing a language.
  2. danwinslow
    From what I can tell, I think it's best to just help him along as we can, and not worry about whether he's doing something particularly productive or effective. That's just my 2 cents on the matter. What he's doing sounds duplicative to the em driver to me, but who cares. Harry - "Extra" memory- 1. Under the OS. Only on certain machines. This is just part of the 64k RAM address space. 2. Banked (or extended) RAM. This is any one of a variety of memory expansions, including the 130XE. 16K blocks mapped into $4000 by fiddling with PORTB. Axlon might be different, not sure, but same idea. 3. Unused memory. Regular RAM locations that are unused under certain circumstances. Printer buffer, cassette buffer, various FP bits and pieces, some ZP locations, etc., even under the stack if you are adventurous. Well documented over the years, but subject to a lot of variability depending on machine config.
  3. danwinslow
    I'm not equating everyone here with my preferences...this might be a language (human, not meta) problem, but I think I understand what you mean. I clearly stated it was my own opinion. I think it's quite presumptuous of you to wave your hand and refer to criticism as 'grave misconceptions'. What were the grave misconceptions you refer to? You seem to think that any negativity or criticism results from us just not understanding things correctly, and when you have time to 'explain' then we will all see that you are right. That more than anything else is what has turned me off from this discussion. I see you started another thread, I think that's probably a good idea because there were some kind of rude posts, which if you'll recall, I spoke against. Good luck with your project.
  4. danwinslow
    Harry - Action doesn't need 'support'. If you want to learn it to use it, then great. Read the docs and write code. No one needs a 'template creator', it's just not useful.
  5. danwinslow
    Yknow, Kaj, taking criticism as "grave misconception" is not helpful to your argument. These guys know their stuff. If one disagrees with you, well...fine, that happens a lot. If two do, then hmmm ok but still. If nearly everyone is saying the same thing - you're probably wrong. You like REBOL, I get it. To me, it's a bizarre language that as far as I can tell never got much traction, but OK, maybe be I'm wrong. Do your thing, I appreciate the effort and skill it takes. But don't expect people to actually use it for much, this is entirely the wrong target market.
  6. danwinslow
    Some kind of numeric over/under flow I would guess.
  7. danwinslow
    NTSC Looks like there's a composite out and a DIN. I need to read up. Back later.
  8. danwinslow
    Yeah, I had too. Got the manual off of it, but was wondering if anyone had done any LCD hookups. I assume a composite converter of some sort might work.
  9. danwinslow
    Any advice on getting one of these hooked up to a modern monitor via s-video or some kind of converter?
  10. danwinslow
    C'mon now. It's his thread and his pet project. No need to get sassy, he's been perfectly polite to all questions and criticisms.
  11. danwinslow
    Just to be clear, my post was an attempt at a wordplay joke, not an opinion on any preceding posts.
  12. danwinslow
    Yes, indeed. Dealing with perception is difficult, depending on your perspective.
  13. danwinslow
    Um, neither projection is 'real'. The FA one does not respect some points of proper perspective handling. The FA one is more like moving sideways rather than actually turning. Not a huge deal to me, but it's there.
  14. danwinslow
    Just me, but I don't think you should worry about the 64k limit. You've done this - it's amazing. Grab another 64k and go nuts for V2.0. The user base nowadays is pretty upgraded, and there's always altirra.
  15. danwinslow
    Ok....well, you said "it needs many different, highly complex and hard to handle existing C toolchains". That was what I was talking about. If you got it covered design-wise already,, great.
  16. danwinslow
    Well, if its a temporary situation, that's understandable. Your desire to cover many toolchains will keep you busy for a long time. Consider an adapter layer, something like maybe what LLVM does, meaning a universal intermediate compilation that then gets run through a particular adapter that would then express the correct source and drive the toolchain.
  17. danwinslow
    Well, I do of course, but I don't want to have to just to write programs. My opinion.
  18. danwinslow
    Kaj - I think a good project would be to do the benchmark suite as found in, for instance, the MAD Pascal thread, and show results and source codes. That would kill 2 objectives with 1 effort. If you want to get real traction for your language here that would be a step towards it. I would not expect someone else to take that on...you never know but when you get things finished to your liking I think that would be a logical next step. We are not as interested in the niceties of language constructs and flexibility as we would be in actual performance and accompanying source.
  19. danwinslow
    Wow, looks GREAT. Thanks!
  20. danwinslow
    Rust is a traditional language. It has some relatively novel heap-ownership mechanisms that help safety, and it's pretty fast.
  21. danwinslow
    Philosophically, it kind of reminds me of FORTH in a way, it's a tool for creating your own language, essentially, thus the name Meta, I think. Cool if you are interested in playing around with language constructs, but I'm still not sure of applicability in our world, which is dominated by tight RAM and speed requirements. Not a shot, Kaj, just my viewpoint so far.
  22. danwinslow
    go to google.com type "atari error codes" into the search box press return read what you find.
  23. danwinslow
    Harry - Again, this is all probably too hard for you. Try something smaller and easier. TGB *just* explained exactly how it works. Read the code he wrote above. Look up each location in Mapping The Atari. Read as much as you can until you understand what the code is doing. Then you will know how any code in any language accesses the RAM under the ROM.
  24. danwinslow
    Bob, I simply gave my opinion. I already know the line is blurred, if that's your point. Faster may not be all that simple, since we've only one accelerator in common usage and it has compatibility problems. Anything anybody wants to do is fine by me, I'm not judging. The point of the thread is that maybe this thing can be adapted to do something cool for the Atari 8 bit world.
  25. danwinslow
    Well, true, and that's the point. I'm more on the conventional side of the argument. If you change too much then you might as well just use a modern machine. I would just like a compatible accelerator that would add some extra speed but not radically change the machine.
AtariAge
Forums
Store
General
Follow AtariAge

Copyright ©1998-2023 AtariAge

×
×
  • Create New...