User forums > Nightly builds

The 09 October 2010 build (6688) CODECOMPLETION BRANCH version is out.

<< < (8/9) > >>

blueshake:
try recompile the whole source ,even the plugins.please

Zadirion:
Hello,

Using r6688 CC branch on Windows 7 x64.
Found the following issue, I hope I'm posting this in the correct thread:
Steps:
- Settings->Editor->Code Completion and Symbols browser page->C/C++ parser tab->Add button under Replacement tokens section
- add the following replacement token:

--- Code: ---Key: BEGIN_NAMESPACE(CryptoPP)
Value: namespace CryptoPP{

--- End code ---
- close CodeBlocks
- reopen CodeBlocks, it should crash with the following exception:

--- Code: ---
---------------------------
Exception
---------------------------
An exception has been raised!

The application encountered an error at E:\CodeBlocks\branches\codecompletion_refactoring\src\sdk\configmanager.cpp, on line 239.
The error message is:

TinyXML error: Error reading Attributes.
In file: C:\Users\Zadirion\AppData\Roaming\codeblocks\default.conf
At row 902, column: 33.

Code::Blocks Version revision 6688 (gcc 4.4.1, build: Oct  9 2010 11:48:56)
---------------------------
OK   
---------------------------

--- End code ---
I believe these are the offending lines added in default.conf?

--- Code: ---
<BEGIN_NAMESPACE(CryptoPP)>
<![CDATA[namespace CryptoPP{]]>
</BEGIN_NAMESPACE(CryptoPP)>

--- End code ---
Perhaps they should be properly escaped when added to the xml.


Also, when are the CodeCompletion and Debugger branches scheduled for merge into trunk? CodeCompletion is finaly able to properly parse the CryptoPP library, and the debugger can finaly show me where the exception was thrown, along with a useful call stack. I can't use one branch or the other because both are very useful for an efficient developing session.

Thanks

Jenna:

--- Quote from: Zadirion on October 24, 2010, 11:27:11 am ---Also, when are the CodeCompletion and Debugger branches scheduled for merge into trunk? CodeCompletion is finaly able to properly parse the CryptoPP library, and the debugger can finaly show me where the exception was thrown, along with a useful call stack. I can't use one branch or the other because both are very useful for an efficient developing session.

--- End quote ---

--- Quote from: jens on October 22, 2010, 12:16:06 am ---
--- Quote from: Folco on October 22, 2010, 12:12:16 am ---Perhaps the branch have been commited ? :)

--- End quote ---
Yes, use trunk instead.

--- End quote ---
and

--- Quote from: killerbot on October 23, 2010, 10:38:22 pm ---[...]
The 23 October 2010 build is out.
[...]

* MERGED ALL THE CODE COMPLETION CHANGES DEVELOPED ON THE CC BRANCH !!!
--- End quote ---

That means cc is in trunk, debugger branch is not yet merged.

Zadirion:
Sweet. Any idea when the debugger branch would be merged?
In the meantime i'm stuck using the debugger branch since I find its debugging features to be of more importance then the code completion improvements on the CC branch.

Best regards,
Eddie

oBFusCATed:
Zadirion: trunk+CC are now merged in the debugger's branch, so the improvements in CC are now in the branch :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page