The 28 May 2014 build (9781) is out.

[stahta01]

You mean:
http://www.dribin.org/dave/blog/archives/2010/05/15/c99_syntax/

Code Select Expand


NSPoint point = { .x = 0, .y = 0};

?

Yes, exactly.

1, we should know it is an initialization statement.
2, we are after the dot.
3, we are in a C file, but we have C99 option enabled.

The hardest part is 1. How do we locate that we are in an C stile initialization? Currently, CC only remember the "{}" pair for function bodies and class definition.

As far as I know, GCC currently has C99/C11 features added (enabled?) in C by default and currently waiting to incorporate C11 as their default flag.

Should not it work since point #3 is partially available by default?

Feel free to submit a patch for CB's CC (Code Completion) if you think it is so easy to do.

Tim S.

[ToApolytoXaos]

Feel free to submit a patch for CB's CC (Code Completion) if you think it is so easy to do.

Tim S.

I can't see anywhere I mention such thing; I just asked. there's no need to be sarcastic.

[ollydbg]

Feel free to submit a patch for CB's CC (Code Completion) if you think it is so easy to do.
Tim S.

I can't see anywhere I mention such thing; I just asked. there's no need to be sarcastic.

Hi, ToApolytoXaos, I don't understand this sentence.

Should not it work since point #3 is partially available by default?

, can you explain more?

Our CodeCompletion plugin has its own parser, the parser does not have the scale as a normal compiler's parser (parser in gcc or clang). I think it was not quite easy to add the feature you request, it is doable, but the developers(include me) are focus to fix other parts of CC which I think is more important. So, we welcome any contribute to CC. 

[ToApolytoXaos]

I was referring at the "if you think it is so easy to do" part. I did not ask for anything; all I needed was more info, academically-wise you could say, that's all.

As far as I know certain features like for example // single line comments are permitted as also the aforementioned structure example. I did not use any flags and was able to compile just fine.

What puzzled me was the suggestion list that would include only C++ keywords and not a single C word at all; that's why I have asked for more information. I did not come here to play the wise guy or to start an unnecessary argument.

Sometimes a literal translation from one language to another can lead to such misinterpretations and most of the time instead of investing time and efford to resolve issues and bugs, let alone share ideas, we waste it to argue who said what and why having as a result to kill the educating (sharing) spirit in favor of ego.

That's just sad I would say...a lot!

[stahta01]

What puzzled me was the suggestion list that would include only C++ keywords and not a single C word at all; that's why I have asked for more information. I did not come here to play the wise guy or to start an unnecessary argument.

You came here to waste bandwidth on topics not valid in this sub forum!

If you wish to discuss or suggest new feature this thread and sub-forum is NOT the correct place!

This thread is for new bugs in this nighty build. And, other questions and info related to this nighty build.

It is NOT a general thread about using CB or request of new features!

Tim S. 

[ToApolytoXaos]

I understand.

You could say this from the start in a good way by the way; no need to sound harsh or aggressive.

No wonder why people are scared to ask questions in here.

[nanyu]

url link doesn't work :
click    http://prdownload.berlios.de/codeblocks/CB_20140528_rev9781_win32.7z
will open the web "http://www.berlios.de/"  homepage only。


--
firefox 29.01 / IE 11

It looks like the whole https://developer.berlios.de/projects/codeblocks/ was down. They have said before, see: berlios will close project host in 2014.04


EDIT
You can download the bin files from mirror sites: http://sourceforge.net/projects/codeblocks.berlios/files/

Thanks!
But why we still use a old url link in this page?

[q4a]

Hi all.

I'm using Lubuntu (LXDE on Ubuntu) 14.04 amd64 fresh installed. I have installed C::B 13.12 from Ubuntu official repo, but it crashed few times and I decided to test Nightly builds.
I tested rev 9781 from PPA for pasgui and rev 9791 from Jens repo - both has problem with Ctrl-C and Ctrl-V.
Copy and Paste works from toolbar and I can undo changes with Ctrl-Z, but Copy and Paste with Ctrl-C and Ctrl-V does not work.

Should I create ticket to SF or it's known problem or it's problem with my system?

[Aleksandr]

Since there was no answer, I will ask here because I use this nightly build. Can it be considered a bug, the behavior of the program described in this topic?
http://forums.next.codeblocks.org/index.php/topic,19256.0.html

[oBFusCATed]

Please don't cross-post!

[ToApolytoXaos]

svn9817 compiled with GCC 4.9.0 on Debian testing (64-bit) had just crashed while typing a macro in C.

I presume it has something to do with the parser, because it would not let me include any structure member while pressing dot or Ctrl-Space. I have reparsed it and still nothing.

Code Select Expand

