Here come the poorly designed games.

How will that be any different than it is now?

Oh great; so what, is that a whole year's time down the toilet?

I have no more than two weeks left to work on this, and already I am hearing that there are major problems and simple things like a = a + b won't work right. Either I fix what I can now, or I give up and forget the whole thing. And yet I wonder if the right version got uploaded; I tried twice to upload it...

Anyways, if anyone wants to see this work out well, it would be a makor help to me if I can get some help and testing and stuff; I had no idea of such problems until I bothered to read this.

I have recently decided that I will need to add in loose type-casting, dereferencing, pointers, arrays of unknown size (only as pointers or when an address is specified), and allow array literals in assignments and as arguments...without these things it will be very frustrating to work with arrays of any size and stuff like that...or should I have gone with an idea I had before and cut out expressions and everything, and allow (require) the direct use of registers and simple ops for everything? I am just so frustrated right now, idk what to do. On top of that, everyone could care less if I never touch my project again; I think they resent that I "waste" so much time on the computer (probably because it doen't make anyone any money, right?)...it would be so easy to just give up now.

Hey, thanks a lot for critizing what you do not fully understand and turning so many people away; I cannot have all the great features of OOP and other 3GL's like C++/Java AND have good assembly. FYI, you could never do multiplication or division in assembly either; it requires whole routines and stuff.

also, there is no floating point of signed numbers in assembly; that is probably why you got those weird results for that comparison to -100. I am very tempted to just go remove the unary (-) and not (~) operators right now.

I apologize if I said anything harsh, I was just very frustrated. I can understand somethings as simple observations / analysis, but I guess I could have asked people not to downtalk my hard work in a nicer way.

If you are offended when someone points out basic flaws in your work, you should look into yourself. Seriously. What do I not understand? I wrote a simple one-liner in this language, and I got wrong code. I added another line and it brought in several more errors. How come you haven't noticed THAT during a WHOLE YEAR? You don't need testers for that. It seems as if you'd never even tried to run your program. The result? In its present form it's completely useless. Why do you expect praise for that?

Fortunately, I'm too angry to continue...

My goodness. Give the guy a break.

Even though you provided constructive criticism with your posts above, you should try to not get too much harsh or rude because I've seen people getting banned from ticalc.org for that :P , here is the ticalc.org posting rules:

Please be constructive and keep comment topics relevant to the article you are replying to.

Don't post general help questions; for such assistance, check our Help section and our Mailing Lists.

Don't insult or flame other people in your comments. Keep such sentiments to private email, or better yet, avoid them completely.

Don't post general feedback or criticism about the site. Instead, Contact Us through email. An exception is suggestions related to the item at hand, but be sure to email us as well since we can't always read every comment. Encouraging suggestions get much better results than irate demands.

Don't use language you wouldn't hear on U.S. network television.

HTML tags are not allowed.

Advertisements and spam are not allowed.

Keep comment signatures short and tasteful.

Don't post asking why a comment was deleted; we deleted it because we felt it was in violation of these guidelines. If you need more of an explanation, please Contact Us.

Don't include messages such as, "Don't delete this comment or else." If you have doubts that your comment is appropriate, we probably will, too. We will delete inappropriate comments irrespective of such pleas.

Don't post comments designed to disrupt page display, such as excessively long comments or gibberish.

Messages containing "first comment" boasts, requests for game ports, or criticisms of "newsworthiness" will generally be deleted.

In order to recieve constructive criticism software has to be at a level where it is functional. Then the users can use it and give feed back, Then you can use the recieved constructive criticism to improve it.

But it sounds like it aint even functional.

>>because I've seen people getting banned from ticalc.org

Like me :)

Yes, fortunately. Wow, CoBB. Cut the guy some slack, even though I can understand your anger... :( It's probably frustrating for him too.

I agree--simple addition errors are almost inexcusable in a compiler release, even if it is a beta.

Also, (to shkaboinka) as a developer you should expect and even be grateful for criticism--you apparently did not catch that error before releasing Antidisassemblage, and CoBB was able to point it out to you. Just fix the problems, and move on--it will take a lot more than criticism to destroy the importance of your project to the development community.

I would of look at a simple basic language and just add stuff like +-*/()%^ and then build off of that. Most all languages are built around operators of some sort. Once you get those working then add features. So what if you have to write a routine to do */and %. Add those features and just jump and run the code if needed. I think you should forget those peoples comments and try your hardest to make something good for your self. On a side note a bunch of if statments is not the way to go. BNF notation and reg expressions is a lot faster.

Maybe it was. You have probably complicated your design too much, or "oversimplified" which leads to difficulty translating operator-based languages to an 8-bit processor like the z80. This is evident in that there seems to be some sort of group working on this, it has been in the works for quite some time, and I was able to cook up TIPower (another one of these cross platform languages) in less than a month with more features and less bugs.

Or maybe I should just shut up ;-)

Nobody wants you to have OOP, we realize that isn't feasible.
However, part of the usufullness of a high level language is that you don't have to worry about certain hardware limitations, such as the lack of multiplication and division instructions. Just look up your expression parser code, and have a multiplication (say, "Expr1 * Expr2") translate to "calculate Expr1 (and push it on the stack) \\ calculate Expr2 \\ call Times". Then include a routine (with start label Times) that takes the topmost two values of the stack (well, you'll have to take the return address into account ofcourse) calculates the product and returns it on top of the stack (careful with the return address). That isn't such a big problem, is it? You'll just generate a little more code then in the case of "Expr1 + Expr2", but that's all.

At last, the gap between BASIC and ASM has been broken! All we need now is a COBOL compiler for the z80 calcs :-)

Indeed...everyone LOVES the world's worst programming language ever.

Heck no, COBOL is the ONLY language that you can actually type in almost-english sentences and get an actual programming command. At one point, COBOL was the de facto standard for programming languages! In COBOL, you can enter: Add one to COBOL and return COBOL

Thats what sucks about it. It requires so much extra and useless typing.

COBOL and the idiot code grinders that use it to write paycheck-printing programs are singularly responsible for all that inane Y2K hysteria.

What's the difference with "a := a + 1;" ?
If you pronounce that "a becomes a plus one" it's near-english too (and saves a whole lot of keystrokes). If you really want your code to *look like* english just throw in a preprocessor that substitutes every occurence of 'becomes' with ':=' (yeah, I know, you've gotta make sure you don't replace 'becomes' if it appears in a string literal or comment, but you get the idea; nothing a reg exp parser can't handle).
A friend of mine claims the same about some language called Ruby: "it reads just like english". Well, I happen to think it's not even readable in the first place, but then again, that's his idea about Pascal. Anyway, what I was trying to say before I got distracted, you may want to look into Ruby, you just might like it. (It uses a lot of symbols, to get the near-english thingie, you'll have to pronounce their name, but then it comes a lot closer to english than Pascal.)

Cobol ain't *that* bad, not as bad as white space at least... Try an on-calc whitespace interpreter (and yes, I'm fully aware there's no tab key on the calc :D ), that oughta be cool. ;)

On a side note, what's the best way to annoy a whitespace programmer? (Apart from showing him a real language ofcourse :P )
Answer (mirrored, so you don't read it immediately, but give it some thought first): !!ediw retcarahc eno eb ot spots bat lla efineD