Forums Feature Suggestions Case: 1,2,3,4 etc...

It's a good idea to keep mIRC away from making it's language draw away from a C syntax, because it would benifit all who program, that way they don't have to keep on going through different help files and then get mixed up later on.

So to make it simple I believe that it would be better to just keep the language universal.

First off, don't kid yourself.. mIRC is nothing like C.

The *only* thing mIRC shares in common with C style syntax is curly braces. Just about nothing else is C inspired. mIRC is untyped for one (let alone dynamically typed), but more specific to syntax: there's no ; command endings, no required (), no strings, no for loops, no arrays, a goto label is ":name" not "name:", functions that return values start with $, functions that dont (optionally) start with /, variables start with %, identifier (not mirc "identifiers") tokens can be any string of non-space characters in mirc, C has it well defined. There's no ON * event handling syntax. Heck, it doesn't even share all the properties of if statements: C doesn't use "elseif". Is that enough difference? If you define a language as C style based on the fact that it uses curly braces, that covers a lot of languages... languages like Tcl, for instance, which mIRC is probably more similar to.. and that language could not be less like C.

Secondly, you talk about getting mixed up-- if mIRC starts adopting C idioms when it hasn't ever done so, that's far more of a mixup to any mIRC scripter than anything else.

If anything, it's a good idea to keep mIRC using the same idioms it already is-- that would confuse no one, because it's consistent.

*pets argv[0]*..

There there, take a nap now..

I beg to differ the case and default statement are parts inside the switch() {

}
statement so it could definitely make the distinction without breaking compatibility. mIRC would have to break switch,case & default aliases anyway so whether it breaks default or default: is of little importance.


Since when has that stopped mIRC from implementing anything ? By that logic the whole on *:TEXT:*:*: concept could/should have never been implemented.

The same escape logic would apply to the case statement
"case X $+ $chr(58) says:"

You are probably right in SOME ways, since nobody's opinion will be the same, let's just end this with: "We agree to disagree."


Really? I always thought the syntax was alot like it and when I did, I didn't say all of it was exactly like it... of course! I don't really see why they put ";"'s at the end of every line. I don't see the use for it. It just makes the code look sloppy, and unreadable. (but that's my opinion, one man's junk is anothers treasure.)

Onwards...

I have seen alot of my scripts using a buttload of elseif's just because I needed to make a simple conversion table, or encryption logarithim. My example in words is that if a line starts with '-', then I want it to read the command before processes all the data it gets. So with that said, I need to use $iif or if,elseif,elseif,elseif,elseif,else statements because it is the only way to do it, for now.

Now... if we had case/switch: it would be alot easier.

For the goto loop:
If I wanted to use a goto, I would take 4 hours trying to figure out what was wrong with it then give up and do it the hard way. Right now, I don't feel like absolutely wasting 4 hours of my time when I have a life to live.

For anything else:
Just ask yourself, is there ANYTHING that can have a comeback and make sense to what I'm about to try and debate with?



Hi there. I have seen almost every good scripting language out there. They all have one thing in common: They all confuse me.
When you talk about confusion, it's inevitable. Why keep everything the way it is and accomplish nothing and be lazy, when you can do something about it, make it better to use, and pretty much delay anything that would make anyone argue?

Personally, I really think that switch would be good for mIRC, because switch in mIRC has no equivalent yet. And another thing: If I posted every suggestion that ran through my mind, you guys would have a huge forum running. But instead, I think about what I'm going to suggest. I look at the quality of my posts, and I think: "Are people [i]really] gonna wanna read this? Or are they going to laugh at me and spit in my face?"

That is the only reason I posted here, so I have data and reason to back anything up that I say, so hit me with your best shot, and may the more experienced or more prepared win.

Point blank: I'm just trying to see what can be done to improve this for everyone, and not just myself.

Thankyou for your time, and if you reply to this and it is off topic, please PM me with it so we can talk privately, because I don't want any more spam on this thread.


PS:
I am sorry for posting something completely off-topic, just needed to clear up some spam.

+1

Stopped counting how often I could have needed some for()-like statement, rather than using var %i = <start>, while (%i < <condition>) { <do stuff>, <change> %i }

Greetings, BhaaL

CASE isn't the same as FOR. FOR and WHILE are pretty much interchangeable... they basically do the same thing, but are formatted differently. Case is more related to just IF/ELSEIF/ELSE.

CASE is also relatively interchangeable except for fallthroughs though fall throughs can be done with nested ifs

Right. I wasn't meaning it wasn't interchangeable... just not with FOR.

Some people say that it's just the same as using an if statement.
Well; What if you have 40 things you want to check?

40 times does not seem pleasant.

But, even though using the goto loop, it would just make the code longer and take much more time to parse rather than just doing it.

Nobody said it was the same syntactically. Semantically, however, you're doing the same thing with a set of if statements.