ooc-dev team mailing list archive

[Amos Wenger <ndd@xxxxxxxxxx>]

Yes changing designated initializers to regular struct initializers isn't
impossible at all. It just frightens me a little, because if you forget a
member, everything goes awry, whereas designated initializers don't have
this problem.

I'll try to modify rock to use regular initializations for class
structures and let you know.

ndd

P.S: Yes, I find MSVC's lack of C99 support very irritating, very much as
I find tcc bugs painful (structs initialization, again - but this time,
even regular struct initialization fails with closure contexts..) - yet I
don't think it's lost time to try and support as many C compilers as
possible.

On Thu, 12 Aug 2010 00:13:30 -0400, Oddity007 <oddity007@xxxxxxxxx> wrote:
> It would be possible for the most part (perhaps a few hickups in some  
> small locations).  Some people have a liking for that kind of  
> initialization, though.
> 
> A few side notes:
> 1) Would a MSVC compat header/compilation mode make sense?
> 2) It seems like there is a "screw them" attitude among certain people  
> with regards to support for MSVC's (lack of) C99 abilities, so #1  
> seems unlikely.
> 3) Compiling to the shared subset of C and C++ might also fit with the  
> compat thing.
> 
> On Aug 11, 2010, at 5:07 PM, Vincent Richomme  
> <forumer@xxxxxxxxxxxxxxx> wrote:
> 
>> Hi,
>>
>> I was curious to see if ooc bootstrap could be compiled using msvc  
>> and the biggest problem I have
>> (I am not talking about missing stdbool, no restrict keyword, ...)  
>> is about the dot syntax used
>> from what I understand to declare structure members.
>> For instance :
>>
>>
>> ...
>>         {
>>            .instanceSize = sizeof(rock_middle_tinker_Trail__Trail),
>>            .size = sizeof(void*),
>>            .name = "Trail",
>>          },
>> ...
>>
>> Would it be possible to generate some C code without this dotted  
>> syntax and use a
>> more traditional way of declaring structure member ?
>>
>> Thanks
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~ooc-dev
>> Post to     : ooc-dev@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~ooc-dev
>> More help   : https://help.launchpad.net/ListHelp
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~ooc-dev
> Post to     : ooc-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ooc-dev
> More help   : https://help.launchpad.net/ListHelp