-
A work-around for the specific symptom is using
&rm -f $(subst #,\#,$(wildcard **/*.gcov))
2009-07-01 07:20:06 UTC in makepp
-
When one uses gcov with the option --long-file-name it creates coverage files for includes like the following ones:
source1.cpp##include1.hpp.gcov
source1.cpp##include2.hpp.gcov
source2.cpp##include1.hpp.gcov
source2.cpp##include2.hpp.gcov
Trying to delete them using a
&rm -f $(wildcard **/*.gcov)
results in deleting the first source (source1.cpp) while leaving all...
2009-06-30 08:53:38 UTC in makepp
-
C/C++ bit fields are (incorrectly) treated like labels:
struct A {
int a:1;
};
will become something like
struct A {
int a:
1;
};
instead of keeping the "1;" in the same row. This is
identical behavior to the original AStyle, see their
bug report 1238641 as reference (including a hacked
solution proposal by me).
2006-11-07 12:09:27 UTC in Astyle Eclipse plugin
-
When I try to add the "other option" --unpad=paren I
get an "option error". The whole option set (which I
copied from a script used elsewhere with the C++
version of AStyle) is
--style=ansi
--indent-switches
--indent-labels
--indent-namespaces
--pad=oper
--unpad=paren
--one-line=keep-blocks
--convert-tabs
--mode=c
The option seemed to appear in one of the newer version...
2006-11-07 11:42:44 UTC in Astyle Eclipse plugin
-
In our sources we use a macro UNALIGNED to mask
compiler specific attributes in declarations, e.g. with
g++:
#define UNALIGNED __attribute__((__packed__))
If we use this in structures like the following the
code is broken by GC:
struct Bit_mask {
unsigned short flag1:1 UNALIGNED;
unsigned short flags2:2 UNALIGNED;
unsigned short flags3:3 UNALIGNED;
};
will be...
2006-08-22 14:10:10 UTC in GC GreatCode
