I don't understand your question that well. You state, that you have problems understanding the type system, which leads to more complex code. I don't fully get the connection between not understanding the type system and more complex code. I'd expect far more troubling problems from not understanding the type system, than just a few lines of additional code. Is the problem, that you're rather used to OOP, or pure pure imperative programming, which makes it difficult for you to write concise code in Julia? Can you give a concrete example, where the code in Julia is more complicated than in C/Python? I find this very interesting, as I'm always in search for examples, which can be expressed concisely in other languages, but not in Julia. ( So far I've found nearly none, besides some domain specific features)
Best, Simon Am Mittwoch, 22. Oktober 2014 13:11:03 UTC+2 schrieb Andreas Lobinger: > > Hello, > > i'm now a julia user for some time, but still i have problems (comming > from a c, f77, matlab, python background) to understand the type system. > Especially when i try to integrate own code into packages (happened to > Cairo + Compose, pending for Winston) i seem to choose always a more > complicated way (my observation, code similar in py or c just looks > shorter...) because somehow things do not match. > > So. > > What to read to understand the julia approach to types and type > interference? > > Wishing a happy day, > Andreas > > >
