Hi,
Sean has left the following comment at Research offset macro consolidation
http://www.google-melange.com/gci/task/view/google/gci2012/8172202:
maybe OBE
Frankly, with non k&r compilation, there may no longer be a real
distinction between getting the offset of the first element and the name of
the array. If that's the case for a variety of compilers, then the array
macro may simply get replaced with the non-array version. That said, this
could be more complex than it seems on the surface. Try creating a struct
with bitfields and non-byte-aligned values so that internal padding may
result. Then see if the offsets are still the same.
As for your second question, yes. sizeof() is meant to be sizeof(type)
where type is inferred if you provide a variable but it's still based
around the type, not the variable/address/whatever.
Greetings,
The Google Open Source Programs Team
---
You are receiving this message because you are subscribed to Research
offset macro consolidation.
To stop receiving these messages, go to:
http://www.google-melange.com/gci/task/view/google/gci2012/8172202.
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
BRL-CAD Tracker mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-tracker
