|
The_Franz posted:MSVC didn't support that particular C99 behavior until VS2013. Yeah, we switched to using /TP eventually, as I recall, and then renamed things to .cpp incrementally.
|
#
?
May 3, 2014 05:16
|
|
|
|
| # ? May 21, 2024 02:13 |
|
|
Subjunctive posted:Yeah, MSVC and some lovely off-brand Unix one (Sun Studio?) were the compilers that kept Firefox C and C++ in the dark ages for a long time; I don't think it was OK to have intermingled variable declarations in C files until...2007? I remember the sun compiler as being really terrible and a thing you should never use if you had gcc available, but I don't think I used any sun after like 2004.
|
|
#
?
May 3, 2014 05:41
|
|
|
fritz posted:I remember the sun compiler as being really terrible and a thing you should never use if you had gcc available, but I don't think I used any sun after like 2004. Sun shipped our software, and of COURSE they built it with their terrible bullshit, so I made the bad decision to care about it for too long.
|
|
#
?
May 3, 2014 05:48
|
|
|
pseudorandom name posted:Microsoft has publicly stated that they will not support any C features that don't naturally fall out of their C++ implementation. That was true for about a decade, but 2013 has a bunch of C99 stuff not part of C++. The fact that they specifically announced that 2013 could build FFmpeg unpatched made some people suspect that c99-to-c89 embarrassed them into doing it (or perhaps just proved that yes, people do care about C99).
|
|
#
?
May 3, 2014 14:15
|
|
|
Still not holding out for SunCC.
|
|
#
?
May 3, 2014 14:25
|
|
|
This is handling what animation the player character has during his various states of running and jumping. It evolved naturally, and I pray to god I don't have to ever add anything to that again. //Player Animation if (player.height != 8) { if (player.touching == FlxObject.FLOOR) // if you touch the ground { if (player.velocity.x > 0) // and have positive speed { if (FlxG.keys.D) // and are pressing D { player.play("run"); // you run } else // if you have positive speed and touch the floor { player.play("stop"); //you play the stop animation } } else // if you touch the ground and have 0 or negative speed { player.play("stand"); // you stand } } else if (player.velocity.y < 0) // if you have negative vertical velocity { player.play("jumpup"); // you jump up } else // if you don't touch the ground { player.play("jump"); // you jump } } else // if you're not not 8 in height { player.play("slide"); //you slide } e: I actually found a redundant "else if" by posting this here. yea! Pizzatime fucked around with this message at 01:16 on May 4, 2014 |
|
#
?
May 4, 2014 01:12
|
|
|
"Who the f*heck is Tadayoshi Funaba and why can he reject sensible patches unilaterally?" Great people skills on display in that thread.
|
|
#
?
May 4, 2014 01:55
|
|
|
Sebbe posted:"Who the f*heck is Tadayoshi Funaba and why can he reject sensible patches unilaterally?"   (Of course, the [1] at the bottom of the post links to his contribution page) 
|
|
#
?
May 4, 2014 02:08
|
|
|
quote:This model is clearly wrong. The most successful projects out there hahahahahahahahahahaha
|
|
#
?
May 4, 2014 03:01
|
|
|
Sebbe posted:"Who the f*heck is Tadayoshi Funaba and why can he reject sensible patches unilaterally?" The claim that Linux doesn't have maintainers making unilateral decisions is pretty adorable.
|
|
#
?
May 4, 2014 03:06
|
|
|
Jewel posted:
It's almost like projects headed up by Linus Torvalds tend to accept patches from dickbags and have histories of dickbag behavior!
|
|
#
?
May 4, 2014 03:13
|
|
|
Almost.
|
|
#
?
May 4, 2014 03:13
|
|
|
Felipe Contreras is a colossal jackass on the Git mailing list too, and I think Linus ignores him on various Linux lists. http://permalink.gmane.org/gmane.comp.version-control.git/236109
|
|
#
?
May 4, 2014 04:48
|
|
|
He takes his last name to heart, I guess.
|
|
#
?
May 4, 2014 05:08
|
|
|
Suspicious Dish posted:It's almost like projects headed up by Linus Torvalds tend to accept patches from dickbags and have histories of dickbag behavior! If I ever saw Al Viro disagree politely with someone, I'd probably submit it to drat You Autocorrect.
|
|
#
?
May 4, 2014 05:22
|
|
|
Sebbe posted:"Who the f*heck is Tadayoshi Funaba and why can he reject sensible patches unilaterally?" The community around Ruby is the reason I never got around to bothering with it. I'm not particularly fond of the language itself, but the way the community acts makes me steer FAR away from it unless I'm forced to use it. The fact that nearly all of the projects I've tried to use that was written in Ruby fails horribly also plays a part in that...
|
|
#
?
May 4, 2014 05:37
|
|
|
God of Mischief posted:The community around Ruby is the reason I never got around to bothering with it. I'm not particularly fond of the language itself, but the way the community acts makes me steer FAR away from it unless I'm forced to use it. The fact that nearly all of the projects I've tried to use that was written in Ruby fails horribly also plays a part in that... How do you read that thread and come away with the conclusion that the Ruby community sucks? Also do you mean the core team or people who write gems? The latter tends to seem more objectionable than the former from my backseat position.
|
|
#
?
May 4, 2014 06:01
|
|
|
God of Mischief posted:The community around Ruby is the reason I never got around to bothering with it. I'm not particularly fond of the language itself, but the way the community acts makes me steer FAR away from it unless I'm forced to use it. The fact that nearly all of the projects I've tried to use that was written in Ruby fails horribly also plays a part in that... You didn't try ruby because they act cordial, even in the face of someone who acts like a complete jerk?
|
|
#
?
May 4, 2014 06:04
|
|
|
Speaking as an open source code owner, we do frequently get our heads stuck up own own asses. The bug/patch submitter seems right on the technical merits: these format strings have an accepted meaning, albeit as an extension beyond POSIX, and Ruby accepts them generally, and this one Ruby library is getting their semantics wrong; absent a permanent bug-for-bug compatibility guarantee, that should be good enough. But this dude is also clearly a jerk, and that gives the code owner a lot of cover to be wrong behind.
|
|
#
?
May 4, 2014 08:22
|
|
|
pokeyman posted:How do you read that thread and come away with the conclusion that the Ruby community sucks?
|
|
#
?
May 4, 2014 09:44
|
|
|
pokeyman posted:How do you read that thread and come away with the conclusion that the Ruby community sucks? I'd certainly be irritated if I'd go "Here's the cure for AIDS motherfuckers!", to which I'd get the reply: "You used a bad word, you arrogant poopoohead! You are now wrong!" - and that's what I currently get from this discussion, not being in Ruby community myself: be polite, or we won't accept your code (also we want to be japanese). From what I see, at least two of them are *leaders* of the language. On the other hand, he's pretty arrogant and inward-looking, and clearly (  ) right (some of my academics were like that), so I hope that some of these people are just screwing with him.I guess people sometimes are too protective of their code and Ruby guys seem to accept this in this case (well, this Japanese guy that created this clearly cannot be wrong, and we don't want to anger him, because he will leave the project, oh no!). Come on Felipe, create your own Ruby, with booze, and hookers!
|
|
#
?
May 4, 2014 09:49
|
|
|
Seriously the dude has all the trappings of an blisteringly blunt know-it-all except for knowing it all.
|
|
#
?
May 4, 2014 09:55
|
|
|
Well maybe if Ruby weren't such a racist language it wouldn't attract racist arguments.
|
|
#
?
May 4, 2014 11:27
|
|
|
pokeyman posted:How do you read that thread and come away with the conclusion that the Ruby community sucks? The people who write gems. I don't deal with the language enough to have any opinions on the core team and how they handle things. And my opinion does not come purely from that thread. It has just been my experience every time I do look at the language, something drives me away, and it is usually something about the community that does it. Strong Sauce posted:You didn't try ruby because they act cordial, even in the face of someone who acts like a complete jerk? I find both sides to be acting like children in this specific argument. Neither side can articulately explain to the other what is going on. One jerk tried submitting a patch, gets shut down immediately by someone he doesn't know, and asks (in a vulgar way) why. He gets told he has a potty mouth and should fork the language. Yeah, reasonable option.
|
|
#
?
May 4, 2014 14:16
|
|
|
Why is it unreasonable to fork the language? Forking things is the best part of open source. Be good or be forked, as the saying goes. And plenty of companies already maintain forks of Ruby, be they commercial (as REE was) or for their private use.
|
|
#
?
May 4, 2014 15:35
|
|
|
People often get the Ruby community and the Rails community mixed up. The Rails community is full of people like David "omakase" Hansson, while the Ruby community is lead by matz, who is the most courteous and kind person ever.
|
|
#
?
May 4, 2014 16:32
|
|
|
Is Ruby even used for anything other than Rails, and tools to scaffold Rails servers?
|
|
#
?
May 4, 2014 17:42
|
|
|
eithedog posted:I'd certainly be irritated if I'd go "Here's the cure for AIDS motherfuckers!", to which I'd get the reply: "You used a bad word, you arrogant poopoohead! You are now wrong!" - and that's what I currently get from this discussion, not being in Ruby community myself: be polite, or we won't accept your code (also we want to be japanese). From what I see, at least two of them are *leaders* of the language. its not the cure for AIDS though; its a patch to change how a bit of datetime works that is not breaking much of anything. people rarely want to work with the dude who creates so much negativity all of the time unless there is literally no other way to do so. I like when he said something like "Yeah I'm an rear end in a top hat and it gets results" and sure it does, but he will literally never move beyond his current level of work that way. also, who do you think is more important to ruby: the drive by pull requester who spews poo poo the moment things aren't going their way or the dude who has written significant portions of what is generally a pretty tricky subject for your project?
|
|
#
?
May 4, 2014 17:58
|
|
|
more like dICK posted:Is Ruby even used for anything other than Rails, and tools to scaffold Rails servers? Yes.
|
|
#
?
May 4, 2014 18:10
|
|
|
Suspicious Dish posted:People often get the Ruby community and the Rails community mixed up. The Rails community is full of people like David "omakase" Hansson, while the Ruby community is lead by matz, who is the most courteous and kind person ever. The first time I can remember hearing about ruby was in this context: http://geekfeminism.wikia.com/wiki/CouchDB_talk
|
|
#
?
May 4, 2014 19:02
|
|
|
FamDav posted:its not the cure for AIDS though; its a patch to change how a bit of datetime works that is not breaking much of anything. people rarely want to work with the dude who creates so much negativity all of the time unless there is literally no other way to do so. I like when he said something like "Yeah I'm an rear end in a top hat and it gets results" and sure it does, but he will literally never move beyond his current level of work that way. From what I've read through it 1) does not parse git time, 2) produces contrary to expected behavior comparing to the same call from glibc (?) I'd think that it's the people responsible for project, not a person - as such if the code in some part doesn't adhere to standard and the main maintainer opposes the change without really a reason... well, then it would get me thinking if it's indeed communal project and what really is the point of making changes if they can be arbitrarily revoked. As I said - everyone makes mistakes, so while there shouldn't be a need for diplomacy, they're ending with a situation that original author is being a dick, community adheres to that and makes them look hm... don't know, inviting isn't certainly the word I'd ever use. To resolve the commit situation I'd still expect a peer review, not an arbitrarily decision; bear in mind that it comes from my idealistic point of view where everyone is happily riding on fluffy clouds, as I don't partake in any open source group project (different matter when it comes to work, but that's not here nor there). As for negativity - from what I've read he started throwing fucks around when he's gotten a response in Japanese to "not come back again" (I don't know about his behavior in other git projects / commits, I'm barely observing what's happening in that thread, and I don't really know if I care enough to go read through it; well, I barely care about this). Probably I'd act similarly. Hm - I'd probably try to go back to original author to discuss this, if the given solution is indeed worthwhile. If the author would still give me response "no", without real explanation hm... I guess then I'd make everyone unhappy and decide on creating a switch that makes this function ugly and corrects its behavior. Nobody wins! (but yes, I'd have to side with the original maintainer) canis minor fucked around with this message at 19:22 on May 4, 2014 |
|
#
?
May 4, 2014 19:13
|
|
|
Suspicious Dish posted:matz, who is the most courteous and kind person ever. That's my takeaway from that thread. He cheerfully translates the bug report response into English, warmly but firmly backs up his DateTime maintainer of ten+ years, and politely explains which arguments are likely to be convincing and which ones aren't. Without even once suggesting that the douche go gently caress himself (or, synonymously, go fork the language). What a champ.
|
|
#
?
May 4, 2014 19:28
|
|
|
Suspicious Dish posted:People often get the Ruby community and the Rails community mixed up. The Rails community is full of people like David "omakase" Hansson, while the Ruby community is lead by matz, who is the most courteous and kind person ever. matz on diversity "let em eat rails girls" https://twitter.com/yukihiro_matz/status/380394450746216448 "@rubyconf is not a tool to solve our social problem. If the program has no explicit discrimination, let it be. We have RailsGirls instead."
|
|
#
?
May 4, 2014 19:40
|
|
|
That's extremely disappointing.
|
|
#
?
May 4, 2014 19:44
|
|
|
Haha, and someone actually called this guy a champ.
|
|
#
?
May 4, 2014 19:45
|
|
|
eithedog posted:As for negativity - from what I've read he started throwing fucks around when he's gotten a response in Japanese to "not come back again" (I don't know about his behavior in other git projects / commits, I'm barely observing what's happening in that thread, and I don't really know if I care enough to go read through it; well, I barely care about this). Probably I'd act similarly. It looks like that's par for the course for this guy tho: Lysidas posted:Felipe Contreras is a colossal jackass on the Git mailing list too, and I think Linus ignores him on various Linux lists. I wouldn't want to work with the dude either.
|
|
#
?
May 4, 2014 20:10
|
|
|
carry on then posted:Haha, and someone actually called this guy a champ. You forgot to add "when he's dealing with abusive patch submitters". His attitude towards social problems in his community looks to be pretty lovely.
|
|
#
?
May 4, 2014 20:49
|
|
|
It's almost like someone can have good social skills while simultaneously holding views that are entirely (if regrettably) typical of the society he lives in.
|
|
#
?
May 4, 2014 21:01
|
|
|
eithedog posted:From what I've read through it 1) does not parse git time, 2) produces contrary to expected behavior comparing to the same call from glibc (?)
|
|
#
?
May 4, 2014 21:10
|
|
|
|
| # ? May 21, 2024 02:13 |
|
|
xtal posted:Why is it unreasonable to fork the language? Forking things is the best part of open source. Be good or be forked, as the saying goes. And plenty of companies already maintain forks of Ruby, be they commercial (as REE was) or for their private use. Forking the language is a fine solution if the issue is important enough or internal to his company. It is not a fine solution for a minor issue that he wants fixed because it affects other major tools (git/github).
|
|
#
?
May 4, 2014 21:13
|
|