Ahmed Al Masli

Ahmed Faraj Hussein Al Masli (Arabic: أحمد فرج حسين المصلي) (born March 4, 1979) is a Libyan international footballer. He currently plays for the Tunisian Ligue Professionnelle 1 club Club Athlétique Bizertin, as a striker. He is also a member of the Libyan national team.

Ahmed Al Masli
احمد المصلي
Personal information
Full name Ahmed Faraj Hussein Al Masli
Date of birth (1979-12-28) December 28, 1979
Place of birth Benghazi, Libya
Height 1.79 m (5 ft 10 12 in)
Playing position(s) Striker
Club information
Current team
Tersana SC
Number 9
Youth career
1993–2000 Tahaddy
Senior career*
Years Team Apps (Gls)
1998–2001 Tahaddy (??)
2004–2006 Ittihad Tripoli 32 (16)
2006–2007 Nasr Benghazi 22 (14)
2007–2008 Ittihad Tripoli 9 (7)
2008 Arabi 2 (2)
2008–present Ahly Benghazi 40 (11)
2009 Stade Tunisien
2009–2010 Hilal
2011–2012 El-Entag El-Harby
2012–2013 Club Athlétique Bizertin
Tersana SC
National team
2003–2010 Libya 45 (29)
* Senior club appearances and goals counted for the domestic league only and correct as of January 27, 2007

Career

By scoring against Al Hilal on November 21, 2008, al-Masli has now scored against every team in the Libyan Premier League. He is the only player ever to do so.

After an impressive couple of seasons with Ahly Benghazi (2008–10), it was announced that the Egyptian Premier League side El-Entag El-Harby had signed the striker on a two-year deal.

On December 27, 2011, the Tunisian Ligue Professionnelle 1 side Club Athlétique Bizertin had signed the striker on a one year and al half deal.

gollark: Well, yes, but they're byte sequences.
gollark: I mean, it's better than C and stuff, and I wouldn't mind writing simple apps in it.
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.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.