http://groups.google.com/group/comp.lang.c++?hl=en
comp.lang.c++@googlegroups.com
Today's topics:
* atexit - 10 messages, 2 authors
http://groups.google.com/group/comp.lang.c++/t/ecb78db904bcd136?hl=en
* China factory wholesale NFL,mlb,nhl,nbaJerseys Free Shipping Paypal payment <
www.wtojerseys.com> - 1 messages, 1 author
http://groups.google.com/group/comp.lang.c++/t/f769d521a2fb7599?hl=en
* dealing with lower level programmers - 2 messages, 1 author
http://groups.google.com/group/comp.lang.c++/t/f708a2c0cfa8ce2d?hl=en
* wholesale Oakley goggle www.online-saler.com - 1 messages, 1 author
http://groups.google.com/group/comp.lang.c++/t/02f474200bcf43e8?hl=en
* ╃♡╃♡╃Wholesale Nokia ,Iphone, Samsung, Blackberry, Sony, Motorola,etc brand
mobiles "www.toptradea.com" - 1 messages, 1 author
http://groups.google.com/group/comp.lang.c++/t/f867f91b3c93484d?hl=en
* ===Welcome to comp.lang.c++! Read this first. - 1 messages, 1 author
http://groups.google.com/group/comp.lang.c++/t/2dfad3237cc109dd?hl=en
==============================================================================
TOPIC: atexit
http://groups.google.com/group/comp.lang.c++/t/ecb78db904bcd136?hl=en
==============================================================================
== 1 of 10 ==
Date: Sat, Jul 25 2009 11:53 am
From: "Fraser Ross"
3.6.3/3 tells me what I want to know for non-local static objects but
where is there the same for local static objects?
SomeClass *pObj1(new SomeClass(1));
Loki::SetLongevity(pObj1, 5);
static SomeClass obj2(2);
SomeClass *pObj3(new SomeClass(3));
Loki::SetLongevity(pObj3, 6);
SetLongevity registers the destructors to be called with atexit for
pObj1 and pObj3. What should be the order of destruction?
Fraser.
== 2 of 10 ==
Date: Sat, Jul 25 2009 11:56 am
From: "Fraser Ross"
int main() {
> SomeClass *pObj1(new SomeClass(1));
> Loki::SetLongevity(pObj1, 5);
> static SomeClass obj2(2);
> SomeClass *pObj3(new SomeClass(3));
> Loki::SetLongevity(pObj3, 6);
}
The code is in a function.
Fraser.
== 3 of 10 ==
Date: Sat, Jul 25 2009 12:04 pm
From: "Alf P. Steinbach"
* Fraser Ross:
> 3.6.3/3 tells me what I want to know for non-local static objects but
> where is there the same for local static objects?
>
> SomeClass *pObj1(new SomeClass(1));
> Loki::SetLongevity(pObj1, 5);
> static SomeClass obj2(2);
> SomeClass *pObj3(new SomeClass(3));
> Loki::SetLongevity(pObj3, 6);
>
> SetLongevity registers the destructors to be called with atexit for
> pObj1 and pObj3. What should be the order of destruction?
The order of atexit calls is defined by the standard, the order of destruction
(what those calls do or not) is defined by the Loki library.
As I recall there is full discussion of SetLongevity et.al. in "Modern C++
Design" by Andre Alexandrescu.
To use Loki you really should have that book at hand.
Cheers & hth.,
- Alf
== 4 of 10 ==
Date: Sat, Jul 25 2009 12:32 pm
From: "Fraser Ross"
"Alf P. Steinbach"
>* Fraser Ross:
>> 3.6.3/3 tells me what I want to know for non-local static objects but
>> where is there the same for local static objects?
>>
>> SomeClass *pObj1(new SomeClass(1));
>> Loki::SetLongevity(pObj1, 5);
>> static SomeClass obj2(2);
>> SomeClass *pObj3(new SomeClass(3));
>> Loki::SetLongevity(pObj3, 6);
>>
>> SetLongevity registers the destructors to be called with atexit for
>> pObj1 and pObj3. What should be the order of destruction?
>
> The order of atexit calls is defined by the standard, the order of
> destruction (what those calls do or not) is defined by the Loki
> library.
I know that. I don't know where in the standard that it says how atexit
interacts with local static destruction. Anyway there seems to be a
stack type ordering.
>
> As I recall there is full discussion of SetLongevity et.al. in "Modern
> C++ Design" by Andre Alexandrescu.
>
> To use Loki you really should have that book at hand.
I'm reading it. It doesn't explain every detail. The whole concept of
longevity should really be a death ordering not a lifespan length.
Fraser.
== 5 of 10 ==
Date: Sat, Jul 25 2009 12:58 pm
From: "Alf P. Steinbach"
* Fraser Ross:
> "Alf P. Steinbach"
>> * Fraser Ross:
>>> 3.6.3/3 tells me what I want to know for non-local static objects but
>>> where is there the same for local static objects?
>>>
>>> SomeClass *pObj1(new SomeClass(1));
>>> Loki::SetLongevity(pObj1, 5);
>>> static SomeClass obj2(2);
>>> SomeClass *pObj3(new SomeClass(3));
>>> Loki::SetLongevity(pObj3, 6);
>>>
>>> SetLongevity registers the destructors to be called with atexit for
>>> pObj1 and pObj3. What should be the order of destruction?
>> The order of atexit calls is defined by the standard, the order of
>> destruction (what those calls do or not) is defined by the Loki
>> library.
>
> I know that. I don't know where in the standard that it says how atexit
> interacts with local static destruction.
Searching for 'atexit' immediately landed me on §3.6.3/3.
Essentially the rules ensure that static objects existing when an atexit handler
is registered, still exist when that handler runs (i.e. not yet destroyed).
For the purpose of ordering you might consider an atexit-handler as equivalent
to the destructor of a hypothetical static object, and the registration as
equivalent to a constructor of that static object.
> Anyway there seems to be a stack type ordering.
Yes.
>> As I recall there is full discussion of SetLongevity et.al. in "Modern
>> C++ Design" by Andre Alexandrescu.
>>
>> To use Loki you really should have that book at hand.
> I'm reading it. It doesn't explain every detail. The whole concept of
> longevity should really be a death ordering not a lifespan length.
Huh?
Cheers & hth.,
- Alf
== 6 of 10 ==
Date: Sat, Jul 25 2009 1:12 pm
From: "Fraser Ross"
"Alf P. Steinbach"
> Searching for 'atexit' immediately landed me on §3.6.3/3.
>
> Essentially the rules ensure that static objects existing when an
> atexit handler is registered, still exist when that handler runs (i.e.
> not yet destroyed).
That section only refers to non-local static objects so its irrelevant.
>>> As I recall there is full discussion of SetLongevity et.al. in
>>> "Modern C++ Design" by Andre Alexandrescu.
>>>
>>> To use Loki you really should have that book at hand.
>> I'm reading it. It doesn't explain every detail. The whole concept
>> of longevity should really be a death ordering not a lifespan length.
>
> Huh?
5 and 6 are the death order values. Longevity sounds like a lifespan
measurement.
Fraser.
== 7 of 10 ==
Date: Sat, Jul 25 2009 1:50 pm
From: "Alf P. Steinbach"
* Fraser Ross:
> "Alf P. Steinbach"
>> Searching for 'atexit' immediately landed me on §3.6.3/3.
>>
>> Essentially the rules ensure that static objects existing when an
>> atexit handler is registered, still exist when that handler runs (i.e.
>> not yet destroyed).
>
> That section only refers to non-local static objects so its irrelevant.
You're missing an apostrophe in "its".
Anyway, it seems you have a misconception regarding what "static storage
duration" means.
It means any object with static storage duration, and that includes "static"
local variables ("static storage duration" is defined by §3.7.1 -- and now,
don't quarrel, cause I'm not going to help you more then, but darn it, read!).
Cheers & hth.,
- Alf
== 8 of 10 ==
Date: Sat, Jul 25 2009 2:38 pm
From: "Fraser Ross"
> Anyway, it seems you have a misconception regarding what "static
> storage duration" means.
>
> It means any object with static storage duration, and that includes
> "static" local variables ("static storage duration" is defined by
> §3.7.1 -- and now, don't quarrel, cause I'm not going to help you
> more then, but darn it, read!).
I know it includes static local variables. 3.7.1/3 says 3.6.3 describes
the destruction of local static variables. I can't see where it is.
Anyway its determined by what gets initialised at run-time and most
programs can run differently depending on run-time factors.
Fraser.
== 9 of 10 ==
Date: Sat, Jul 25 2009 3:00 pm
From: "Alf P. Steinbach"
* Fraser Ross:
>> Anyway, it seems you have a misconception regarding what "static
>> storage duration" means.
>>
>> It means any object with static storage duration, and that includes
>> "static" local variables ("static storage duration" is defined by
>> §3.7.1 -- and now, don't quarrel, cause I'm not going to help you
>> more then, but darn it, read!).
>
> I know it includes static local variables.
In the previous article you wrote (incorrectly), "That section only refers to
non-local static objects so its irrelevant.", so you're contradicting yourself.
> 3.7.1/3 says 3.6.3 describes
> the destruction of local static variables. I can't see where it is.
Read the very first sentence of the very first paragraph.
> Anyway its determined by what gets initialised at run-time and most
> programs can run differently depending on run-time factors.
That's right.
Cheers & hth.,
- Alf
PS: Forget about the apostrophe, there shouldn't be any.
== 10 of 10 ==
Date: Sat, Jul 25 2009 3:02 pm
From: "Alf P. Steinbach"
* Alf P. Steinbach:
> * Fraser Ross:
>>> Anyway, it seems you have a misconception regarding what "static
>>> storage duration" means.
>>>
>>> It means any object with static storage duration, and that includes
>>> "static" local variables ("static storage duration" is defined by
>>> §3.7.1 -- and now, don't quarrel, cause I'm not going to help you
>>> more then, but darn it, read!).
>>
>> I know it includes static local variables.
>
> In the previous article you wrote (incorrectly), "That section only
> refers to non-local static objects so its irrelevant.", so you're
> contradicting yourself.
>
>
>
>> 3.7.1/3 says 3.6.3 describes the destruction of local static
>> variables. I can't see where it is.
>
> Read the very first sentence of the very first paragraph.
>
>
>> Anyway its determined by what gets initialised at run-time and most
>> programs can run differently depending on run-time factors.
>
> That's right.
>
>
> Cheers & hth.,
>
> - Alf
>
> PS: Forget about the apostrophe, there shouldn't be any.
On second thoughts, there should.
Darn, I'm cross-eyed.
Argh.
==============================================================================
TOPIC: China factory wholesale NFL,mlb,nhl,nbaJerseys Free Shipping Paypal
payment <www.wtojerseys.com>
http://groups.google.com/group/comp.lang.c++/t/f769d521a2fb7599?hl=en
==============================================================================
== 1 of 1 ==
Date: Sat, Jul 25 2009 12:56 pm
From: wtojerseys
ALL ARE IN HAND,FAST SHIPMENT!
We use EMS,it usually takes 4-7 days arrive your hand!
BRAND NEW WITH tAG (NWT)
FASTEST SHIPPING PROMIS
SIZE:M,L,XL,XXL48,50,52,54
M48:81--65cm(length-width)
L50:83--66cm(length-width)
XL52:85--67cm(length-width)
XXL54:88--67cm( length-width)
We offer money back(not include shipment) guarantee on all my
jerseys,
if you are not happy you can return it for a FULL REFUND as long as
the item is in the same condition that you received.
ALL LETTERS AND NUMBERS ARE SEWN ON!!!
High Quality Promised!!!
and you can mix the order!!!
Arizona Cardinals(www.wtojerseys.com)
Atlanta Falcons(www.wtojerseys.com)
Baltimore Ravens(www.wtojerseys.com)
Buffalo Bills(www.wtojerseys.com)
Carolina Panthers(www.wtojerseys.com)
Chicago Bears(www.wtojerseys.com)
Cincinnati Bengals(www.wtojerseys.com)
Cleveland Browns(www.wtojerseys.com)
Dallas Cowboys(www.wtojerseys.com)
Denver Broncos(www.wtojerseys.com)
Detroit Lions(www.wtojerseys.com)
Green Bay Packers(www.wtojerseys.com)
Houston Texans(www.wtojerseys.com)
Indianapolis Colts(www.wtojerseys.com)
Jacksonville Jaguars(www.wtojerseys.com)
Kansas City Chiefs(www.wtojerseys.com)
Miami Dolphins(www.wtojerseys.com)
Minnesota Vikings(www.wtojerseys.com)
New England Patriots(www.wtojerseys.com)
New Orleans Saints(www.wtojerseys.com)
New York Giants(www.wtojerseys.com)
San Francisco 49ers(www.wtojerseys.com)
Seattle Seahawks(www.wtojerseys.com)
St. Louis Rams(www.wtojerseys.com)
Tampa Bay Buccaneers(www.wtojerseys.com)
Tennessee Titans(www.wtojerseys.com)
Washington Redskins(www.wtojerseys.com)
New York Jets(www.wtojerseys.com)
Oakland Raiders(www.wtojerseys.com)
Philadelphia Eagles(www.wtojerseys.com)
Pittsburgh Steelers(www.wtojerseys.com)
San Diego Chargers(www.wtojerseys.com)
==============================================================================
TOPIC: dealing with lower level programmers
http://groups.google.com/group/comp.lang.c++/t/f708a2c0cfa8ce2d?hl=en
==============================================================================
== 1 of 2 ==
Date: Sat, Jul 25 2009 1:05 pm
From: Brian Wood
On Jul 25, 3:34 am, Ian Collins <ian-n...@hotmail.com> wrote:
> > More likely you've never worked in an environment designed to
> > produce good software. More likely you don't know how to judge
> > good. Although I've seen a few exceptions, most professional
> > programmers are competent, and the cases I've seen where they're
> > not productive, it's been because management has prevented them
> > from being productive. Sometimes, simply by letting a few
> > snotty brats who think that they're the only ones who know
> > anything run things.
>
> Or marketing types who think they know how to develop software!
>
> I think more professional programmers succeed despite rather than
> because of their management.
>
One reason I started a company was to get away from the
groupthink/immaturity that is pervasive in companies today.
I read the hand writing on the wall in the 1990s and didn't
feel I had a choice. The company was born out of necessity
more than than it being a goal of some sort. Now I view it
as a move parallel to the pilgrims who left Europe on the
Mayflower and some other ships. They didn't have it easy,
but they were successful in producing humbler management
for themselves in America. That worked for awhile, but
lately we've not been getting much out of our "leaders."
Brian Wood
Ebenezer Enterprises
www.webEbenezer.net
== 2 of 2 ==
Date: Sat, Jul 25 2009 3:38 pm
From: Brian Wood
On Jul 25, 3:05 pm, Brian Wood <c...@mailvault.com> wrote:
>
> One reason I started a company was to get away from the
> groupthink/immaturity that is pervasive in companies today.
> I read the hand writing on the wall in the 1990s and didn't
> feel I had a choice. The company was born out of necessity
> more than than it being a goal of some sort. Now I view it
> as a move parallel to the pilgrims who left Europe on the
> Mayflower and some other ships. They didn't have it easy,
> but they were successful in producing humbler management
> for themselves in America. That worked for awhile, but
> lately we've not been getting much out of our "leaders."
>
Here's a few headlines from July 25, 2009
http://wnd.com
Analyst says Obama will change healthcare plan
'The president hates one thing more than anything else – losing'
GOP not allowed to say 'government-run health care'
Communications with constituents that use phrase lose franking
privilege
Brian Wood
Ebenezer Enterprises
www.webEbenezer.net
==============================================================================
TOPIC: wholesale Oakley goggle www.online-saler.com
http://groups.google.com/group/comp.lang.c++/t/02f474200bcf43e8?hl=en
==============================================================================
== 1 of 1 ==
Date: Sat, Jul 25 2009 4:41 pm
From: "www.sneaker-shop08.com"
Sunglass:
wholesale ADIDAS Sunglass www.online-saler.com
wholesale ARMANI Sunglass www.online-saler.com
wholesale Burberry Sunglasswww.online-saler.com
wholesale BVLGARL Sunglass www.online-saler.com
wholesale Cartier Sunglass www.online-saler.com
wholesale CHANEL Sunglass www.online-saler.com
wholesale COACH Sunglass www.online-saler.com
wholesale D&G Sunglass www.online-saler.com
wholesale DIESEL Sunglass www.online-saler.com
wholesale DIOR Sunglass www.online-saler.com
wholesale ED Hardy Sunglasswww.online-saler.com
wholesale FENDI Sunglass www.online-saler.com
wholesale Ferragamo Sunglass www.online-saler.com
wholesale GIVENCHY Sunglasswww.online-saler.com
wholesale GUCCI Sunglass www.online-saler.com
wholesale LV Sunglass www.online-saler.com
wholesale NIKE Sunglass www.online-saler.com
wholesale Oakley Sunglass www.online-saler.com
wholesale POLICE Sunglass www.online-saler.com
wholesale PRADA Sunglass www.online-saler.com
wholesale Ray.Ban Sunglass www.online-saler.com
wholesale ROBERTO CAVALLI Sunglass www.online-saler.com
wholesale Salvatore Sunglass www.online-saler.com
wholesale VERSACE Sunglass www.online-saler.com
wholesale YSL Sunglass www.online-saler.com
goggle:
wholesale Armani goggle www.online-saler.com
wholesale Catier goggle www.online-saler.com
wholesale Chanel goggle www.online-saler.com
wholesale D&G goggle www.online-saler.com
wholesale DIOR goggle www.online-saler.com
wholesale FENDI goggle www.online-saler.com
wholesale FERRE goggle www.online-saler.com
wholesale FRED goggle www.online-saler.com
wholesale GUCCI goggle www.online-saler.com
wholesale LV goggle www.online-saler.com
wholesale MONT BLANC goggle www.online-saler.com
wholesale NIKE goggle www.online-saler.com
wholesale Oakley goggle www.online-saler.com
wholesale POLICE goggle www.online-saler.com
wholesale PRADA goggle www.online-saler.com
wholesale PUMA goggle www.online-saler.com
wholesale RAY.BAN goggle www.online-saler.com
wholesale VERSACE goggle www.online-saler.com
==============================================================================
TOPIC: ╃♡╃♡╃Wholesale Nokia ,Iphone, Samsung, Blackberry, Sony, Motorola,etc
brand mobiles "www.toptradea.com"
http://groups.google.com/group/comp.lang.c++/t/f867f91b3c93484d?hl=en
==============================================================================
== 1 of 1 ==
Date: Sat, Jul 25 2009 8:11 pm
From: peng Selina
╃♡╃♡╃Wholesale Nokia ,Iphone, Samsung, Blackberry, Sony, Motorola,etc
brand mobiles "www.toptradea.com"
Iphone http://www.toptradea.com/category.php?id=435
Nokia http://www.toptradea.com/category.php?id=436
Blackberry http://www.toptradea.com/category.php?id=437
HTC http://www.toptradea.com/category.php?id=438
Samsung http://www.toptradea.com/category.php?id=440
Motorola http://www.toptradea.com/category.php?id=439
Toptrading Co.,ltd found in 1995, our Email&MSN is
toptradea@hotmail.com. As a manufacture supplier,we have more than 10
years experience of this business.All products are at prices from
original factory.All items have been verified by us, so they are
credible.Veries of styles can meets the different customer need, fit
customer demand to adjust the production.AAA quality,most competitive
prices is our promise. Our main products are Mobile phones,
Laptop,MP3/4/5, video games, PSP, Watches and so on, you can click our
website www.toptradea.com to have a look.
==============================================================================
TOPIC: ===Welcome to comp.lang.c++! Read this first.
http://groups.google.com/group/comp.lang.c++/t/2dfad3237cc109dd?hl=en
==============================================================================
== 1 of 1 ==
Date: Sat, Jul 25 2009 9:30 pm
From: Shiva
Welcome to comp.lang.c++! Read this first.
This post is intended to give the new reader an introduction to reading
and posting in this newsgroup. We respectfully request that you read
all the way through this post, as it helps make for a more pleasant
and useful group for everyone.
First of all, please keep in mind that comp.lang.c++ is a group for discussion
of general issues of the C++ programming language, as defined by the ANSI/ISO
language standard. If you have a problem that is specific to a particular system
or compiler, you are much more likely to get complete and accurate answers in a
group that specializes in your platform. A listing of some newsgroups is given
at the end of this post.
The FAQ (Frequently Asked Question) list has a wealth of information for
both the new and veteran C++ programmer. No matter what your experience
level, you are encouraged to read the entire list, if only to familiarize
yourself with what answers are available to minimize redundant replies.
The comp.lang.c++ FAQ is available at http://www.parashift.com/c++-faq-lite/
If the FAQ list does not help, then many regular readers of this group
are happy to assist with problems of standard C++. We have only a few
requests that we ask be adhered to, for the benefit of all:
* Please put a short summary in the subject line. Descriptions such as
"HELP!!!!!!" are not helpful, and many regular posters ignore such
requests. A good example is, "Problem with Virtual Functions."
* State the question or the problem clearly and concisely. Describe what
you are trying to do, and the problem you are running into. Include all
relevant error messages.
* Include the smallest, complete and compilable program that exhibits your
problem. As a rule, posters in comp.lang.c++ will not do homework, but will
give helpful hints if you have shown some willingness to try a solution.
* comp.lang.c++ is forum for discussion, and as such some regular posters do
not give E-mail replies. Very often follow-ups to postings have corrections,
so plan on taking part in the discussion if you post a question. If you
do receive e-mail replies, it is considered polite to post a summary.
* Don't post in HTML format. Many readers of this newsgroup don't use
newsreaders which can handle HTML postings.
* If you have to include source code in your post, include the
source in the message body. Don't use attachments. A lot
of contributors to this newsgroup won't even notice the existence
of attachments or won't open them. You try to get any help
you can get, don't you?
Some netiquette topics which frequently crop up on comp.lang.c++ are
also answered in the FAQ.
* Should I post job advertisements and/or resumes on comp.lang.c++?
http://www.parashift.com/c++-faq-lite/how-to-post.html#faq-5.10
* What if I really need a job; should I post my resume on comp.lang.c++?
http://www.parashift.com/c++-faq-lite/how-to-post.html#faq-5.11
* What should I do to someone who posts something off-topic?
http://www.parashift.com/c++-faq-lite/how-to-post.html#faq-5.12
A note on comp.lang.c++ etiquette: Accuracy is valued very highly in this
newsgroup; therefore posts are frequently corrected, sometimes perhaps
too harshly, and often to the annoyance of new posters who consider the
correction trivial. Do not take it personally; the best way to fit in
with comp.lang.c++ is to express gratitude for the correction, move on,
and be more careful next time.
This is a very busy group, so these requests are designed to make it as
pleasant and efficient an experience as possible. We hope it proves
a valuable commodity to you.
A list of some Newsgroups :
Languages and Programming
-------------------------
comp.lang.c The C Programming Language
comp.lang.asm.x86 x86 assembly language programming
comp.programming Non-language specific programming
comp.graphics.algorithms Issues of computer graphics
Operating Systems
-----------------
comp.os.msdos.programmer DOS, BIOS, Memory Models, interrupts,
screen handling, hardware
comp.os.ms-windows.programmer.win32 MS/Windows: Mice, DLLs, hardware
comp.os.os2.programmer.misc OS/2 Programming
comp.sys.mac.programmer.misc Macintosh Programming
comp.unix.programmer General Unix: processes, pipes, POSIX,
curses, sockets
comp.unix.[vendor] Various Unix vendors
Microsoft VC++
-------------
microsoft.public.vc.language VC++ issues
microsoft.public.vc.mfc MFC Issues
microsoft.public.dotnet.languages.vc C++/CLR Issues
microsoft.public.dotnet.framework .Net Framework
Borland C++ Builder
-------------------
borland.public.cppbuilder.language Borland C++ Builder
borland.public.cpp.language
borland.public.cppbuilder
-Shiva
http://www.slack.net/~shiva/welcome.txt
Sun Jul 26 00:30:00 EDT 2009
==============================================================================
You received this message because you are subscribed to the Google Groups "comp.lang.c++"
group.
To post to this group, visit http://groups.google.com/group/comp.lang.c++?hl=en
To unsubscribe from this group, send email to comp.lang.c+++unsubscribe@googlegroups.com
To change the way you get mail from this group, visit:
http://groups.google.com/group/comp.lang.c++/subscribe?hl=en
To report abuse, send email explaining the problem to abuse@googlegroups.com
==============================================================================
Google Groups: http://groups.google.com/?hl=en
No comments:
Post a Comment