From mboxrd@z Thu Jan  1 00:00:00 1970
From: Shriramana Sharma <samjnaa@gmail.com>
Subject: Re: class Q_CORE_EXPORT QFlag
Date: Tue, 15 May 2007 00:20:41 +0530
Message-ID: <4648AF81.1070702@gmail.com>
References: <46372A8E.5090201@gmail.com> <6a00c8d50705040504p4fadca4vd62b074c2696c7e6@mail.gmail.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-c-programming-owner@vger.kernel.org>
In-Reply-To: <6a00c8d50705040504p4fadca4vd62b074c2696c7e6@mail.gmail.com>
Sender: linux-c-programming-owner@vger.kernel.org
List-Id: <linux-c-programming.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
To: Steve Graegert <graegerts@gmail.com>
Cc: Linux C Programming List <linux-c-programming@vger.kernel.org>

Thanks Leslie and Steve. It did not occur to me that it would be 
something MOC takes care of.

I need to read up on what these mangled __ symbols mean. I have seen 
some in glibc sources (just perused a few files) especially things like 
__throw -- probably flags to the C++ compiler indicating what a 
particular class or function or whatever behaves like, yes?

Shriramana Sharma.