Hi Mark. On Sat, 17 Jan 2015 11:11:18 -0500, Mark Odell wrote: > Nice but I'd suggest looking more ANSI and having a consistent naming > scheme that better reflects the type...
You're correct, but personally I prefer a more 'shorthand' variable name, which does not add an extra 'dot' to the variable. At maximum, I'd use .s8 and .u8 myself, mainly because I find that ... *d8++ = *s8++; ... more appealing (and easier on my eyes) than ... *d.uint8_p++ = *s.uint8_p++; ... but I do agree, its' more correct and makes it more clear what's going on, if some type info is given. (and I think it's also a good idea to only include for instance uint8_t and sint32_t in a structure, if those are the only types allowed in there). Love Jens ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
