On 2011-06-18 07:00, Nick Sabalausky wrote:
"Jacob Carlborg"<d...@me.com> wrote in message
news:itgamg$2ggr$4...@digitalmars.com...
On 2011-06-17 18:45, Jose Armando Garcia wrote:
On Fri, Jun 17, 2011 at 1:15 PM, Jacob Carlborg<d...@me.com> wrote:
On 2011-06-14 15:53, Andrei Alexandrescu wrote:
Instead of complaining about others ideas (I'll probably do that as well
:)
), here's my idea:
https://github.com/jacob-carlborg/orbit/wiki/Oribt-Package-Manager-for-D
From website:
Spec and Config Files
The dakefile and the orbspec file is written in Ruby. Why?
Why ruby and not D with mixin? I am willing to volunteer some time to
this if help is needed.
-Jose
As I stated just below "The dakefile and the orbspec file is written in
Ruby. Why?". D is too verbose for simple files like these. How would it
even work? Wrap everything in a main method, compile and then run?
That would be better than forcing Ruby on people.
So you prefer this, in favor of the Ruby syntax:
version_("1.0.0");
author("Jacob Carlborg");
type(Type.library);
imports(["a.d", "b.di"]); // an array of import files
Or maybe it has to be:
Orb.create((Orb orb) {
orb.version_("1.0.0");
orb.author("Jacob Carlborg");
orb.type(Type.library);
orb.imports(["a.d", "b.di"]); // an array of import files
});
I think it's unnecessary verbose. BTW, DMD, Phobos and druntime is
forcing makefiles on people (I hate makefiles). DSSS forced an
INI-similar syntax on people.
If the config/spec files should be in D then, as far as I know, the tool
needs to:
1. read the file
2. add a main method
3. write a new file
4. compile the new file
5. run the resulting binary
This seems very unnecessary to me. Unnecessary IO, unnecessary
compilation, unnecessary processes (two new processes). The only thing
this will do is slowing down everything.
--
/Jacob Carlborg
