Fernando Pérez Pascal

Fernando Pérez Pascal (born October 3, 1964) is a Mexican former professional tennis player.

Fernando Pérez
Full nameFernando Pérez Pascal
Country (sports) Mexico
Born (1964-10-03) October 3, 1964
Height5 ft 11 in (180 cm)
PlaysRight-handed
Prize money$12,170
Singles
Highest rankingNo. 356 (November 23, 1987)
Doubles
Career record3–5
Highest rankingNo. 169 (May 15, 1989)
Team competitions
Davis Cup7–6

Biography

A native of Mexico City, Pérez was the world's top ranked junior doubles player in 1982.

Pérez played college tennis for Louisiana State University (LSU) and won two Southeastern Conference singles championships, the first in 1983 and the second as a senior in 1986.[1] During his collegiate career he also represented Mexico in international competition, including the 1983 Pan American Games in Caracas, where he was runner-up to American Greg Holmes in the singles event. In 1986 he teamed up with Leonardo Lavalle for a Davis Cup doubles win over Boris Becker (and Andreas Maurer), which helped Mexico secure a place in the World Group quarter-finals.[2]

In the late 1980s, Pérez competed briefly on the professional tour, reaching a best singles ranking of 356 in the world. As a doubles player he was a semi-finalist at the 1989 WCT Tournament of Champions in Forest Hills and reached three finals on the Challenger circuit.

Pérez, who met his wife Beth while at LSU, returned to Mexico after college but since the 1990s has lived in the United States.[3]

gollark: Speaking specifically about the error handling, it may be "simple", but it's only "simple" in the sense of "the compiler writers do less work". It's very easy to mess it up by forgetting the useless boilerplate line somewhere, or something like that.
gollark: Speaking more generally than the type system, Go is just really... anti-abstraction... with, well, the gimped type system, lack of much metaprogramming support, and weird special cases, and poor error handling.
gollark: - They may be working on them, but they initially claimed that they weren't necessary and they don't exist now. Also, I don't trust them to not do them wrong.- Ooookay then- Well, generics, for one: they *kind of exist* in that you can have generic maps, channels, slices, and arrays, but not anything else. Also this (https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/), which is mostly about the file handling not being good since it tries to map on concepts which don't fit. Also channels having weird special syntax. Also `for` and `range` and `new` and `make` basically just being magic stuff which do whatever the compiler writers wanted with no consistency- see above- Because there's no generic number/comparable thing type. You would need to use `interface{}` or write a new function (with identical code) for every type you wanted to compare- You can change a signature somewhere and won't be alerted, but something else will break because the interface is no longer implemented- They are byte sequences. https://blog.golang.org/strings.- It's not. You need to put `if err != nil { return err }` everywhere.
gollark: Oh, and the error handling is terrible and it's kind of the type system's fault.
gollark: If I remember right Go strings are just byte sequences with no guarantee of being valid UTF-8, but all the functions working on them just assume they are.

See also

References
  1. "Fernando Perez One Of The Area's Best Tennis Players Built His Reputation Mostly In Mexico". The Morning Call. September 20, 1990.
  2. "U.S. Rebounds at Pan Am". The New York Times. August 26, 1983.
  3. "Sharing His Racquet Upper Bucks Director Has Pro Background". The Morning Call. April 7, 1994.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.