For this purpose I'm interested in Julia as an end user, to get stuff done, 
which is why I posted to julia-users rather than julia-dev.  

Python has, for example, the custom of subdirectory structures for modules, 
with __init__.py files, and the "from . import X" idiom, and so on.  There 
is also a set of distutils conventions for the setup.py file to prepare a 
program for distribution.  I haven't seen the equivalent for Julia.  Or 
maybe the Pkg documentation is intended to explain everything?



On Friday, December 12, 2014 11:38:46 PM UTC-8, [email protected] wrote:
>
> Tamas makes a good point, it depends on if your interest is in Julia as a 
> language or Julia as a way of getting stuff done.  Both communities are 
> active, but I doubt they have the same definition of "well written" :)
>
> Cheers
> Lex
>
> On Saturday, December 13, 2014 5:23:41 PM UTC+10, Tamas Papp wrote:
>>
>> I like reading library code from the Julia core team for learning 
>> purposes, especially libraries for 0.4. Given how fast Julia is moving, 
>> I would not expect anything super-polished at this stage outside 
>> libraries, especially since in scientific computing the programs 
>> themselves are used only a few times (compared to other kinds of 
>> software). 
>>
>> Best, 
>>
>> Tamas 
>>
>> On Fri, Dec 12 2014, Tom Fawcett <[email protected]> wrote: 
>>
>> > Hi, all.  I'm slowly moving over to Julia from Python.  There is just 
>> > enough of a difference of Julia from other languages that I'd like to 
>> find 
>> > a well-written, small to medium-sized Julia program to study its coding 
>> > style and code organization.  It doesn't have to be huge; just a 
>> > well-organized collection of modules and classes/types.  Any 
>> nominations 
>> > for exemplary Julia? 
>> > 
>> > (I've gone through various library code files, but libraries aren't 
>> > organized the same as programs.  I've skimmed a few of the programs in 
>> > Julia.jl but it's hard to determine what's considered well-written.) 
>> > 
>> > Thanks, 
>> > -Tom 
>>
>

Reply via email to