[Vm-dev] limiting compiler warnings...

stephane ducasse stephane.ducasse at gmail.com
Wed Mar 21 08:45:04 UTC 2012

>> I am quickly trying to limit the number of warnings we get when compiling cog.
>> The current output is amazingly verbose, and utterly useless when looking for possible bugs :/.
>> Furthermore it seems that cared about the following warning:
>> /Users/cami-data/education/phd/project/cog/dh83s-blessed/src/vm/gcc3x-cointerp.c:2066: warning: passing argument 1 of ?longAt? makes integer from pointer without a cast
>> what would be the easiest way to introduce an auto-cast for longAt and family?
>> I think the easiest solution would be to reintroduce the macros that are currently disabled, no?
> That is a Really Bad Idea. If the warnings are bothering you, then just
> relax and have a cup of tea. But they exist for a reason, and if you
> ever want to get the type declarations right, you will want to pay
> attention to the what the compiler is telling you. If you think there
> are too many warnings, then put your energy into addressing the type
> declaration issues that produce the warnings.


(non aggressive) Are vm maintainers interested in getting less warning?
Because then it would be really a nice effort to push.


More information about the Vm-dev mailing list