Very few people prefer assembly language over C or other high level languages. And those that do on the PC, most likely prefer to use x86 assembly over 6502.

The "most people" argument does not work. Progress requires meeting unmet needs.

James Adrian
jim@futurebeacon.com

_________________
Jim Adrian

https://www.futurebeacon.com/jamesadrian.htm

I've never heard of such an animal and at the risk of sounding somewhat myopic, see no reason why anyone would concoct such an animal.

Assembly languages are much too specific to the MPU and the machine in which the MPU runs to make input in assembly language A generate a binary for MPU B to be practical. Compiled languages, such as C and FORTRAN, exist to efface machine differences. If the same approach were practical in assembly language it would have already been done.


That is true—if there is a need. Where is the need for what you are proposing?

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

I think that it might be a personal journey of progress, BDD. Kinda like translating a 38-year old miniature interpreter from the 6800 to the 6502, or building a seven-foot-long model locomotive ... it scratches an itch.

Mike B.

You make a valid point, but I'm not interpreting it that way.

My reply may have been a bit crass. However, I took the "unmet needs" statement, which was preceded by the "The 'most people' argument does not work." retort (I think) to Arlet's comment, as a suggestion that the demand for such software is all around us, and that one of us should start shifting our buns and get it written. I don't think there is a demand for such software—I'm not aware of any such demand, and don't see why someone would attempt to write such software, unless that someone has a need for such software.

If it is indeed a personal journey of progress involved, the individual desiring to progress should take a cue from the individual who is building the seven-foot-long model locomotive. His "unmet needs" are not universal.

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

Hi Jim,
from the responses so far, and from general experience, you might happily conclude that there's no such thing as the wishes of the 6502 community - because there are so many different ways of being a 6502 enthusiast. But ask instead if anyone is interested in the possibility, or is anyone interested in hearing about your thoughts and your progress, and you might well find a small audience for your project. If it's something you want to do, then do it, and please do keep up a conversation about your thoughts and your progress - we can all learn from each other.

Cheers
Ed

BigEd,

Thank you for your encouraging note.

I am in communication privately with those who are interested. There is no question of the technical feasibility or the need, despite the overwhelming popularity or current methods. I have found a large unmet need among professors and hobbyist. Not eveybody wants to devote their life to programming. Perhaps the subject should now migrate to the imagined technical obstacles.

I see a PC screen with a processor status register visible and the instruction set accessible. It is suitable for writing encryption programs and much much more.

Thank you for your help.

Jim Adrian

_________________
Jim Adrian

https://www.futurebeacon.com/jamesadrian.htm

I wonder if Bill Forster's approach is quite close to what you're seeking. He's using a set of macros in C so he can write code like this:

Apart from the use of upper case everywhere, which is of course a personal choice, it looks OK to me. Very like, but not precisely like, assembly code. The C compiler will then take care of producing machine code for the appropriate CPU - which it can even optimise.

(You could probably write more macros to write more structured assembly language if you so chose.)

BigEd,

This is very valuable.

Thank you for your help.

Jim Adrian

_________________
Jim Adrian

https://www.futurebeacon.com/jamesadrian.htm

No, we don't. That diatribe is grumpy as hell. What are you looking for exactly? You may be in private conversations, etc., but at least for me, I'm not exactly sure what you're asking, and it is most definitely a subject I'm into, so why not elaborate just a hair more? The answers in this thread have so far netted zero, and I have offered a library archive.org would be envious of, so why not just unload?

What is it you need?

One idea I've read from computer history books is that there were two tribes who came to microcomputing: those who came from minicomputing and those who came from calculators. These days, there's at least one more tribe, which is those who came from gaming.

From minicomputing, we have people who like an operating system, a filing system, tools.
From calculators, we have people who want to string together simple operations and get some results.
From gaming, we have people who want to move pixels on a screen, and play music or at least get sounds.

(Of course that's an approximation, and we're several generations on from those days.)

Jim's ideas to me seem to have something in common with programming a programmable calculator: something direct, with not too many available operations and not too much extra syntax beyond that.

(When MCM introduced their desktop APL machine, their potential customers were happy to write programs in what is a very direct, but also very terse programming language, using only a one-line display. IBM also sold an APL-only machine, and then a dual-boot APL and Basic machine. It seems that Visicalc put paid to APL, as a much more friendly (but much heavier) solution to array-based calculations.)

_________________
http://WilsonMinesCo.com/ lots of 6502 resources
The "second front page" is http://wilsonminesco.com/links.html .
What's an additional VIA among friends, anyhow?

Yes - instrumentation and control is (another) category of computing - in fact now I think of it I'm sure I read that there were three kinds of manufacturers who first tried to make and sell computers
- calculator companies
- business system companies (punched cards and time clocks)
- instrument making companies (including control systems like autopilots)

For me, it's usually about numbers, but it's always worth appreciating where other people are coming from.

I'll take "Topic" for 200, Alex.

RIght, but I wasn't talking at random: there seems to be a gap between the puzzle Jim is trying to solve, and your efforts to try to understand what that puzzle is. I thought it should be helpful to consider the different ways people approach computing, while we're waiting for more from Jim.