User forums > Nightly builds

The 17 May 2012 build (7966) is out.

<< < (3/15) > >>

NilC:
Four things:

0. Sorry for my English

1. C++11 & AStyle bug
As you surely know, there is "range-based for loop" in C++11:
for (int & x : a)
{
}

AStyle think that it's a label, because of colons and places it in the beginning of the line, so...
file "ASBeautifier.cpp" line "2376"
else if (isJavaStyle() && lastLineHeader == &AS_FOR)
The condition "isJavaStyle()" is no longer needed.

2. "Activate Project" Command

I have about 10 projects in workspace, when I activate some project - sometimes code::blocks freeze for ~5 second, once it freeze forever.
This bug appeared in nightly builds, following the 7790 (7790 if fine). I'm already posts info about this bug, but no one cares :)
Trying to fix by myself.

3. O_o WTF??

Guys, why the hell do you using targets (like Debug, Release, Win32, Linux in normal way) instead of using projects?

oBFusCATed:

--- Quote from: NilC on May 19, 2012, 12:44:12 am ---Guys, why the hell do you using targets (like Debug, Release, Win32, Linux in normal way) instead of using projects?

--- End quote ---
What targets?
You're free to use whatever fits your way of doing things...

NilC:

--- Quote from: oBFusCATed on May 19, 2012, 01:20:09 am ---
--- Quote from: NilC on May 19, 2012, 12:44:12 am ---Guys, why the hell do you using targets (like Debug, Release, Win32, Linux in normal way) instead of using projects?

--- End quote ---
What targets?
You're free to use whatever fits your way of doing things...

--- End quote ---

Putting all code in a one pot, and then get some of its parts with the targets - it's a perversion IMHO (But I'm not alone who think so).
Take a look (~350 KB)
http://dl.dropbox.com/u/58962113/Bru.png
http://dl.dropbox.com/u/58962113/CodeBlocks.png

oBFusCATed:
No one stops you from using a single target. At work I do just that.
I don't see a problem here.

MortenMacFly:

--- Quote from: oBFusCATed on May 19, 2012, 08:24:53 am ---I don't see a problem here.

--- End quote ---
I don't, too. In the C::b project case, it bundles nicely related SDK libs, the SDK itself, the main app and some plugins into one project. The build order is from top to bottom and if you want, you can select just several targets of those using virtual targets (what we do). So this is another, but valid concept how to use targets. You don't have to do it that way, of course. All contrib plugins do it different for example.

Navigation

[0] Message Index

[#] Next page

[*] Previous page