Gfortran 4.3 projects

[Daniel Franke]

2006/9/20, Tobias Burnus <burnus@net-b.de>:
> Daniel Franke wrote:
> > By any chance, is there also a list of "Junior Jobs" (as the KDE
> > people coined it)? I.e. tasks that can be done in a couple of hours by
> > newcomers to learn their way around which the core developers tend to
> > avoid because it's merely a nuisance to them?!
>
> I'm not aware of such a list, but going through the Fortran bugs in
> bugzilla (is a comparably short list) should give some ideas; otherwise
> some simpler Fortran 2003 might also be good starting points.
> (Like my trivial new_line patch, which still needs to be reviewed.)
> Fixing and enhancing the documentation is probably also a good idea.

Tobias,
true, for sure. I already started with intrinsic.texi a while ago and
hope to send in another doc patch these days. On the other hand, a few
days ago I found that  memory leak that, in the meanwhile,  was fixed
by Paul (thanks, btw). While I was able to describe the problem, I had
no clue where to start to fix it. There is the code in front of me and
... ufff. Yes. Somewhere in there. To stay with that example, I
assumed it could/would be a library problem and stated so - for those
involved, obvious enough, it was not in the library but somewhere else
(code generation?). Although I am used to steep learning curves and
RTFM, I am seriously lost here.

Since I heavily rely on gcc/gfortran during work and in private
projects, I would like to devote some time to the community in return.
Some small tasks that can be done without a degree in compiler
development - junior jobs so to say :)

Regards
       Daniel