Don't forget command line argument obfuscation. That seems to be very important. That, and include paths. Impenetrable.
Cheers,
Don't forget command line argument obfuscation. That seems to be very important. That, and include paths. Impenetrable.
Cheers,
is go so badly broken that it doesn't use the "#line" preprocessor directive to enable source level debugging? or are you making s*it up?
If you check the doc's, they mention that the GCC frontend generates C code, which is all you get for debugging.
I haven't read the docs, so I'll take your word for it. But if that's the case, then it is not a gcc frontend - it's a pre-processor generating C as an intermediary language. That's fair enough - there are several compiler tools that do that, and it's a quick way to make a fairly portable tool. But the terminology they have used on the website is at best misleading.
Of course not. It's a nice symmetry. Previously one could only get confused about the order the parameters. Now scope for confusion about the order of results has been added.
Sylvia.
Have something to add? Share your thoughts — no account required.
Ask the community — no account required