The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I may do that, but I have to get rid of some crutches first. For example, the memory map is not final yet. Anyone trying to follow an article where I throw in new parts at every step and then replace them by something else two steps later would be totally confusing. Once I got rid of all these stepping stones, an article would make much more sense.
For example, I now use a simple power-on reset and an EEPROM at memory address 0000 to start the Zwölf. Nice and well, that sure works. For several reasons, I want to get rid of the EEPROM, but as it is now, the Zwölf would only find empty RAM after a reset. I need a way to load a program into RAM before the processor starts running. A PIC microcontroller is going to that. It's going to control the processor's clock and operating modes, load a bootloader into the RAM via DMA. That opens up many new possibilities. The Zwölf's clock frequency becomes programmable. Even single stepping by bus cycles or instructions becomes possible. I can support the old Elf's features, which require a very precise clock frequency. The PIC could even synchronize up to 8 CPUs on the same bus, so that they share the memory and I/O devices without getting into each other's way.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
At 70, I have still have no understanding of the creature known as woman, but have learned patience and tolerance, as you have. But I do understand that I am not perfect and she tolerates and encourages me to be the weird that I am so what more could I ask for?
Monday starts Diarrhea awareness week, runs until Friday!
Back then MIcrosoft knew they had to explain it or no one else would.
Now, everyone thinks, "I don't need to do no 'splainin cuz it already been done somewheres else on the Internet prolly. So no one really explains. Oh, that 2nd param no one explains what it is.
I liked MFC. OOP wrappers around API. Nice and clean.
But I was a newbie in 1995-8 and OOP was rising and I jumped on the New Thing Boat and this was my anchor.
But, alas, MFC went away for the most part...was ignored when C# came out and all that learning...down the drain. MFC was a weird sidebar but I still liked it.
I never liked MFC, it always struck me as over complicated, especially those ridiculous macros just to generate a simple jump table. Probably because of my machine code and assembler background, I much preferred the Win32 API.
I never liked MFC, it always struck me as over complicated, especially those ridiculous macros just to generate a simple jump table. Probably because of my machine code and assembler background, I much preferred the Win32 API
Yeah, I remember my mentor at the time felt the same way.
I think the thing I liked about it at the time was the distance I got from the Windows Message loop.
It was wrapped up nicely in MFC template project.
Of course in the original WinAPI you had to handle it all yourself.
MFC was kind of like the jump to C# way before C#. But it wasn't as nice as C#, of course.
Yeah, it's amazing that VSTudio still even supports MFC. It's too bad it didn't take off like C#. I liked it better because it was more esoteric. Seemed more like hidden knowledge you had to go into the cave and explore for. Then along came C# and brought everything out into the light and everyone was dragging and dropping and developing.
Last Visit: 27-Mar-20 23:27 Last Update: 27-Mar-20 23:27