From -4711816320985422378 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,24d6aa350e7865ed X-Google-Attributes: gidf78e5,public X-Google-ArrivalTime: 2002-01-14 08:31:27 PST Path: archiver1.google.com!news2.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!dispose.news.demon.net!news.demon.co.uk!demon!mail2news.demon.co.uk!not-for-mail From: "Scott Robert Ladd" Newsgroups: comp.std.c++ Subject: Re: Memory layout of an object Date: Mon, 14 Jan 2002 16:28:34 GMT Organization: RoadRunner - TampaBay Approved: Fergus Henderson , moderator of comp.std.c++ Message-ID: References: X-Trace: mail2news.demon.co.uk 1011025719 mail2news:1861 mail2news mail2news.demon.co.uk X-Complaints-To: abuse@demon.net X-Mail2News-Path: news.demon.net!mulga.cs.mu.oz.au X-Authentication-Warning: mulga.cs.mu.OZ.AU: fjh set sender to devnull@stump.algebra.com using -f X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 NNTP-Posting-Date: Mon, 14 Jan 2002 11:27:08 EST Lines: 23 Xref: archiver1.google.com comp.std.c++:9014 > is the memory layout (data, function pointers) of an object of a class ISO > specified? No. This is probably due to the platform-independence of POD representations and function semantics; i.e., the ISO standard can't say that an "int" looks a certain way in memory because an "int" may vary in definition between platforms. -- Scott Robert Ladd Master of Complexity, Destroyer of Order and Chaos Visit CoyoteGulch at http://www.coyotegulch.com No ads -- just info, algorithms, and very free code. --- [ comp.std.c++ is moderated. To submit articles, try just posting with ] [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://www.research.att.com/~austern/csc/faq.html ]