Re: [boost] [Root.Ptr] Update (C consultancy -> ISO)

Subject: Re: [boost] [Root.Ptr] Update (C consultancy -> ISO)
From: Phil Bouchard (philippeb8_at_[hidden])
Date: 2017-08-14 14:55:25

I am unfamiliar with all the Github features and I will ask support to
create a private branch off the public repository. Meanwhile I needed a
repository so I just made everything private.

I do understand my library needs to be perfect before it is accepted but I
need to upgrade the ISO standards before submitting it to Boost (reverse of
the usual procedure).

I do understand also Root.Ptr is not trivial so I'm better off improving it
myself than spend time explaining it. But I will explain it and answer
questions after it is well tested.

But the benefits are there, hands down. It will also jumpstart C++ when
comparing to other languages.

What I don't understand is where is the whole memory management crew gone?
Years ago there was at least 20 people fascinated about the subject. Now I
need to change oil before the engine starts.

Regards,
-Phil

Seth via Boost <boost_at_[hidden]> wrote:
> On 14-08-17 14:04, Phil Bouchard via Boost wrote:
>> 
>> Once I am done then I'll make everything public again or if I create a
>> new private repository for the parser then I can make root_ptr public. 
> 
> warning: brief mode engaged
> 
> Creating a public repo is not costly. Just split it off now.
> 
> From where I'm sitting: on the one hand you seem to regret a lack of
> community adoption/support, and at the same time appear to manage simple
> things like repo availability upside-down. This just makes the project
> (i.e. you) appear untrustworthy, dilettant, intransparent or a
> combination of those.
> 
> Just my $0.02
> 
> Seth
> 
> 
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
> 
>