SRL Archive - OSR Help

I've discovered an extremely weird bug in Simba: if you name a variable as 'i5', you will encounter a strange bug that parameters are no longer automatically displayed when a parenthesis is typed after the function name.
Sounds completely absurd right? See evidence below:

No other variable names have this problem:

Not sure if it's just my Simba behaving so oddly, so try the code below and see if anyone else have this problem.

program new;
var
  i5: Integer;

begin
  writeln    //now add a '(' to <<<
end.  

Happens to me too, quite interesting because I do remember other times when Simba wouldn't show the parameters unexpectedly, though I don't think I ever named a variable i5 before.

From: litoris
Happens to me too, quite interesting because I do remember other times when Simba wouldn't show the parameters unexpectedly, though I don't think I ever named a variable i5 before.

Yeah i've like 5 for loops within a function so i decided that naming them i-i5 is more neat than just i j k l m or something. Took me a good 10min to find out why my parameter hint disappeared. Probably some other variable names could cause this problem too? Anyone has any idea what's behind these cursed variable names?

I know that I have had this occur previously, but as in litoris' case I have never called a variable i5 so it definitely occurs with other variable names, too. What causes it I have no idea.

From: P1ng
I know that I have had this occur previously, but as in litoris' case I have never called a variable i5 so it definitely occurs with other variable names, too. What causes it I have no idea.

I've also had this happening quite a lot. I'm unfortunately not sure what happened just like the others :P I believe it usually happens when making huge procedures/functions with multiple loops. Maybe placing some begin/ends wrong and some other stuff without a ; might be the problem. But even then it shouldn't be happening :(

From: J J
I've also had this happening quite a lot. I'm unfortunately not sure what happened just like the others :P I believe it usually happens when making huge procedures/functions with multiple loops. Maybe placing some begin/ends wrong and some other stuff without a ; might be the problem. But even then it shouldn't be happening :(

I got it for the first time when I had a case statement inside another, perhaps the loops cause this.

Sorry for gravedig, but I had the same issue as JJ.

I found thesolution.

Make sure when you're assigning variables, you use semicolons.

//BAD
i := 1

//GOOD
i := 1;

Worked for me. Was annoying me to no end.