| 1 |
On 10.01.02 12:24 +0100(+0000), Karl Trygve Kalleberg wrote: |
| 2 |
> On Tue, Jan 08, 2002 at 11:10:39AM -0600, Damon M. Conway wrote: |
| 3 |
> >From what I have understood, eclasses is primarily about bringing a few of |
| 4 |
> the OOP principles to bash scripts. As a computer-linguist, I find this |
| 5 |
> attempt misguided at best, but as a system administrator/bash script |
| 6 |
> hacker, I find the idea appealing. |
| 7 |
> |
| 8 |
> Since eclasses are associated with a learning curve, would it not be |
| 9 |
> preferrable to recast the whole inheritance thing in a proper |
| 10 |
> object-oriented language and rather build a support framework for it there |
| 11 |
> ? |
| 12 |
> |
| 13 |
> For instance, use scsh (okay, okay, so Scheme might not be popular with |
| 14 |
> the crowd) or Python. If you take a look at SCons, you'll see Make recast |
| 15 |
> into Python, with all the benefits that gives you (stable, clean, |
| 16 |
> well-known language, lots of documentation, lots of support libraries, |
| 17 |
> cross-platform runtime). |
| 18 |
> |
| 19 |
> Just stirring things up since the eclasses debate seems to be coming |
| 20 |
> regardless. |
| 21 |
> |
| 22 |
hmm using scheme sounds very appealing, but the problem is that |
| 23 |
many of us have an unnatural fear of parenthesises... By using |
| 24 |
OO portage would be indeed more powerful and it would make it possible |
| 25 |
for a user to override doman if he wishes so easily, or to add a hook |
| 26 |
procedure that is run whenever src_compile is ready... |
| 27 |
|
| 28 |
- Einar Karttunen |
Archives