I would like us to move towards less obfuscation.
my $0.02CDN
On Thu, Jun 28, 2012 at 4:01 AM, JMGross <msp...@grossibaer.de> wrote:
> ----- Ursprüngliche Nachricht -----
> Von: Peter Bigot
> Gesendet am: 27 Jun 2012 16:36:58
>
> >> P.s.: I also wish all this TIMER1_VECTOR/TIMER0_A1_VECTOR
> >> confusion would vanish from the header files.
>
> > That's been fixed as much as it can be. See:
> >
> https://sourceforge.net/tracker/?func=detail&aid=3484369&group_id=42303&atid=432701
> > Since this was done upstream, it should also be available in future
> > IAR and CCS releases.
>
> Yes, that allows the "new" style to be used on older devices without
> breakign existing code.
> It does not, however, fix the problem that people, seeing the old code
> examples, fail to
> use them on their newer devices or on Timer A1.
> I don't see a good way to do it.
> It's a shame that you cannot include preprocessor directives into a macro,
> or else you could
> issue a warning whereever the old vector names are used.
>
> > Now all we need to do is convince TI not to hard-code device-specific
> > headers in their generic examples, e.g. for the Launchpad. AFAICT
> > <msp430.h> ought to work for everybody.
>
> While using MSP430.H is convenient, I don't like it at all.
> The simple reason is that usign this generic header hides
> the device the code was written for.
>
> If you change the project settings to another device, the
> header will auto-switch and you'll get lots of errors and
> don't know why.
>
> Also, when posting such a code (or an example code), then
> it obfuscates problems caused by device mismatching, and
> makes an analysis even more difficult.
> I have to battle this every now and then in the E2E forum.
>
> Including a dedicated header removes much ambiguity from
> the code.
>
> JMGross
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Mspgcc-users mailing list
> Mspgcc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>
--
Eric B. Decker
Senior (over 50 :-) Researcher
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
