I've been considering adding actual words for the logical operators:

// &&	= and

// ||	= or

// !	= not



if (player[i].possessed

	|| (!player[i].dead && !player[i].unconcious))

{



}



if (player[i].possessed

	or (not player[i].dead and not player[i].unconcious))

{



}

I'm sure that people who are weaker programmers might like these words, especially since they're much closer to English.

I've also been considering unless() and until() statements, which are basically if() and while() that execute when the condition is false. Sometimes it could mean conditionals that better explain themselves.

// You don't have the trinket, you get nagged.

if (!(found_legendary_trinket))

{

	Textbox(	

		"You still haven't found it? Just be glad the gods didn't give " + 

		"me the power to walk off of this throne to smack you."

	);

}

// You don't have the trinket, you get nagged.

unless (found_legendary_trinket)

{

	Textbox(	

		"You still haven't found it? Just be glad the gods didn't give " + 

		"me the power to walk off of this throne to smack you."

	);	

}



...



while (!(done))

{

	

}

until (done)

{



}

Yeah, yeah. The nested brackets around a single conditional aren't necessary, but it would be necessary to make until/unless work. Either that, or reverse the behaviour of the compiled code's jumps, so it would go past the if()/while() when the condition was true, and go into the block when false. The latter would avoid the minor, minor effect of logical not on a statement inside brackets, but likely suffer slightly more complexity in the compiler.

So what says you people? Is this good to add more variety into the language by introducing new words, or should they be avoided?

Edited to not abuse preformatting. -Grue
Thanks. -Overkill

I find it pretty easy to just set my "code words" using #DEFINE tags. It's not exactly necessary to hardcode it...

Also. Isn't it possible to enact Unless() and Until() loops using different forms of If() and While() logic anyway?

I find it pretty easy to just set my "code words" using #DEFINE tags. It's not exactly necessary to hardcode it... Even though #define can be used this way, I dunno... But yeah, of course it's not necessary. However, I think verge1 and verge2 both had and/or words acceptable in conditionals, as evident in the the textpad syntax definition I have (which must have just copied the v2 syntax definition and added v3 functions).

Also. Isn't it possible to enact Unless() and Until() loops using different forms of If() and While() logic anyway? Yeah, basically just using the ! operator on the whole condition cluster.

I dunno, yeah I'm a bit conflicted too. But allowed variety occasionally makes cleaner code when used effectively. Although, when ineffectively used, code could possiby be worse, in a minor way (like mixing logical keywords with logical operators in a statement). But bad code is always bad code.

Well, I suppose if you feel the urge to do so, it's not going to break the engine or anything like that.

v1 had AND and OR.

And I recall them making my first little steps into programming very easy.

And having them certainly would not make the code less readable to experienced programmers.

Anybody who would type 'NOT' in place of a simple '!' when they know full well that both would do the same thing...

Well, I don't know about those people. Heck, in Python that even feels right. But I don't know about here. ...I _guess_ it wouldn't hurt.

You could also add IS and ISNT as valid replacements for = and != along these lines. And then we'll be a step away from VergeSQL, which is man's oldest dream. >_>

Quote:Originally posted by Gayo

Oooh, someone should totally design a vc lib for interfacing with a MySQL server.

Also, someone should suck my dick.

Actually, using zeromus's plugin library, it'd be a trivial matter to build a module to interface with a SQL Server *OR* with an FUFME server...

...NOW IF HE'D ONLY MAKE THE GODDAMNED EXAMPLES TO SHOW THE REST OF US HOW GRR.

Well no, I hadn't planned to have the keywords replace the existing logical operators, but rather give the user an alternative to symbols if they so chose.

VergeC is not meant to be C, therefore it can have differences. One such difference could be the introduction of keywords which really don't hurt the syntax in order to make it slightly easier to pick up for new people. It isn't really redundant, it's an alternative syntax. It's simply making the compiler check for another keyword without hurting the internal execution of code at all.

Also, the compiler/interpretter already is separate from the engine. There's just a crapload of vc wrapper functions that are called by the interpretted code, which in turn call the actual engine functions.

Oh yeah, and added unless() / until().