This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Ziemowit Laski <zlaski@apple.com> writes:
Please, folks -- this ain't rocket science...
You posted your question three hours ago. Generally it takes at least a day to get an answer out of anyone.
I find either (1) or (3) infinitely preferable to (2), and would suggest you consider a (3a) in which the ObjC/ObjC++ front ends enlarge the C/C++ lang_type structures (in much the same way that all these front ends currently build on struct c_common_identifier to create their struct lang_identifier). This is preferable to (3) if the additional data is small (up to, say, four pointers), or if it needs allocating for practically every RECORD_TYPE. If it is both large and rarely needed, your original (3) is better.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |