[haiku-development] Re: Banning Barrett

  • From: looncraz <looncraz@xxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Fri, 15 Mar 2019 14:45:51 -0500

I haven't chimed in here since I've been sick and fell behind reading all this... mess.

I don't see Barret's demonstrated behavior as warranting a full-on ban.  Removing commit access and forcing to go through Gerrit review seems reasonable, but not an outright ban (which I would take to mean from the ml, IRC, and everything else).

IMHO, a ban requires more than just someone who irritates people. Barret brought up some valid points in a less than diplomatic manner, but, IMHO, wasn't met with a measured and tempered response that could have allayed his concerns and prevented this whole situation.

On 3/15/2019 14:21, Dario Casalinuovo wrote:


    Well ... that doesn't seem to make a lot of sense to me, to continue
    committing code but not to be subscribed to the list where discussions
    take place.


Not all people are of this opinion.

I certainly am.  I just don't understand why someone would not want to be a part of the mailing list if they're even just interested in contributing.


Yes because I didn't fail as you to find the real issue here, memset should not be used on POD objects.

I think you have that backwards - POD types are fine with memset, it's non-POD types that are not... since you are undermining the work of the constructor (or even vtables if you're sloppy enough).

POD is just a range of memory represented by types, setting all bytes to 0 with memset is fine so long as that should be the default state of the data.

--The loon

Other related posts:

  1. Home
  2. haiku-development
  3. Archive
  4. 03-2019