Author Topic: MLC 68k (Read 26454 times)

DJ Omnimaga · « **Reply #60 on:** December 31, 2006, 01:59:00 pm »

wow bfr i missed your post above the one about your site, I,M glad this will support number higher than 255 or 65536. Does it still run fast?

Halifax · « **Reply #61 on:** December 31, 2006, 09:05:00 pm »

wow how do you do that?? make it support numbers higher than 65536. What do you like combine 16 bit registers to make a 32 bit register?

Liazon · « **Reply #62 on:** January 01, 2007, 03:11:00 am »

or using floating point registers. 68k is 32 bit anyways. iirc it has 16 32 bit registers for addressing and data manipulation purposes

bfr · « **Reply #63 on:** January 17, 2007, 12:34:00 pm »

So, MLC has been coming along...slowly. The next steps are to complete the string parser, the variable name parser(s), the new VAT system for pictures, and the new VAT system for strings.

Would you all be interested in a demo? I've got finals coming up soon, but if you would like, I could release a demo of MLC within a few weeks.

Also, I'm trying to keep MLC 68K backwards-compatible with MLC for the TI-86, but I'm not sure if it's going to be completely compatible with MLC for the Casio AFX, unfortunately, because there was little communication between the one programming MLC for the Casio AFX. The MLC converter will take care of any minor incompatibilities though between MLC 68K and MLC for the TI-86 (and hopefully for the TI-83+, some time), such as changing "|" to indicate a command, supported by MLC 68K but not MLC for the TI-86, to a "#" to indicate a command. I might just have the converter generate errors or warnings for major incompatibilities, such as advanced VAT manipulation. Hopefully, even if MLC 68K and MLC Casio AFX are completed independently, I can let the MLC converter handle any incompatibilities.

DJ Omnimaga · « **Reply #64 on:** January 17, 2007, 02:07:00 pm »

sound nice, any screenshot planned soon?

bfr · « **Reply #65 on:** January 17, 2007, 02:20:00 pm »

Hmm...I could take new screenshots, but there wouldn't really be anything interesting to take a screenshot of at the moment. Watching variables being declared isn't very exciting.

Once I complete all of these parsers and VATs (which could take anywhere from probably a couple weeks to maybe a month or so), though, then loads of new commands are going to be implemented, including graphics/sprites/tile-mapping commands, which is going to be a good thing to take screenshots of.

DJ Omnimaga · « **Reply #66 on:** January 17, 2007, 03:07:00 pm »

aaah ok i was just asking in case there was new addition into graphics or example of games in action

lachprog · « **Reply #67 on:** January 18, 2007, 08:15:00 am »

Nice to see that MLC is progressing

I'm looking forward to be able to program in this!

And btw, a demo would be nice

DJ Omnimaga · « **Reply #68 on:** January 18, 2007, 01:09:00 pm »

hey lachprog nice to see you there! And yea mlc sound nice I can't wait to see it in action

(now i should remember to check mario 68k progress more often as well %)

)

bfr · « **Reply #69 on:** April 04, 2007, 09:27:00 am »

I'll try to get a demo up sometime (which might not be until summer, but...).

Anyway, after not working on MLC 68K in months, and having a lot of time due to Spring Break, I decided to work on it. The code was really disorganized (because things were in the middle of being changed from the static VAT to the dynamic VAT, and because I also just have a bad habit of coding things in a disorganized way) and hard to make sense out of, especially after not doing much C for a while, and there were routines that were partially finished which I didn't really know where I left off, so I've just created a new TIGCC project file (this is not really a new project...just a different file) for an organized rewrite. Basically the only things that I don't need to rewrite are the initial MLC program detection/checking for the "MLC:" header, and the mathematical expression parser (the string parser was supposed to be easier, yet I never finished it...).

I'll hopefully have a cool screenshot (or even demo, but probably not) to show to you all by this Saturday, but if not, then the next progress on MLC might occur as late as in May or June, due to a really intense forth quarter history project and other things....

Madskillz · « **Reply #70 on:** April 07, 2007, 04:16:00 pm »

Sounds great bfr...sorry it has been taking me so long, but I have one month left until summer break. I will however hit this again probably sometime in the coming week. I have been coding like mad lately on a few different projects, I am gonna see how many I can get done before school starts again in the fall. I working MLC demo for the 83+ is high on my list. There WILL BE A DEMO hopefully before June, but for sure before July.

bfr · « **Reply #71 on:** April 07, 2007, 04:48:00 pm »

Awesome, and nice to see you here, Madskillz.

I seriously would be really upset with myself if I don't finish MLC within a year (it will hopefully be done by the end of this summer), and there should be a demo probably whenever after I get sprites or something cool like that finished (which might be sometime around June or July). I could release a demo now, but stuff like pausing and clearing the screen and declaring variables isn't that exciting. I'm not really going to be able to work on MLC much the rest of this school year, particularly during the next few weeks, because I have a lot of work - mainly a dreadful forth quarter history project in which I must prepare a varied lesson plan for a few weeks for a unit and then present, in front of the class, a portion of it.

bfr · « **Reply #72 on:** April 18, 2007, 12:44:00 pm »

I didn't have much homework today, and I accidentally left my mathematics book at school, so I decided to work on MLC today and yesterday (I forgot my book both days

). Anyway, I made some progress on the string parser and the declaration of strings. At the moment, the string parser can parse literal strings, which wasn't really complicated to code, and strings can be declaraed. What still needs to be done? The string parser can't parse variables that are strings yet, and the values of strings that are already declared can't be changed. Both of these things should be fixed by the end of this weekend.

Here's a screenshot: user posted image

The weird stuff being displayed is temporary debugging stuff that shows that it is working, and the error that occurs at the end is because I didn't make the program counter update by the proper amount after declaring a string (which should be fixed by this weekend).

Insanity · « **Reply #73 on:** April 18, 2007, 12:47:00 pm »

*Insanity

Liazon · « **Reply #74 on:** April 19, 2007, 04:32:00 am »

89 has more compatibility w/ old games AFAIK, 89t just has a lot of flash

good work bfr!

Author Topic: MLC 68k (Read 26454 times)

Liazon

Insanity

Liazon