|
Boost :
|
- Next message: Eric Woodruff: "[boost] Re: reinterpret_cast<const shared_ptr<constT>&>[wasRe:const-correctness as function argument]"
- Previous message: Alexander Terekhov: "[boost] Re: boost vs. The Lawyers (non-technical)"
- In reply to: Thorsten Ottosen: "Re: [boost] Re: new initialization lib, any interest?"
- Next in thread: Yitzhak Sapir: "RE: [boost] Re: new initialization lib, any interest?"
- Maybe reply: Yitzhak Sapir: "RE: [boost] Re: new initialization lib, any interest?"
- Maybe reply: Rozental, Gennadiy: "RE: [boost] Re: new initialization lib, any interest?"
- Maybe reply: Aleksey Gurtovoy: "RE: [boost] Re: new initialization lib, any interest?"
- Maybe reply: Yitzhak Sapir: "RE: [boost] Re: new initialization lib, any interest?"
- Maybe reply: Aleksey Gurtovoy: "RE: [boost] Re: new initialization lib, any interest?"
- Reply: Thorsten Ottosen: "Re: [boost] Re: new initialization lib, any interest?"
- Maybe reply: Rozental, Gennadiy: "RE: [boost] Re: new initialization lib, any interest?"
- Maybe reply: Aleksey Gurtovoy: "RE: [boost] Re: new initialization lib, any interest?"
Thorsten Ottosen wrote:
>>>I think that the stuff you downloaded need some refractoring regarding
>>>hearder files. I'm considering
>>>two alternatives:
>>>
>>>/init/vector.hpp
>>>/init/deque.hpp
>>>... <one for each header>
>>>/enum.hpp
>>>
>>>or
>>>
>>>/imap.hpp // all map stuff
>>>/iseq.hpp // vector, deque
>>>/iset.hpp
>>>/iadap.hpp // stack queue
>>>/enum.hpp
>>>
>>>In the last approach one would also need some config macros s.t.
>>
> libraries
>
>>>without hash based containers canuse the same header. A third
>>>alternative would be to provide fine granularity for those who wants it
>>
> and
>
>>>a really big chunk as now. Suggestions are welcome.
>>
>>Sounds good, minimize dependencies and all that.
>>
>>Vin
>
>
> so which is better?
I'd prefer the first one
but I'm sure a lot of people will object to the names being so similar
to the standard headers
With the second one I'd go with fuller names
iseq.hpp -> isequential.hpp
or even -> init_sequential.hpp
I would mainly go for that because it took me a while to figure out what
seq stood for !! :-|
Vin
- Next message: Eric Woodruff: "[boost] Re: reinterpret_cast<const shared_ptr<constT>&>[wasRe:const-correctness as function argument]"
- Previous message: Alexander Terekhov: "[boost] Re: boost vs. The Lawyers (non-technical)"
- In reply to: Thorsten Ottosen: "Re: [boost] Re: new initialization lib, any interest?"
- Next in thread: Yitzhak Sapir: "RE: [boost] Re: new initialization lib, any interest?"
- Maybe reply: Yitzhak Sapir: "RE: [boost] Re: new initialization lib, any interest?"
- Maybe reply: Rozental, Gennadiy: "RE: [boost] Re: new initialization lib, any interest?"
- Maybe reply: Aleksey Gurtovoy: "RE: [boost] Re: new initialization lib, any interest?"
- Maybe reply: Yitzhak Sapir: "RE: [boost] Re: new initialization lib, any interest?"
- Maybe reply: Aleksey Gurtovoy: "RE: [boost] Re: new initialization lib, any interest?"
- Reply: Thorsten Ottosen: "Re: [boost] Re: new initialization lib, any interest?"
- Maybe reply: Rozental, Gennadiy: "RE: [boost] Re: new initialization lib, any interest?"
- Maybe reply: Aleksey Gurtovoy: "RE: [boost] Re: new initialization lib, any interest?"
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk