User forums > Nightly builds
The 02 November 2012 build (8500) is out.
oBFusCATed:
--- Quote from: MortenMacFly on November 04, 2012, 05:31:07 pm ---No, why should I?
--- End quote ---
Because you're writing non-standard code which will break with another compiler, which doesn't support GCC extensions probably.
MortenMacFly:
--- Quote from: oBFusCATed on November 04, 2012, 06:26:35 pm ---Because you're writing non-standard code which will break with another compiler, which doesn't support GCC extensions probably.
--- End quote ---
OK - but I don't want to use another compiler and use several GCC extensions already because they are handy. But yes - its surely a portability issue.
carra:
I can confirm that the fix for custom abbreviations is working correctly now: the empty extra lines are no longer inserted due to Windows line terminators "\r\n".
However, this bug persists when the abbreviations are using scripts! I don't really know why, since I thought script execution should be unaffected by this.
For instance, if you write this abbreviation under Windows (using the windows EOL):
--- Code: ---[[ print("*line 1*\r\n*line 2*"); ]]
--- End code ---
CodeBlocks 8500 prints the following:
--- Code: ---*line 1*
*line 2*
--- End code ---
While 8248 and previous correctly printed
--- Code: ---*line 1*
*line 2*
--- End code ---
Should I now change my scripts to Linux EOL '\n'? (and hope it won't break EOL consistency in my files)
EDIT: I have verified that the bug, however, does not happen if you execute that script line in the script console. So it has to do with abbreviations instead
Alpha:
--- Quote from: carra on November 05, 2012, 03:14:33 pm ---However, this bug persists when the abbreviations are using scripts! I don't really know why, since I thought script execution should be unaffected by this.
--- End quote ---
That does not make sense... I will see if I can figure out why.
--- Quote from: carra on November 05, 2012, 03:14:33 pm ---Should I now change my scripts to Linux EOL '\n'? (and hope it won't break EOL consistency in my files)
--- End quote ---
Yes, this is the recommended (by me ;)) method; code generation will match the editor's current EOL style just before insertion (if you would like to double check, set EditorTweaks to show EOL characters).
shurick:
Packages for openSUSE 12.1, openSUSE 12.2 (binaries and sources) for 32-bit and 64-bit.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version