rename jl/ to base/ #591

Closed
StefanKarpinski opened this Issue Mar 15, 2012 · 14 comments

Comments

Projects
None yet
4 participants
Owner

StefanKarpinski commented Mar 15, 2012

No description provided.

Member

aviks commented Mar 15, 2012

Everything in core should probably be assumed to loaded on startup. Anything in core that isn't loaded at startup should be moved into extra.

Owner

StefanKarpinski commented Mar 15, 2012

Agreed.

Member

vtjnash commented Mar 19, 2012

+1

I wonder if extras/ should be named something like packages/ or modules/, etc. so it is clear that it is the standard place to place additional code libraries. Many of the source files in examples/ could probably be moved in there too. I expect examples to be like an extended help file that demonstrates a complete program but several seem to be a mostly complete implementation of some data structure and without an actual example usage of it.

I'm also wondering if we will need some additional organization in extras/ (or whatever it gets called). I'm thinking it would be helpful to have some sort of folder structure defined sooner rather than later. That should makes it easy to just create git submodules and (eventually) a custom package manager, without worrying too much about file name conflicts. This might get us closer to resolving #432 too.

Owner

JeffBezanson commented Mar 19, 2012

I believe this will conflict with other files named core that I often have in this directory :)

Owner

StefanKarpinski commented Mar 19, 2012

How about a better name then?

Owner

JeffBezanson commented Mar 19, 2012

corelib?

Owner

StefanKarpinski commented Mar 19, 2012

How about stdlib since that's what we call it in the manual? Seems kind of windy though.

Member

aviks commented Mar 19, 2012

+1 to some organisation in extras/ , a folder for each package (winston, ad ... etc)

Member

vtjnash commented Mar 19, 2012

to me, stdlib sounds mentally confusing with the standard c header of the same name

another thought is that we could go with everything being in jl/ and move everything in there now to jl/core? with an additional folder for each "package". to make loading easier, we could also have a convention that load() on a folder tries instead to load a file of the same name from within that folder (which can then load the rest of it's needs).

Owner

StefanKarpinski commented Mar 19, 2012

That seems like a reasonable scheme to me. It helps keep all the Julia code in one place.

Owner

JeffBezanson commented Mar 19, 2012

Why should all the julia code be in one place?

Owner

StefanKarpinski commented Mar 19, 2012

Tidiness?

Owner

JeffBezanson commented Mar 19, 2012

I still think using core is a bad idea. How about base? Then we can also call the namespace of the standard library Base which is nice and short.

Owner

StefanKarpinski commented Mar 19, 2012

I like that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment