From: | Thomas Koenig <tkoenig@netcologne.de> |
Newsgroups: | comp.compilers |
Date: | Fri, 21 Oct 2022 21:32:06 -0000 (UTC) |
Organization: | news.netcologne.de |
References: | 22-10-029 22-10-031 22-10-035 22-10-036 |
Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="49329"; mail-complaints-to="abuse@iecc.com" |
Keywords: | courses |
Posted-Date: | 21 Oct 2022 19:46:25 EDT |
Spiros Bousbouras <spibou@gmail.com> schrieb:
> On Thu, 20 Oct 2022 11:30:40 +0200
> Hans-Peter Diettrich <DrDiettrich1@netscape.net> wrote:
>> On 10/19/22 10:30 AM, Nuno Lopes wrote:
>>
>> > PL is very broad, so I don't know exactly what you like, but I suggest you
>> > start participating in an open-source project to learn how production code
>> > is developed and to improve your own coding skills.
>>
>> Open source projects often direct newbies to their to-do list. That's
>> the "hall of shame" with problems beyond the skills or knowledge of the
>> "core" developers.
>
> First , participating in an open source project doesn't mean that one waits
> to be "directed". They can simply notice a bug and send a fix or add some new
> functionality. Second , issues on the todo list may be stuff that core
> developers don't know how to do or it may be stuff that they haven't got
> around to doing. In my experience it is almost always the latter.
A quote from the "Quickstart Guide to Hacking GFortran":
What kind of PR to start with
[...]
Traditionally, internal compiler errors on invalid code have been
considered relatively easy. But you may always find a hard one...
Return to the
comp.compilers page.
Search the
comp.compilers archives again.