Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PHP 7's new hashtable implementation

nikic.github.io

Post reply on HN
Print view View original

1–10 of 137 posts

Re: PHP 7's new hashtable implementation

#4

Post by McGlockenshire »

Bahamut wrote: post #2

What happened to PHP 6?

Here's a slide deck postmortem: http://www.slideshare.net/andreizm/the-good-the-bad-and-the-...

tl;dr: They made some bad decisions about Unicode and everyone got burned out.

They skipped 6 because 7 contains none of the Unicode changes and didn't want to confuse people.

Re: PHP 7's new hashtable implementation

#6

Post by jmspring »

michaelchisari wrote: post #3
Bahamut wrote: post #2

What happened to PHP 6?

It was a no-go. There was a lot of difficulties in getting it out the door, so I'm guessing they're pushing on with PHP7 to get rid of any social/political baggage that comes with the 6 release.

Were there cascading problems to word press, Drupal, etc?

Re: PHP 7's new hashtable implementation

#7

Post by adunn »

This is great news. PHP doesn't have many structured data types, so arrays (aka maps) are basically used for everything. Any improvement to them will impact the entire application.

It would be nice to have separate types for arrays and maps though. I don't understand why they were combined to begin with. Simplicity? Seems like there are more edge cases and gotchas the way things are now.

Re: PHP 7's new hashtable implementation

#8

Post by _RPM »

adunn wrote: post #7

This is great news. PHP doesn't have many structured data types, so arrays (aka maps) are basically used for everything. Any improvement to them will impact the entire application. It would be nice to have separate types for arrays and maps though. I don't understand why they were combined to begin with. Simplicity? Seems like there are more edge cases and gotchas the way things are now.

> It would be nice to have separate types for arrays and hash tables though. I don't understand why they were combined to begin with. Simplicity? Seems like there are more edge cases and gotchas the way things are now.

There is no "hash table" type in PHP user land.

Re: PHP 7's new hashtable implementation

#9

Post by imaginenore »

_RPM wrote: post #8
adunn wrote: post #7

This is great news. PHP doesn't have many structured data types, so arrays (aka maps) are basically used for everything. Any improvement to them will impact the entire application. It would be nice to have separate types for arrays and maps though. I don't understand why they were combined to begin with. Simplicity? Seems like there are more edge cases and gotchas the way things are now.

> It would be nice to have separate types for arrays and hash tables though. I don't understand why they were combined to begin with. Simplicity? Seems like there are more edge cases and gotchas the way things are now. There is no "hash table" type in PHP user land.

There are no arrays in PHP.

There are only hash tables that are called "array" for simplicity.

Re: PHP 7's new hashtable implementation

#10

Post by adunn »

_RPM wrote: post #8
adunn wrote: post #7

This is great news. PHP doesn't have many structured data types, so arrays (aka maps) are basically used for everything. Any improvement to them will impact the entire application. It would be nice to have separate types for arrays and maps though. I don't understand why they were combined to begin with. Simplicity? Seems like there are more edge cases and gotchas the way things are now.

> It would be nice to have separate types for arrays and hash tables though. I don't understand why they were combined to begin with. Simplicity? Seems like there are more edge cases and gotchas the way things are now. There is no "hash table" type in PHP user land.

You're right, thanks for pointing that out.
Post reply on HN