Forums Bug Reports if $me == $nick

Amongst a fleet of so many things itd take up a lot of space to report the multiple possible bugs .. the strangets yet most fundamental one is " if $me == $nick " no longer working .. why is this ?

Also a lot of various ial stuff seems to have changed to the point where the current script i use is presently unable to function in 6.14

I was actually working up a bug report for this one, once I've narrowed it down exactly.

There was a fundimental change to parsing of IF conditions that have broken many old scripts. You should try using ()'s around your if-checks now, at least whenever possible.

I haven't exactly figured out what still works and what nolonger works just yet. Could you please paste the exact code you're using that breaks it?

[color:990000]if ($me == $nick)[/color] does work however.

- Raccoon

Sadly i all ready use that in ma coding and sadly there is i fear a lot of issues in 6.14. The script was last updated when 6.0 was released, so all coding is current, so as yet im not sure what has been changed in 6.14 but it has broken a lot of things.

maybe i his starting to force us to use the () and lets say that i agree with him.
I realy don't like to see ifs without the ()

problem im having in 6.14 is something in the scripting of the events is no longer working in 6.14 which is causing the rest of the script to fall apart. all my if statements are using the () and always have. ial being a huge thing an a big key in ma script.

interesting point, well if you need help i can help you fix that script, that way we can find from where the problem came...

The guy who wrote this script is mr-rdk an can be found on the undernet IRC network .. i know a lil about this .. but he is the main one who does the scripting im erely trying to find out what fundamental things could be causing various issues.

i never use () and my scripts are fine

Ok, but i believe it is a bad programming attitude and it takes more time to run (i benchmarked it)

I have to agree that using the () are essential.

Can khaled or anyone else tell em what variables have changed in 6.14 that arent documented ? as this si what is causing my problems and unf untill i know what variables have been changed an not mentioned i cant get this fixed.

well whenever i actually NEED to use () i will (c++), but when i don't i find it makes it look a lot neater.

If you could give an actual example of code that you're using which has caused this bug it could help a lot. Knowing which OS you're using might also be useful.

I wish i could .. but there is so much broken and not working i dont even know where to begin. A simple roll back to 6.12 and everything works perfectly .. so there is obviously quite a lot of significant changes to a lot of things that is causing a multitude of stuff ups in the script.

I don't use parentheses, and "if $me == $nick { stuff }" works just fine.
I haven't noticed anything similar not working either.

Well im not sure where to begin. But im sure it'll figure it'self out in time

Hmm, I should dig up the clone script that Julie2 said stopped working.

.. ah, here it is. Poolshark's CloneStopper2.5
She explained the error started on line 112, and after adding ()'s she was given 3 more errors and lines that she added ()'s too.

*lets others look too*

EDIT: Oh yea, it wasn't a status window error she was getting... but an infinite loop that she had to break out of. (Ctrl+Break or Ctrl+ScrlLock)

Well I didn't run the script, but I took a look at it and really there's little wonder it's having problems. Apparently whoever wrote that hates syntax with a vengeance. There are dozens of lines which will cause 'ambiguous format' error messages (ie. if %clone1 !ison $chan || %clone2 !ison $chan goto noclones) - that's not a result of errors, it's a result of bad syntax. Unfortunately the spaghetti codeness of it makes it very difficult to tell if there's a logic bug in it aswell.

At this point I'd like to clarify something (not to you; in general). if condition { commands } is perfectly acceptable by mirc and

1) doesn't generate errors
2) is faster (NOT slower, as many people seem to believe) than if (condition) { commands }

In all the scripts I've written so far, I use this syntax and I've never seen it break. Of course, in multiple conditions, () pairs may be needed to control the order of evaluation (for example if 0 && (1 || 2) ), but that's all they are necessary for.

However, things are different when you omit the { } around the commands part: if condition command can break very easily, depending on the contents of "condition" or "command". I would strongly advise against this syntax, unless one really knows what they're doing.

Well when i say that using () is faster please trust me next time...

alias super {
var %fich = $false
var %ticks = $ticks
var %i = 0

while (%i < 35000) {
if %fich == $true echo teste
inc %i
}
echo 1º time is $calc($ticks - %ticks)

%ticks = $ticks
%i = 0

while (%i < 35000) {
if (%fich == $true) echo teste
inc %i
}
echo 2º time is $calc($ticks - %ticks) 4game over i win!
}

output:
1º time is 1562
2º time is 1516 game over i win!

you can run it the times you want... it is not much faster but it is faster!!
the code looks better, faster and more professional (start training if you want to be a good programmer)

btw using {} also makes the code look better but in this case makes it slower

thanks

p.s don't put %fich = $true