Yes – in fact, the entire point of having a pre-1.0 version number is to indicate that you should expect that APIs and the language itself will change in backwards incompatible ways. Ditto between 1.0 and 2.0. That said, I think that between deprecations and Compat.jl keeping code up to date with Julia master is not too bad.
On Sat, Dec 20, 2014 at 9:14 AM, John Myles White <[email protected]> wrote: > Julia is a _lot_ less mature than Fortran or Python. Between Julia 0.3 and > Julia 1.0 I am pretty sure there will changes as substantial as the Python > 2 and Python 3 changes. We've tried to provide deprecation periods for > changes, but there's going to be more changes than in Fortran. > > -- John > > On Dec 20, 2014, at 7:22 AM, Sergio Rojas <[email protected]> wrote: > > > > > Hello, > > > > Starting to explore Julia, I am wondering about > > its compatibility between versions for long term > > projects. For instance, we can still compile very > > old fortran codes without much pain, which in > > general does not go further than using a > > compiling option. This compatibility helps in > > developing via Fortran big projects that will last for years > > without worrying on wasting time unnecessarily on rewriting > > already tested piece of code. > > > > On the contrary, running Python code from previous > > versions on the new set up (say running Python 2 scripts > > on Python 3 could be a pain. One needs o spend a lot of time > > on it). > > > > Is Julia evolving via the incompatibility between versions as` > > Python is doing? > > > > Sergio > > > >
