mIRC Home    About    Download    Register    News    Help

Print Thread
Page 2 of 2 1 2
Re: File Handle routine, EOF halts execution... [Re: MeStinkBAD] #228596 02/01/11 03:59 PM
Joined: Oct 2004
Posts: 8,330
Riamus2 Offline
Hoopy frood
Offline
Hoopy frood
Joined: Oct 2004
Posts: 8,330
Since your /fopen script is large and possibly has something else causing the issue, I set up a short script to show what $$ does and ran it in both 7.17 and 6.35. The results are the same:

Code:
alias t1 {
  echo -a 1
  t2 $1-
  echo -a 3
}

alias t2 {
  echo -a 2
  echo -a $$1-
}


If you use /t1 test with both versions, you get:
Quote:

1
2
test
3


That shows that it runs through all of the way because there is a $1. However, if you use /t1 in both versions, it only shows:
Quote:

1
2


This shows that it halted both aliases because of no $1 when using $$. If it was RETURN instead of HALT, then you'd see:
Quote:

1
2
3


... where only the $$ line would be skipped. I can change those aliases around so that /t2 will RETURN $$1- and the result is the same, or so that /t2 is called as $$t2($1-) with no $$ being in /t2 at all and the result is also the same.

As a comparison, here's how it would work if it doesn't HALT:

Code:
alias t1 {
  echo -a 1
  echo -a : $t2($1-)
  echo -a 3
}

alias t2 {
  if ($1) { return $1- }
}


Results for /t1:
Quote:

1
:
3


