User forums > Using Code::Blocks

First impression of C::B - Perforce and Intel Fortran issues

<< < (3/3)

Jenna:

--- Quote from: pclausen on November 23, 2010, 05:52:18 pm ---Its been a while - and I still like Code::Blocks   :D

--- End quote ---
Nice to hear !


--- Quote from: pclausen on November 23, 2010, 05:52:18 pm ---Still, Code::Blocks chokes on the "line 0"

--- End quote ---

I don't see a possibility to do anything other.
If C::B does not get a valid line-number it can not jump to the error.
In this cases (line <= 0) the DoGotoError-function just returns.

The regexes are saved in ~/.codeblocks/default.conf on linux.
You can export the compiler-set in question (<compiler><sets><icc> for default Intel C/C++) with cb_share_config and import it on other machines.

Copied (cloned) compiler sets are stored in <compiler><user_sets> .

xunxun:

--- Quote from: pclausen on November 23, 2010, 05:52:18 pm ---Its been a while - and I still like Code::Blocks   :D


--- Quote from: xunxun1982 on November 12, 2010, 04:56:38 pm ---Could you show your some source code? I don't know what "Fortran names are too long"'s meaning is. I think "Fortran names are too long" may occur some error as "This symbol has too many characters".

--- End quote ---

The code is:

--- Code: ---MODULE CELL_RASTER
.....
contains
  subroutine s_get_nd_in_area_gad_brute_force (minp, &
    &                                          maxp)
    use coordinate_transformation
    ...
   end subroutine

--- End code ---

Generates the warning:


--- Code: ---fortcom: Warning: /scratch/users/clausen/Repository/main/development/baseline/source/prog_dev/prog_mod/s_cell_reg.f90, line 0: Global name too long, shortened from: cell_raster_mp_s_get_nd_in_area_gad_brute_force_$BLK.coordinate_transformation_mp_design_cycle_aktuell_ to: ster_mp_s_get_nd_in_area_gad_brute_force_$BLK.coordinate_transformation_mp_design_cycle_aktuell_

--- End code ---
I fixed it by including the USE-statement in the top of module statement - the way it should be! Still, Code::Blocks chokes on the "line 0"




--- End quote ---

Sorry, I can't reproduce your warnning.
I use intel c/c++/fortran compiler 12.

pclausen:

--- Quote from: jens on November 23, 2010, 10:10:21 pm ---
--- Quote from: pclausen on November 23, 2010, 05:52:18 pm ---Still, Code::Blocks chokes on the "line 0"

--- End quote ---

I don't see a possibility to do anything other.
If C::B does not get a valid line-number it can not jump to the error.
In this cases (line <= 0) the DoGotoError-function just returns.

--- End quote ---

hmm, well, I would have expected C::B to go to the file, which it does not. In my humble opinion the behavior should be:

--- Code: --- if (line <=0) {line = 1;}
--- End code ---
. But its no biggy...

Navigation

[0] Message Index

[*] Previous page