Results 1 to 7 of 7

Thread: Extremely weird variable: i5

  1. #1
    Join Date
    Jan 2012
    Posts
    2,568
    Mentioned
    35 Post(s)
    Quoted
    356 Post(s)

    Default Extremely weird variable: i5

    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.
    Simba Code:
    program new;
    var
      i5: Integer;

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

  2. #2
    Join Date
    Jul 2011
    Location
    /home/litoris
    Posts
    2,226
    Mentioned
    0 Post(s)
    Quoted
    159 Post(s)

    Default

    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.
    Miner & Urn Crafter & 07 Chicken Killer
    SPS BlindWalk Tutorial

    Working on: Nothing

    teacher in every art, brought the fire that hath proved to mortals a means to mighty ends

  3. #3
    Join Date
    Jan 2012
    Posts
    2,568
    Mentioned
    35 Post(s)
    Quoted
    356 Post(s)

    Default

    Quote Originally Posted by litoris View Post
    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?

  4. #4
    Join Date
    Apr 2012
    Location
    Australia
    Posts
    1,252
    Mentioned
    1 Post(s)
    Quoted
    22 Post(s)

    Default

    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.

  5. #5
    Join Date
    Dec 2011
    Location
    The Netherlands
    Posts
    1,631
    Mentioned
    47 Post(s)
    Quoted
    254 Post(s)

    Default

    Quote Originally Posted by P1ng View Post
    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

    Script source code available here: Github

  6. #6
    Join Date
    Jul 2011
    Location
    /home/litoris
    Posts
    2,226
    Mentioned
    0 Post(s)
    Quoted
    159 Post(s)

    Default

    Quote Originally Posted by J J View Post
    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.
    Miner & Urn Crafter & 07 Chicken Killer
    SPS BlindWalk Tutorial

    Working on: Nothing

    teacher in every art, brought the fire that hath proved to mortals a means to mighty ends

  7. #7
    Join Date
    Mar 2012
    Location
    127.0.0.1
    Posts
    3,383
    Mentioned
    95 Post(s)
    Quoted
    717 Post(s)

    Default

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

    I found thesolution.

    Make sure when you're assigning variables, you use semicolons.
    Simba Code:
    //BAD
    i := 1

    Simba Code:
    //GOOD
    i := 1;

    Worked for me. Was annoying me to no end.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •