Hi GCC dev team,
I have developed software to parse C(++) code and automatically add
const to function arguments (tracing all functions and their
references). However, I have encountered an issue with the GCC/VS
compilers preventing assignment of typeX** to const typeX**.
Considering that const is
On 5 December 2015 at 11:26, Richard Baxter wrote:
> Hi GCC dev team,
Hi, this is the wrong mailing list for questions seeking help using
GCC, please direct any follow-up to the gcc-help mailing list, thanks.
> I have developed software to parse C(++) code and automatically add
> const to functi
On 12/04/2015 10:32 AM, Tom Tromey wrote:
"Martin" == Martin Sebor writes:
Martin> To get around these, I end up using info macro to print the
Martin> macro definition and using whatever it expands to instead. I
Martin> wonder if someone has found a more convenient workaround.
For some of th
Martin> The one that's more difficult is 18881 where the debugger cannot
Martin> resolve calls to functions overloaded on the constness of the
Martin> argument. Do you happen to have a trick for dealing with that
Martin> one?
Nothing really convenient to use. Sometimes you can get it to do the
r
