Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.advocacy > #88132
| From | Kelsey Bjarnason <kbjarnason@gmail.com> |
|---|---|
| Newsgroups | comp.os.linux.advocacy, comp.os.linux.embedded |
| Subject | Re: Reading the Riot Act To ARM's developers |
| Date | 2012-02-10 21:22 -0800 |
| Organization | A noiseless patient Spider |
| Message-ID | <4iah09-1p2.ln1@spankydtr.localhost.net> (permalink) |
| References | <WGiYq.100467$WX2.28685@newsfe28.ams2> |
Cross-posted to 2 groups.
[snips] On Tue, 07 Feb 2012 23:43:43 +0000, 7 wrote: > Typically the CMSIS library forces you to write code using hard coded > numbers. So you want to set some flag to enable an interrupt it would > read something like > > SYSCON->INT |= (1<<4) > > Here is the crunch, who the hell is going to know if its the 4th bit or > the 14th bit when you got a million of these lines of code? > > Shortest possible answer NOBODY. Not even you!!!!!!!!! > > And then you change CPU, and something changes in hardware, how will you > know what to look for - you gonna search for "4" all throughout the > code????? Are you actually using a tool so bad it doesn't let you define your own symbols? define INT_XMA (1 << 4) ... SYSCON->INT |= INT_XMA Need to change INT_XMA? Change it in one place, *every* usage of it changes. If your development tools can't cope with this - and, ideally, with include files - then you should consider using a macro preprocessor to generate the compilable code from the maintainable code. Either way, has nothing to do with ARM, per se; just to do with an apparently crippled toolchain and/or a developer who can't look beyond the trivial tool to see possible solutions.
Back to comp.os.linux.advocacy | Previous | Next — Next in thread | Find similar
Re: Reading the Riot Act To ARM's developers Kelsey Bjarnason <kbjarnason@gmail.com> - 2012-02-10 21:22 -0800
Re: Reading the Riot Act To ARM's developers 7 <email_at_www_at_enemygadgets_dot_com@enemygadgets.com> - 2012-02-11 09:58 +0000
Re: Reading the Riot Act To ARM's developers David Brown <david.brown@removethis.hesbynett.no> - 2012-02-11 15:16 +0100
Re: Reading the Riot Act To ARM's developers 7 <email_at_www_at_enemygadgets_dot_com@enemygadgets.com> - 2012-02-12 00:56 +0000
Re: Reading the Riot Act To ARM's developers David Brown <david.brown@removethis.hesbynett.no> - 2012-02-12 10:24 +0100
Re: Reading the Riot Act To ARM's developers "Ezekiel" <zeke@nosuchemail.com> - 2012-02-12 08:21 -0500
Re: Reading the Riot Act To ARM's developers 7 <email_at_www_at_enemygadgets_dot_com@enemygadgets.com> - 2012-02-12 19:12 +0000
Re: Reading the Riot Act To ARM's developers Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2012-02-13 08:54 +0200
Re: Reading the Riot Act To ARM's developers David Brown <david@westcontrol.removethisbit.com> - 2012-02-13 09:12 +0100
Re: Reading the Riot Act To ARM's developers Kelsey Bjarnason <kbjarnason@gmail.com> - 2012-02-11 10:34 -0800
csiph-web