1 |
Sorry for the crosspost, but it looks like this topic is approximately |
2 |
equivalently active on either lis, and I did not find the "submission |
3 |
instructions" perhaps because its not yet time for design submits :).. |
4 |
|
5 |
On Wednesday 03 December 2003 15:08, Daniel Robbins wrote: |
6 |
> I haven't looked at twisted, but a good solution suggested by nerdboy is |
7 |
> to have a design competition once we have the requirements finalized. |
8 |
|
9 |
So, we are going to do it according to "accepted practices" :). |
10 |
Seriously, I am glad to see it! And here is my entry ;). |
11 |
|
12 |
Well, this really is a proposal of the language to use for core stuff, not as |
13 |
much of a design. Ever since the implementation in Prolog was mentioned I was |
14 |
keeping some thoughts on the backburner and finally I decided to do a |
15 |
competing entry, for the reason's I'll try to outline. |
16 |
|
17 |
I have them nicely wrapped up here: |
18 |
http://dev.gentoo.org/~george/portage-ng_core-proposal.html |
19 |
|
20 |
To reiterate them shortly, Prolog is a really esoteric language and I am not |
21 |
sure we will be able to find enough people to feel comfortable about having |
22 |
the very core of portage-ng implemented in it. Also there might be issues of |
23 |
portability and efficiency.. |
24 |
|
25 |
On the other hand I understand the desire to stay clear off the C/C++ use and |
26 |
completely support it. Therefore I propose a middle-ground solution, to use a |
27 |
common compiled procedural language that was designed to enhance readability, |
28 |
modularization and ease maintaince of a large system. Oh, it is also very |
29 |
portable and widely awailable and is alive and well supported. |
30 |
What else? It took me only about two weeks (of like 1-2 hrs per day of |
31 |
reading) to get into it and sturt crunching out some code when I decided to |
32 |
learn it :).. (not Hellow World, but real code, mind you). |
33 |
|
34 |
But read-on for the details.. |
35 |
|
36 |
However that's not all. I have produced some basic prototyping code to |
37 |
illustrate what could be expected. The prototype is quite crude, as I did |
38 |
this during relatively rare breaks from writing an article (completely |
39 |
unrelated to CS :)), but it should serve the purpose. Did I say the code |
40 |
shoul be readable? So, even though I do not expect many people to be familiar |
41 |
with that language I would still suggest trying to look at the code. You are |
42 |
in for a one nice surprise ;). |
43 |
(I am not revealing the name of language in this posting deliberately, because |
44 |
I want people to read through arguments first). |
45 |
|
46 |
The code is available here: |
47 |
http://dev.gentoo.org/~george/proto_portage-0.7.5.tar.bz2 |
48 |
but you will probably want to read the text before that. |
49 |
|
50 |
In any case, if you want to jump in, just a short install instruction: |
51 |
run "emerge gnat booch_components " |
52 |
then untar the package and run make |
53 |
Although reading INSTALL that comes with the package might be usefull too ;) |
54 |
(it has some details in case you experience problems). |
55 |
|
56 |
George |
57 |
|
58 |
|
59 |
|
60 |
-- |
61 |
gentoo-dev@g.o mailing list |