<?xml version="1.0" encoding="utf-8"?>
<report version="1.0" kind="exception">
 <system description="Linux 3.14-1-amd64 x86_64"/>
  ...
  ... [ deleted unnecessary modules to save space ]
  ...
 <stack>
   <frame level="0"/>
   <frame level="1" function="wxsResourceTree::InvalidateItemData(wxsResourceTreeItemData*)" offset="00000010"/>
   <frame level="2" function="wxsResourceTreeItemData::~wxsResourceTreeItemData()" offset="00000036"/>
   <frame level="3"/>
   <frame level="4"/>
   <frame level="5" function="wxGenericTreeItem::~wxGenericTreeItem()" offset="00000016"/>
   <frame level="6" function="wxGenericTreeItem::DeleteChildren(wxGenericTreeCtrl*)" offset="0000002d"/>
   <frame level="7" function="wxGenericTreeCtrl::Delete(wxTreeItemId const&amp;)" offset="00000106"/>
   <frame level="8" function="wxGenericTreeCtrl::DeleteAllItems()" offset="00000023"/>
   <frame level="9" function="wxGenericTreeCtrl::~wxGenericTreeCtrl()" offset="00000050"/>
   <frame level="10" function="wxTreeCtrl::~wxTreeCtrl()" offset="00000043"/>
   <frame level="11" function="wxsResourceTree::~wxsResourceTree()" offset="00000061"/>
   <frame level="12" function="wxsResourceTree::~wxsResourceTree()" offset="00000018"/>
   <frame level="13" function="wxWindowBase::DestroyChildren()" offset="00000026"/>
   <frame level="14" function="wxWindow::~wxWindow()" offset="00000062"/>
   <frame level="15" function="wxPanel::~wxPanel()" offset="00000009"/>
   <frame level="16" function="wxWindowBase::DestroyChildren()" offset="00000026"/>
   <frame level="17" function="wxWindow::~wxWindow()" offset="00000062"/>
   <frame level="18" function="wxSplitterWindow::~wxSplitterWindow()" offset="00000009"/>
   <frame level="19" function="wxWindowBase::DestroyChildren()" offset="00000026"/>
   <frame level="20" function="wxWindow::~wxWindow()" offset="00000062"/>
   <frame level="21" function="wxsStoringSplitterWindow::~wxsStoringSplitterWindow()" offset="0000002a"/>
   <frame level="22" function="wxsStoringSplitterWindow::~wxsStoringSplitterWindow()" offset="00000018"/>
   <frame level="23" function="wxWindowBase::Destroy()" offset="0000000f"/>
   <frame level="24" function="wxAuiNotebook::DeletePage(unsigned long)" offset="000000b4"/>
   <frame level="25" function="wxAuiNotebook::~wxAuiNotebook()" offset="00000032"/>
   <frame level="26" function="cbAuiNotebook::~cbAuiNotebook()" offset="00000053"/>
   <frame level="27" function="cbAuiNotebook::~cbAuiNotebook()" offset="00000018"/>
   <frame level="28" function="wxWindowBase::DestroyChildren()" offset="00000026"/>
   <frame level="29" function="wxWindow::~wxWindow()" offset="00000062"/>
   <frame level="30" function="MainFrame::~MainFrame()" offset="00000000" file="/home/stefanos/svn_code/CodeBlocks/src/src/main.cpp" line="660"/>
   <frame level="31" function="MainFrame::~MainFrame()" offset="00000000" file="/home/stefanos/svn_code/CodeBlocks/src/src/main.cpp" line="660"/>
   <frame level="32" function="wxAppBase::CleanUp()" offset="00000036"/>
   <frame level="33" function="wxEntryCleanup()" offset="00000050"/>
 </stack>
</report>


[oBFusCATed]

Seems like a wxsmith related crash...

[nasty_wolverine]

Note, most likely rev 9575 is the cause; I do not have time to look into it right now, so consider reverting if it is not an easy fix.

Regarding the autoformat/indent not working properly, i think i figured out whats making that happen. its the return characters(^M). when i was editing the same files with vim/emacs, i noticed that most of the places where autoformat was screwing up was where the return characters were (the code was carried over from a previous visual studio project). So i guess autoformat cant handle ^M and that throws it off.

[ToApolytoXaos]

Seems like a wxsmith related crash...

That's weird; I'm not using wxSmith at all. It's a plain C console application, made long time ago with "Empty Project".

[nasty_wolverine]

Note, most likely rev 9575 is the cause; I do not have time to look into it right now, so consider reverting if it is not an easy fix.

Regarding the autoformat/indent not working properly, i think i figured out whats making that happen. its the return characters(^M). when i was editing the same files with vim/emacs, i noticed that most of the places where autoformat was screwing up was where the return characters were (the code was carried over from a previous visual studio project). So i guess autoformat cant handle ^M and that throws it off.

sorry, apparently not. still happens after i have removed those symbols.