In the UK, most maps use the British Grid projection. Google, in their international wisdom, appear to have used a different projection which causes the map to "appear wrong" to a UK person. Actually, the map is perfectly correct, it's just that Google are presenting it in a way which is not customary for the UK.
For example, try a search for postcode "EH1" on http://maps.google.co.uk, and the same on www.multimap.co.uk. Notice that the shape of the quarter-circle road system (Princes St, Melville Drive, the Bridges) is different on each.
> (traits are meaningless when you have either manifest types like scripting > languages or type inference like ML)
What does type inference have to do with traits? In C++, traits are used to get information relating to a specific type (the biggest int, the biggest float, etc). How does one do this using ML-like type inference?
Slashdot Mirror
In the UK, most maps use the British Grid projection. Google, in their international wisdom, appear to have used a different projection which causes the map to "appear wrong" to a UK person. Actually, the map is perfectly correct, it's just that Google are presenting it in a way which is not customary for the UK.
For example, try a search for postcode "EH1" on http://maps.google.co.uk, and the same on www.multimap.co.uk. Notice that the shape of the quarter-circle road system (Princes St, Melville Drive, the Bridges) is different on each.
> (traits are meaningless when you have either manifest types like scripting
> languages or type inference like ML)
What does type inference have to do with traits? In C++, traits are used to get information relating to a specific type (the biggest int, the biggest float, etc). How does one do this using ML-like type inference?