On Thursday, 13 February 2014 at 23:14:20 UTC, 1100110 wrote:
I think it's about time I gave back to this wonderful community.
I'm offering a $50 bounty on this.
(Preferably Bitcoins, but I'll use bountysource if desired.)
rules:
Has to be called -minimal
Has to fulfill Walter's original post. (listed below)
Has to split the separate parts into different flags as well as
-minimal(-nogc, -nomoduleinfo, etc. Naming is left to the
implementer).
This seems to be a good idea and has lots of support from the
community, would anyone like to chip in a few more bucks?
I haven't set the bounty yet, depends on if multiple people
chip in. I'll probably set it sometime tonight.
Let me know what y'all think, am I leaving anything out?
Thanks
On Tuesday, 11 February 2014 at 19:43:00 UTC, Walter Bright
wrote:
I've toyed with this idea for a while, and wondered what the
interest there is in something like this.
The idea is to be able to use a subset of D that does not
require any of druntime or phobos - it can be linked merely
with the C standard library. To that end, there'd be a
compiler switch (-betterC) which would enforce the subset.
(First off, I hate the name "better C", any suggestions?)
The subset would disallow use of any features that rely on:
1. moduleinfo
2. exception handling
3. gc
4. Object
I've used such a subset before when bringing D up on a new
platform, as the new platform didn't have a working phobos.
What do you think?
I'll throw in $300 extra (maybe more), but can you please first
formalize the requirements (list of flags, and what each flag
should mean, required unittests to pass etc).
I also think it's best to split into a few tasks (e.g. a task per
feature or compiler flag). This way it is:
- easier to verify correctness/completeness
- many people can work without interfering with each other
- easier to implement and grab a bounty