(: is used so it doesn't throw an error about echoing a null value). As you see, with RETURN, it will continue processing even if there isn't a $1. If we change that to HALT, it works like $$ does-
Code:
alias t1 {
  echo -a 1
  echo -a 1- $t2($1-)
  echo -a 3
}

alias t2 {
  if (!$1) { halt }
  return $1-
}


Results for /t1:
Quote:

1


As you can see from these examples, $$ does HALT the script and associated aliases instead of using RETURN. Most likely, it's something else in the script that reacts differently between versions that is giving you the problem. $$ has acted as a HALT for as long as I can remember... I don't feel like pulling out even older versions to find out when or if it was ever different. Since your last screenshot shows a difference and you used 6.35 and 7.17, my test with those two versions that shows $$ working the same between versions should be enough to show that it's something else in your script that is working differently. However, if you or someone else wants to do the same kind of test in 6.2 or older, feel free.


Invision Support
#Invision on irc.irchighway.net
Re: File Handle routine, EOF halts execution... [Re: Riamus2] #228598 02/01/11 04:29 PM
Joined: Apr 2003
Posts: 342
M
MeStinkBAD Offline OP
Fjord artisan
OP Offline
Fjord artisan
M
Joined: Apr 2003
Posts: 342
Originally Posted By: Riamus2
As you can see from these examples, $$ does HALT the script and associated aliases instead of using RETURN. Most likely, it's something else in the script that reacts differently between versions that is giving you the problem. $$ has acted as a HALT for as long as I can remember... I don't feel like pulling out even older versions to find out when or if it was ever different. Since your last screenshot shows a difference and you used 6.35 and 7.17, my test with those two versions that shows $$ working the same between versions should be enough to show that it's something else in your script that is working differently. However, if you or someone else wants to do the same kind of test in 6.2 or older, feel free.


Yes yes okay that's good to know that $$ is next to useless. It's be slightly less useless even if it did act as /return IMO. I don't care about that though. Now explain what I'm experiencing! The script is not that large!

You know... could the /debug function actually display script processing information. Why is there no way to access the trace stack? Why isn't there no profiling option? Why is the editor so poor? No language is as complicated as this one. Not one language.




Last edited by MeStinkBAD; 02/01/11 05:06 PM.

Beware of MeStinkBAD! He knows more than he actually does!
Re: File Handle routine, EOF halts execution... [Re: MeStinkBAD] #228600 02/01/11 06:21 PM
Joined: Jul 2006
Posts: 3,790
W
Wims Offline
Hoopy frood
Offline
Hoopy frood
W
Joined: Jul 2006
Posts: 3,790
I can reproduce the problem, which is in fact not a problem.
I used this code :
Code:
#_DEFAULT.PROPERTIES OFF

[start]

[CONST]
SJISSPEC=$mircdir $+ sjis-0208-1997-std.txt

#_DEFAULT.PROPERTIES END

ALIAS __SJISspec { return $readini($script,CONST,SJISSPEC) }

ALIAS DEC2HEX {
  var %pad = $len($base($$1,10,16))
  if (2 \\ %pad) { %pad = %pad + 1 }

  if ($isid) { return $base($$1,10,16,%pad) }
  elseif ($1 isnum) { echo -aspe 0x $+ $base($$1,10,16,%pad) }
}
ALIAS HEX2DEC {
  if ($left($1,2) == 0x) || ($left($1,2) == U+) { tokenize 32 $right($1,-2) }
  if ($isid) { return $base($$1,16,10,1) }
  else { echo -aspe  $base($$1,16,10,1) }
}

alias import_sjis {
  if ($hget(sjis)) hfree sjis
  hmake sjis 10000
  fopen sjis $qt($__SJISspec)
  var %z
  while (!$fopen(sjis).eof && !$ferr) {
    tokenize 09 $fread(sjis)
    inc -s %z
    if ($0 > 2) { var %sjis = $1, %utfc = $2, %desc = $3- }
    else { var %sjis = $1, %utfc, %desc = $2- }

    ; if ($+($#,*) iswm %sjis) continue
    if ($hex2dec(%sjis) < 128) continue
    echo -s %desc - %sjis - %utfc - $feof - $ferr -
    if (<doublebytes> isin %desc) { /hadd sjis $hex2dec(%sjis) <doublebytes> }
    elseif (<cjk> isin %desc) { /hadd sjis $hex2dec(%sjis) $hex2dec(%utfc) $chr($hex2dec(%utfc)) }
    elseif ($left(%utfc,2) == U+) { /hadd sjis $hex2dec(%sjis) $hex2dec(%utfc) $chr($hex2dec(%utfc)) }
  }
  :error
  if ($error) echo -s Error : $error
  fclose sjis
}
First note that there's a empty line in your big file at the end.
This code will show you that in mIRC 6.35, $feof (or $fopen().feof) is 1 after $freading the last non empty line, which cause the while loop to stop.
In mIRC 7.17, it correctly read the next line, which is $null and in that case mIRC halt because of a $null value and the use of $$.
The commented line in the code is odd, $# doesn't exist which cause an error if you have that warning option enabled, or a line like "if (* iswm %sjis) continue"..


Looking for a good help channel about mIRC? Check #mircscripting @ irc.swiftirc.net
Re: File Handle routine, EOF halts execution... [Re: MeStinkBAD] #228602 02/01/11 09:16 PM
Joined: Oct 2003
Posts: 3,918
A
argv0 Offline
Hoopy frood
Offline
Hoopy frood
A
Joined: Oct 2003
Posts: 3,918
$$ is very useful. It's *not* meant for verified parameters, it's meant to verify parameters:

Code:
/o mode # +o $$1


The above alias will not run if you don't supply a parameter. This avoids an error message from the server. If you *were* to provide your own error message, you would need to use $1, not $$1.

Return or halt doesn't make a difference here, since $$* isn't meant to be used in deep stacks. Halt, however, does make sense in the context of parameter verification, since you would want to halt in this situation:

Code:
/kb ialban $1 | kick # $1
/ialban mode # +b $$address($1, 2)


If $$* did /return in the above, you would still perform the kick even if you could not perform a ban, because /ialban would return, not halt the entire stack. That's usually not what you want from a kickban. Similar problems arise when you move parameter verification one alias down the stack, which is commonly done when you refactor larger scripts.

Finally, stop complaining. If you don't like the language, go find one you like and use it. mIRC is not complicated-- in fact, it's ridiculously simple. "$$* will /halt if the identifier expands to $null" is a simple rule. I can name hundreds of languages that have orders of magnitude more syntax rules, keywords and semantic gotchas. Java, C++, Scala all come to mind, but it's completely irrelevant. Khaled isn't going to redesign the entirety of mIRC's scripting language just because one person got mad that his bug report wasn't actually a bug and refused to admit it was PEBKAC. If you don't understand a feature, just don't use it. That is simple.


- argv[0] on EFnet #mIRC
- "Life is a pointer to an integer without a cast"
Re: File Handle routine, EOF halts execution... [Re: argv0] #228744 09/01/11 11:11 AM
Joined: Apr 2003
Posts: 342
M
MeStinkBAD Offline OP
Fjord artisan
OP Offline
Fjord artisan
M
Joined: Apr 2003
Posts: 342
The additional line at the end of the file was the problem. Thank you.

And Argv, $null is an empty string... but it's also an identifier. Take a look at this...

Code:
//echo -a 1 ; $$+($$chr(32),$$str($chr(32),5)) ; | /echo -a 2 ; $null ; | /echo -a ; $$null ;


Result is...
Code:
1 ; ;
2 ; ;


I understand it's purpose... but it's behavior is inconstant. And that is because mIRC's parser is inconsistent.


Beware of MeStinkBAD! He knows more than he actually does!
Re: File Handle routine, EOF halts execution... [Re: MeStinkBAD] #228760 09/01/11 06:42 PM
Joined: Oct 2004
Posts: 8,330
Riamus2 Offline
Hoopy frood
Offline
Hoopy frood
Joined: Oct 2004
Posts: 8,330
What are you expecting the result to be?

$$ will halt the command if there whatever $$ is attached to is NULL. And $null will always be NULL, so $$null doesn't echo in the 3rd echo. That would be expected.


Invision Support
#Invision on irc.irchighway.net
Page 2 of 2 1 2