{
bool ok = true;
for(auto it: events)
ok = ok && this->subscribeEvent(elem, it);
return ok;
}
Index: src/plugins/astyle/astyle/ASBeautifier.cpp
===================================================================
--- src/plugins/astyle/astyle/ASBeautifier.cpp (revision 7900)
+++ src/plugins/astyle/astyle/ASBeautifier.cpp (working copy)
@@ -2373,9 +2373,9 @@
tabCount += classInitializerTabs;
}
- else if (isJavaStyle() && lastLineHeader == &AS_FOR)
+ else if ((isJavaStyle() || isCStyle()) && lastLineHeader == &AS_FOR)
{
- // found a java for-each statement
+ // found a java/C++0x for-each statement
// so do nothing special
}
Is this something that should be submitted to Code::Block's patch tracker, or to the actual AStyle project?This is astyle, not Code::Blocks. However, you should first look at the astyle code whether this has probably been fixed already. You can integrate later versions of astyle easily into Code::Blocks, just make sure you keep these two methods in the public section:
However, you should first look at the astyle code whether this has probably been fixed already.You were right; I checked the AStyle project, and it appears this problem has already been fixed. Patch #3268 (https://developer.berlios.de/patch/index.php?func=detailpatch&patch_id=3268&group_id=5358) updates Code::Blocks to this.
Patch #3268 (https://developer.berlios.de/patch/index.php?func=detailpatch&patch_id=3268&group_id=5358) updates Code::Blocks to this.You don't need to provide patches - I am maintaining this already, but thanks anyways.
Just wondering, is this commited upstream now?No, whats missing is the integration of the new features to the UI.
Just wondering, is this commited upstream now?No, whats missing is the integration of the new features to the UI.
I may do an interim-commit, but this would mean that you cannot setup all features.
Isn't this just a small patch for supporting these new-style lopps?Yes.