Re:Why perl has separate arrays and hashes: It's as if they ...
by pavel_lishin on Tuesday June 21, 2011 @02:40PM
(#2679871)
> It's just a little disappointing to be downvoted without anyone actually commenting on the subject.
When I saw your comment, it didn't look downvoted to me. You clearly realize that people can vote on comments - has it occurred to you that comments can bounce back from a negative score? That is, unless you append some passive aggressive horse-shit to the end.
Honestly, I don't know if we gain anything by PHP having arrays pull double duty in this way. The only advantage is, what, having one less keyword to remember?
Re:Why perl has separate arrays and hashes: It's as if they ...
by saucetenuto on Tuesday June 21, 2011 @04:51PM
(#2680355)
You said that PHP's arrays/hashes were awesome, but did not say why. In other words, you did not contribute to the discussion. This may have attracted some of your downvotes; certainly it made it your post unlikely to convince anyone of anything.
I can't see the future, but I can edit the past. It's just a little disappointing to be downvoted without anyone actually commenting on the subject.
> but having actual arrays and hashes as different types is super convenient.
I agree especially if, in the language, arrays and hashes are objects with methods.
I didn't claim PHP's arrays were the greatest data structure on earth but ordered hashes that special-cases integer indexes is a pretty nice procedural-style data structure. PHP doesn't really have arrays; it's just the hash type is flexible enough to do double-duty.
Apparently, on Hacker News, having such opinions is both downvote worthy and punch-in-the-face worthy.