|
|
|
|
|
by dmbaggett
3535 days ago
|
|
It requires a lot of code because the rules that govern the use of fares on a ticket are insanely complicated -- literally beyond anything you could possibly imagine a priori. There are dozens of rule "categories", each larded up with tons of complexity. There's even "Rule Category 25: Fare By Rule" which is essentially a complete macro facility for fares, allowing carriers to literally take an arbitrary fare's rules, modify them in all kinds of random ways, and publish the result as a new "virtual" fare. As for the GDSes, their code is primarily TPF assembly. So now add the LoC blow-up of using a very low-level language. There are like 25 people in the world who understand this stuff, and half of them likely work at ITA/Google. |
|
As to the "categories", people at Sabre working with them used to say in some cases you can not even be sure if the calculation (of a ticket price - "fare") will end in finite time, so the "macro language" is apparently Turing-complete!