Türkiz Talay

Türkiz Talay (born April 8, 1974) is a Turkish-German actress.

Türkiz Talay
Born
Türkiz Talay

(1974-04-08) April 8, 1974
Years active1987present
Websitehttp://www.tuerkiz-talay.de/

Filmography

Film
Year Film Role Notes
2006Goldene Zeiten Soapdarstellerin #2Credited as Tükiz Talay
1999Alte ZeitenNadja

Television

Year Film Role Notes
2006Hammer & HartYüksel
2006Türkisch für AnfängerFrau Sismanoglu3 episodes
2003Im Namen des GesetzesTanja Schulz
2003Fliege kehrt zurück
2002KüstenwacheMaria Ehrlich1 episode
2002S.O.S. BarracudaMaria Rodriguez2 episodes
2002Alles getürkt!Nihan Karagöz
2000Der Puma - Kämpfer mit HerzFatma
2000Auf eigene GefahrMelah Taskin1 episode
1999Die KommissarinMeryem1 episode
1998Die Schule am SeeCarla1 episode
1997Gegen den WindRebecca1 episode
1996SK-BabiesNesrin Üstünkaya6 episodes
1995Frauenarzt Dr. Markus MerthinGül1 episode
1987Moskito - Nichts sticht besser!
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.
gollark: Oh, and the error handling is terrible and it's kind of the type system's fault.

References


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