News for hackers. Stuff that matters.
Re:Why we created Julia - new language for fresh approach to... by ludwigvan on Saturday February 18, 2012 @09:10AM (#3606605)
I think they are aiming for smooth transition for MATLAB users. They also have 1-index based arrays as opposed to 0-index .
Re:Why we created Julia - new language for fresh approach to... by wbhart on Saturday February 18, 2012 @09:22AM (#3606621)
It would certainly be nice if there was an option to use 0 based indices in blocks of code. It's understandable in that they are pitching at the technical community, and many mathematical papers and books are written with 1 based indices. But I am a mathematician who prefers 0 based indices.
Re:Why we created Julia - new language for fresh approach to... by fijal on Saturday February 18, 2012 @09:43AM (#3606660)
It seems like both 0 and 1 based arrays is asking for trouble :) I would prefer 0-based, but still prefer 1-based to mixed or optional.
Re:Why we created Julia - new language for fresh approach to... by javajosh on Saturday February 18, 2012 @01:43PM (#3607312)
We are scientists and so willing to compromise, yes? So how about 0.5-based arrays? :)
Re:Why we created Julia - new language for fresh approach to... by Danieru on Saturday February 18, 2012 @03:24PM (#3607647)
Only if it is in base .5
Re:Why we created Julia - new language for fresh approach to... by ViralBShah on Saturday February 18, 2012 @01:36PM (#3607278)
Actually, it is quite easy to implement 0 based indices or any other indexing scheme in julia, since all the array indexing code is implemented in julia itself.

https://github.com/JuliaLang/julia/blob/master/j/array.j#L15...

I personally would find multiple indexing schemes confusing both for usage as well as to develop and maintain. Given that 1 based indexing seems to be a popular choice among many similar languages, we just went ahead with that.

Re:Why we created Julia - new language for fresh approach to... by chancho on Saturday February 18, 2012 @03:29PM (#3607660)
Have you looked at the Haskell Ix class? http://www.haskell.org/onlinereport/ix.html

It generalizes the choice of 0 or 1 to an arbitrary starting index. So when you create an array you specify not just where it ends but also where it begins. This lets you do neat things (consider a filter kernel with range [-s,+s]^n instead of [1,2s]^n) and the extra complexity it adds can be hidden when not needed using for-statements or higher order functions.

Nobody uses it because the implementation is not very efficient and Haskellers have a chip on their shoulder about performance. It subtracts the origin and computes strides on every index, but you could easily avoid this by storing the subtracted base pointer and strides with the array. Of course when you go to implement it you'll see light on 0-based indexing :)

Re:Why we created Julia - new language for fresh approach to... by wbhart on Sunday February 19, 2012 @09:22AM (#3609394)
The problem with changing it in the library is that you'd also have to change it everywhere arrays are used in Julia itself.

The only way I could think to manage it would be a pragma which switches 0-based on for a given file. But this is doubtlessly not trivial.

Or there is the less elegant option of introducing a new operator for 0-based arrays. But this is liable to cause confusion I think.

Re:Why we created Julia - new language for fresh approach to... by svdad on Saturday February 18, 2012 @11:33PM (#3608655)
Perl still has this with $[ but it's deprecated as of 5.12.
Re:Why we created Julia - new language for fresh approach to... by TheoLib on Saturday February 18, 2012 @12:00PM (#3606969)
A number of programming languages allow an arbitrary range of indices for an array, including Ada, Fortran 77, and Pascal. See the "Specifiable Base Index" column in this table at Wikipedia: http://en.wikipedia.org/wiki/Comparison_of_programming_langu...
Re:Why we created Julia - new language for fresh approach to... by Bromskloss on Saturday February 25, 2012 @08:05PM (#3634422)
Actually, the main reason I want to do away with Matlab and Octave is that I can't stand the 1-indexing! When voicing that opinion among collegues, I have heard no-one disagree with me. If you are actually stuck with this in Julia as well, I don't think I will have anything more to do with it.
Re:Why we created Julia - new language for fresh approach to... by maximilian on Saturday February 18, 2012 @09:51AM (#3606677)
Fortran is 1-index as well. I think MATLAB gets its notational style from Fortran.
Re:Why we created Julia - new language for fresh approach to... by ludwigvan on Saturday February 18, 2012 @11:52AM (#3606944)
Actually, broadly speaking, I think math (think summation etc.) in general is usually 1-index based while programming is 0-index (due to memory locations so that the array index also points to the first element?).

Also see Dijkstra's take on the matter: http://www.cs.utexas.edu/users/EWD/ewd08xx/EWD831.PDF for

Re:Why we created Julia - new language for fresh approach to... by StefanKarpinski on Saturday February 18, 2012 @12:59PM (#3607171)
At first we were going to use 0-based indexing, but it made porting any Matlab code over very hard, which defeats a large part of the purpose of having Matlab-like syntax in the first place — to leverage the large amount of Matlab code and expertise that exists out there.

However, as I've used it more and more, 1-based indexing has really grown on me. I feel like I make far fewer off-by-one errors and actually hardly ever have to think about them. This has led me to conclude that 1-based indexing is probably easier for humans while 0-based indexing is clearly easier for computers.

Re:Why we created Julia - new language for fresh approach to... by wbhart on Saturday February 18, 2012 @01:35PM (#3607274)
Many divide-and-conquer algorithms seem to be easier to express with 0 based indexing, whereas quite a few array operations seem to be better with 1 based indexing. I can certainly understand and appreciate the different points of view, I just personally always think about algorithms with 0-based arrays.
Re:Why we created Julia - new language for fresh approach to... by warmfuzzykitten on Saturday February 18, 2012 @02:15PM (#3607420)
As does anyone trained in the C tradition, but it's annoying, too, to have to translate 1-based math formulas to the C convention. Having recently used Octave for the Stanford online ML class after a couple decades of C, C++ and Java, I doubt programmers will have trouble with the mental transition.
Re:Why we created Julia - new language for fresh approach to... by Peaker on Saturday February 18, 2012 @04:43PM (#3607836)
We shape our tools and then our tools shape us.

Be careful when generalizing from your own personal preferences and cognitive biases to what is easier for humans in general.

Re:Why we created Julia - new language for fresh approach to... by StefanKarpinski on Saturday February 18, 2012 @06:57PM (#3608128)
Well, for what it's worth, I certainly also "grew up" with 0-based indexing (actually, literally grew up since I was a kid when I learned Pascal). I'm just saying that 1-based has really grown on me and that I find myself thinking about avoiding off-by-one errors far less often when using 1-based indexing. There are other times when I really wish I was using 0-based indexing. However, I find that that latter are more often times when I'm doing libraryish internals code, whereas the former are more common when I'm doing high level userish code.
Re:Why we created Julia - new language for fresh approach to... by Peaker on Sunday February 19, 2012 @04:23AM (#3609029)
My experience is the exact opposite.

I find 1-based indexing to be weird/illogical and prone to off-by-1 errors.

Inclusive/exclusive ranges as in Python along with 0-based indexing means the likelihood of any off-by-1 is negligible...