Re: Idea for 'documenting' unused values
- Posted by Pete Lomax <petelomax at blueyonder.co.uk> Jul 20, 2004
- 525 views
On Tue, 20 Jul 2004 07:05:54 -0700, Derek Parnell <guest at RapidEuphoria.com> wrote: >Another method is ... > > if func( .. . .) then end if > >But that only works for atomic return values. > <reshuffle> >How many people have ways around all those warnings that are generated >by using Win32lib event handlers? I've even used "if sequence({x,y,z}) then end if" before now... And countless instances of: if integer(self) or integer(event) or sequence(params) then end if vs: ignore({self,event,params}) Much better, but would prefer an inline syntax for unused params... (Any ideas?) >For ignoring parameters we have our good friend 'without warning'. The >problems with this is that it can accidently hide warnings we *are* >concerned about Ugh, bad memories: Early experience on my first job: warnings flashing by ten a penny; guess what, first bug I spent *ages* fixing? The compiler had already warned me and everyone else about, zillions of times. The dipshit I was working for, who had already spent longer than should have been allowed looking for that bug and frankly (if he hasn't been sacked or more likely long since retired by now) would still be looking for to this day, ended up accusing me of breaking the system ... because (and I think you all know what I'm about to say) the warning messages were "wrong" when he recompiled... <shudder> Pete