Author Topic: Bug: CodeCompletion  (Read 7156 times)

Alturin

  • Guest
Bug: CodeCompletion
« on: January 09, 2007, 10:18:59 pm »
Steps to reproduce:
1) Create new project or open an old one.
2) Add the attached file.
3) Save

Now, you'll notice that when in the anotherTest() function it will show in the Code Completion bar as still being in the test() function.
Also, the combo box only has two available functions, main() and test().
When adding any additional functions below test(), they will not appear, instead, it will keep saying test().

Adding a space between the " and ", thus making:
Code
printf("" "");
solves the problem.

Adding any text between either braces does not change this.

I hope this was helpful,

Alturin.

[attachment deleted by admin]

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5491
Re: Bug: CodeCompletion
« Reply #1 on: January 09, 2007, 11:07:26 pm »
the parsing get crazy on those quotes I guess.
I think the code is not even correct.

Quote
printf    function

int printf ( const char * format, ... );

   

<cstdio>

Print formatted data to stdout

Writes to the standard output (stdout) a sequence of data formatted as the format argument specifies. After the format parameter, the function expects at least as many additional arguments as specified in format.

Parameters

format
    String that contains the text to be written to stdout.
    It can optionally contain embedded format tags that are substituted by the values specified in subsequent argument(s) and formatted as requested.
    The number of arguments following the format parameters should at least be as much as the number of format tags.
    The format tags follow this prototype:

    %[flags][width][.precision][length]specifier
    Where specifier is the most significant one and defines the type and the interpretation of the value of the coresponding argument:
    specifier   Output   Example
    c   Character   a
    d or i   Signed decimal integer   392
    e   Scientific notation (mantise/exponent) using e character   3.9265e+2
    E   Scientific notation (mantise/exponent) using E character   3.9265E+2
    f   Decimal floating point   392.65
    g   Use the shorter of %e or %f   392.65
    G   Use the shorter of %E or %f   392.65
    o   Signed octal   610
    s   String of characters   sample
    u   Unsigned decimal integer   7235
    x   Unsigned hexadecimal integer   7fa
    X   Unsigned hexadecimal integer (capital letters)   7FA
    p   Pointer address   B800:0000
    n   Nothing printed. The argument must be a pointer to a signed int, where the number of characters written so far is stored.   
    %   A % followed by another % character will write % to stdout.

    The tag can also contain flags, width, .precision and modifiers sub-specifiers, which are optional and follow these specifications:

    flags   description
    -   Left-justify within the given field width; Right justification is the default (see width sub-specifier).
    +   Forces to preceed the result with a plus or minus sign (+ or -) even for positive numbers. By default, only negative numbers are preceded with a - sign.
    (space)   If no sign is going to be written, a blank space is inserted before the value.
    #   Used with o, x or X specifiers the value is preceeded with 0, 0x or 0X respectively for values different than zero.
    Used with e, E and f, it forces the written output to contain a decimal point even if no digits would follow. By default, if no digits follow, no decimal point is written.
    Used with g or G the result is the same as with e or E but trailing zeros are not removed.
    0   Left-pads the number with zeroes (0) instead of spaces, where padding is specified (see width sub-specifier).

    width   description
    (number)   Minimum number of characters to be printed. If the value to be printed is shorter than this number, the result is padded with blank spaces. The value is not truncated even if the result is larger.
    *   The width is not specified in the format string, but as an additional integer value argument preceding the argument thas has to be formatted.

    .precision   description
    .number   For integer specifiers (d, i, o, u, x, X): precision specifies the minimum number of digits to be written. If the value to be written is shorter than this number, the result is padded with leading zeros. The value is not truncated even if the result is longer. A precision of 0 means that no character is written for the value 0.
    For e, E and f specifiers: this is the number of digits to be printed after de decimal point.
    For g and G specifiers: This is the maximum number of significant digits to be printed.
    For s: this is the maximum number of characters to be printed. By default all characters are printed until the ending null character is encountered.
    For c type: it has no effect.
    When no precision is specified, the default is 1. If the period is specified without an explicit value for precision, 0 is assumed.
    .*   The precision is not specified in the format string, but as an additional integer value argument preceding the argument thas has to be formatted.

    length   description
    h   The argument is interpreted as a short int or unsigned short int (only applies to integer specifiers: i, d, o, u, x and X).
    l   The argument is interpreted as a long int or unsigned long int for integer specifiers (i, d, o, u, x and X), and as a wide character or wide character string for specifiers c and s.
    L   The argument is interpreted as a long double (only applies to floating point specifiers: e, E, f, g and G).

additional arguments
    Depending on the format string, the function may expect a sequence of additional arguments, each containing one value to be inserted instead of each %-tag specified in the format parameter, if any. There should be the same number of these arguments as the number of %-tags that expect a value.

Return Value
On success, the total number of characters written is returned.
On failure, a negative number is returned.
However gcc seems to accept it, I think the code is incorrect.

So it should be printf("\"\"");
And then everything works fine again.

So not that big a problem, a compiler also halts after certain syntax errors, because the parser isn't able to make any sense out of it.[But maybe we can do better, but low priority I would say]
« Last Edit: January 10, 2007, 12:13:14 am by killerbot »

Offline Ceniza

  • Developer
  • Lives here!
  • *****
  • Posts: 1441
    • CenizaSOFT
Re: Bug: CodeCompletion
« Reply #2 on: January 09, 2007, 11:32:42 pm »
Well, using two or more strings, one after each other, looks a bit weird, and in most cases it's completely unnecessary, but in fact all it does is to concatenate them. A case where you would maybe like to use it is when you have newlines in the string, like this:

Code
printf
(
  "First line.\n"
  "Second line.\n"
  "Third line.\n"
  "Last line.\n"
  "A number %d.\n", 123
);

The plugin is failing when nothing separates both strings (space, newline, ...), making it a bug... a minor one.

Alturin

  • Guest
Re: Bug: CodeCompletion
« Reply #3 on: January 10, 2007, 12:54:50 am »
Aye, it is a bit of silly code, and I didn't write it myself, but it was in a code base I'm using, in which it'd be annoying at the least, to have to search for all occurrences of that.
Would be great if it'd get fixed :).

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: Bug: CodeCompletion
« Reply #4 on: January 10, 2007, 11:16:21 am »
Bug fixed.
Be patient!
This bug will be fixed soon...

Alturin

  • Guest
Re: Bug: CodeCompletion
« Reply #5 on: January 10, 2007, 05:08:33 pm »
Bug fixed.

 :mrgreen:
*worships* Totally awesome!
Anyone saying the C::B team doesn't work hard enough should burn their box  :D.

sethjackson

  • Guest
Re: Bug: CodeCompletion
« Reply #6 on: January 10, 2007, 07:04:49 pm »
Bug fixed.
Anyone saying the C::B team doesn't work hard enough should burn their box  :D.

Eww an electrical fire. :lol: