On 1/31/14, 9:40 AM, Andrej Mitrovic wrote:
> On 1/31/14, Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> wrote:
>> Andrej, could you please file two issues under bugzilla
>> with the respective tags ldc and gdc? I'll see if I can place bounties
>> on them.
>
> That's a great idea! Here we go:
>
> https://d.puremagic.com/issues/show_bug.cgi?id=12048
> https://d.puremagic.com/issues/show_bug.cgi?id=12049

Added the LDC keywords (GDC already existed) and assigned it to 12048.

Andrei

On Friday, 31 January 2014 at 21:56:16 UTC, Andrej Mitrovic wrote:
> On 1/31/14, Dicebot <public@dicebot.lv> wrote:
>> At any time you can just download those, make any changes you
>> need and run `makepkg`. Or just use build() function from
>> PKGBUILD as a base for your own build script.
>
> This is great, I could start hacking on GDC then. Perfect, thanks!

+1. This is fantastic, I can now quickly start hacking about in GDC and learn the ropes. Hopefully I can contribute something back sooner rather than later.

Cheers,
ed

On 1/31/14, 12:44 PM, Iain Buclaw wrote:
> On 31 January 2014 01:39, Andrei Alexandrescu
> <SeeWebsiteForEmail@erdani.org> wrote:
>> Who's that guy and what code did he write? If no response, let's redo his
>> work. We should not be afraid of it.
>>
>
> David Friedman, I'm in direct contact with him and give both him and
> Donald (the FSF assignments clerk) a nudge over the issue once every
> couple of months.  Whilst David has no problem, he is in the
> unfortunate position of having his IP owned by a company.  And at last
> check, they were still dealing with clauses in the assignment.
>
> As for the codebase, I can say that around 60% has been potentially
> re-written since I picked it up in 2008/2009.

OK, we need to push this forward. If you think I could help, please send me his contact information. If you think the situation has reached an impasse, I'd say taskify (sic!) the code to be replaced and let's just rewrite it. It's all public and visible so the differences will be obvious.

>> An increasing number of people depend on GDC for getting work done.
>> Including a couple of projects here at Facebook. Yet the simple reality is
>> that even if I summoned TODAY one of our engineers with "get on helping gdc
>> full time", that engineer would have absolutely no idea where to start.
>>
>
> The same could be said with DMD.  I'd never expect someone to pick up
> a 20k codebase in a week, but one can do it in small steps.  In my
> opinion, the best way to get stuck into GDC is to do a couple of
> frontend merges (2.064 -> 2.065 -> future).

Here's where I think in fact DMD and GDC are very different and could use a lot more alignment. There are literally thousands of mini-tasks for dmd, druntime, etc. documented on bugzilla. Contributors have invariably started by fixing something in bugzilla that they wished done and figured it can't be too complicated.

Think of it this way: where would be DMD right now if instead of bugzilla we'd have a private list maintained by Walter? That's the situation GDC is in.

Bugzilla, bugzilla, bugzilla. Know what I'm sayin'?

> Differences between gdc and dmd in the frontend implement are important.
>
> GCC has a strict backend and will ICE at any opportunity it can find.
> As GDC has been well tailored to this over the years to produce
> correct code for GCC.  Things like this in GCC can flag up any big
> problems in the frontend quite easily.  Regardless of whether or not
> DMD compiles it without a hitch.
>
> Having arbitrary changes to the frontend means that not just anyone
> can pick up the latest version of D and slot it in.  Internal
> knowledge of what changes are present in that patch, and why in my
> head after months of study and testing.  It makes merges more
> difficult, setting aside changes in the frontend have a hidden
> knock-on effect in the glue.

I see. The way I'm thinking of this is we can improve the front-end to make things easier for you and LDC. Again this takes figuring out what discernible steps could be taken and documenting them under bugzilla.

>> I'll do my best on my side to help with very concrete bits, i.e. put
>> bounties on important issues or have legal contact people for signatures.
>> But I need to know!
>>
>
> If you can get me in touch with your guy, I could do with a hand in
> having a third party look over my own code reviews, which doesn't
> require any previous knowledge of gdc.
>
> http://gcc.gnu.org/codingconventions.html

Done. Check your inbox.


Andrei

On 1/31/14, 3:10 PM, ed wrote:
> On Friday, 31 January 2014 at 21:56:16 UTC, Andrej Mitrovic wrote:
>> On 1/31/14, Dicebot <public@dicebot.lv> wrote:
>>> At any time you can just download those, make any changes you
>>> need and run `makepkg`. Or just use build() function from
>>> PKGBUILD as a base for your own build script.
>>
>> This is great, I could start hacking on GDC then. Perfect, thanks!
>
> +1. This is fantastic, I can now quickly start hacking about in GDC and
> learn the ropes. Hopefully I can contribute something back sooner rather
> than later.

This information should go in a prominent place on the gdc website or wiki. Iain?

Andrei

On Saturday, 1 February 2014 at 16:20:33 UTC, Andrei Alexandrescu wrote:
> This information should go in a prominent place on the gdc website or wiki. Iain?

It seems some of my posts from gmail didn't go through to the forums, argh. Anyway, I've added this instruction:

http://wiki.dlang.org/GDC/Installation#Arch_Linux_.28also_Manjaro_Linux.29

On Saturday, 1 February 2014 at 16:37:33 UTC, Andrej Mitrovic wrote:
> On Saturday, 1 February 2014 at 16:20:33 UTC, Andrei Alexandrescu wrote:
>> This information should go in a prominent place on the gdc website or wiki. Iain?
>
> It seems some of my posts from gmail didn't go through to the forums, argh.

Likewise, I haven't received any mail since 9.40am this morning. Someone poke Brad. :-)

On Saturday, 1 February 2014 at 16:20:33 UTC, Andrei Alexandrescu wrote:
> On 1/31/14, 3:10 PM, ed wrote:
>> On Friday, 31 January 2014 at 21:56:16 UTC, Andrej Mitrovic wrote:
>>> On 1/31/14, Dicebot <public@dicebot.lv> wrote:
>>>> At any time you can just download those, make any changes you
>>>> need and run `makepkg`. Or just use build() function from
>>>> PKGBUILD as a base for your own build script.
>>>
>>> This is great, I could start hacking on GDC then. Perfect, thanks!
>>
>> +1. This is fantastic, I can now quickly start hacking about in GDC and
>> learn the ropes. Hopefully I can contribute something back sooner rather
>> than later.
>
> This information should go in a prominent place on the gdc website or wiki. Iain?
>

Both.  I want to build up the website to have at least the core set of information readily available (via more clickable menus on the top).

On 1/31/14, Dicebot <public@dicebot.lv> wrote:
> For any Arch Linux
> (and thus Manjaro) package there is a matching entry in SVN
> repository with build script.

Thanks again, I'm building it right now. So far everything seems to work ok. I've added your instructions to the wiki:

http://wiki.dlang.org/GDC/Installation#Arch_Linux_.28also_Manjaro_Linux.29

On Saturday, 1 February 2014 at 18:54:53 UTC, Andrej Mitrovic wrote:
> On 1/31/14, Dicebot <public@dicebot.lv> wrote:
>> For any Arch Linux
>> (and thus Manjaro) package there is a matching entry in SVN
>> repository with build script.
>
> Thanks again, I'm building it right now. So far everything seems to
> work ok. I've added your instructions to the wiki:
>
> http://wiki.dlang.org/GDC/Installation#Arch_Linux_.28also_Manjaro_Linux.29

Please note that, as far as I am aware, GDC development is done in master (4.9) branch and only occasionally merged into 4.8 branch. So if you want to actually contribute something, gdc-git from AUR should be of more interest.