date:20120320

Re: Proposal: user defined attributes

2012-03-20 Thread Jacob Carlborg


On 2012-03-19 22:51, Andrej Mitrovic wrote:

On 3/19/12, Jacob Carlborg  wrote:

Yeah, but that will complicate the retrieval of the information.


What is so complicated about extracting fields? Just iterate via .tupleof:


It wasn't actually that much more complicated. But now there is one 
extra enum for each NonSerialized field.


--
/Jacob Carlborg

Re: Keyword arguments / Named parameters library implementation

2012-03-20 Thread Matthias Walter

On 03/19/2012 08:21 PM, Andrej Mitrovic wrote:
> On 3/19/12, Matthias Walter  wrote:
>> Hi,
>>
>> I've written a small module (at the moment called utils.keywordargs)
>> which simulates keyword arguments (aka named parameters).
> 
> Cool. A small tip (in case you didn't already know):
> 
> You can use allSatisfy from std.typetuple when checking a single
> constraint on multiple parameters: static
> assert(allSatisfy!(isKeywordArgument, H, V));

Didn't know that - thanks a lot!

Re: Keyword arguments / Named parameters library implementation

2012-03-20 Thread Matthias Walter

On 03/19/2012 07:53 PM, bearophile wrote:
> Matthias Walter:
> 
>> I've written a small module (at the moment called utils.keywordargs)
>> which simulates keyword arguments (aka named parameters). The
>> documentation can be found here,
> 
> Regardless the implementation quality of your code, I wait for the real thing 
> :-)

I understand "the real thing" as a language implementation of keyword
arguments instead of a library "workaround", right?

Re: Proposal: user defined attributes

2012-03-20 Thread Jacob Carlborg


On 2012-03-19 22:00, Andrei Alexandrescu wrote:


I salute creative uses of the language over defining new features.

Andrei


The actual point of user defined attributes it to be able to create 
domain specific attributes so we don't have to add new features to the 
language. This is also to have a sane syntax for the attributes.


I think in several cases D could have chose to implement a more general 
feature but instead implemented a very specific feature or hack.


Example:

If D supported passing delegates to a function after the function call 
several language features could have been implemented in the library 
instead.


void synchronized (void delegate () dg)
{
try
{
lock();
dg();
}
finally
unlock();
}

synchronized {
// do something
}

In the same way foreach can be implemented in a library function:

void foreach (T) (T[] arr, void delegate (T) dg)
{
for (size_t i = 0; i < arr.length; i++)
dg(arr[i]);
}

auto arr = [3, 4, 5];

foreach (arr ; e // this is the parameter to the delegate) {
writeln(e);
}

--
/Jacob Carlborg

Re: Proposal: user defined attributes

2012-03-20 Thread F i L


Jacob Carlborg wrote:
If D supported passing delegates to a function after the 
function call several language features could have been 
implemented in the library instead.


void synchronized (void delegate () dg)
{
try
{
lock();
dg();
}
finally
unlock();
}

synchronized {
// do something
}

In the same way foreach can be implemented in a library 
function:


void foreach (T) (T[] arr, void delegate (T) dg)
{
for (size_t i = 0; i < arr.length; i++)
dg(arr[i]);
}

auto arr = [3, 4, 5];

foreach (arr ; e // this is the parameter to the delegate) {
writeln(e);
}


That's pretty slick. D would need delegate inlining + 
@forceInline before foreach could be expressed this way though.

Re: Mono-D@GSoC - Mentor needed

2012-03-20 Thread F i L

On Monday, 19 March 2012 at 21:18:02 UTC, alex wrote:

Hi everyone,

It may sounds a bit annoying because I already was asking
everywhere in the IRC channels but still had no success -

Is there anyone who wants to be my GSoC mentor for the Mono-D
project?

In the case you don't know what Mono-D is all about:
It's about creating a D language binding for MonoDevelop.
(http://monodevelop.com/Screenshots )

There are couple of things that are already implemented - like
a relatively nice but fast code completion, build support,
small refactoring operations like they can be used in every
modern IDE and few other things which will make application
development with D a lot easier - especially for D newbies.
(Debugging is also available via gdb on Linux systems - so
yeah, why not? :))

The main road map for this summer of code is available under
https://github.com/aBothe/Mono-D/blob/master/MonoDevelop.DBinding/Remaining%20features.txt
- Especially things like the evaluation of constant expressions
and CTFE made e.g. a pre-compile-time view of mixin expressions
possible! - This would be more than nice, I guess!

So if you want to support D (and perhaps me, too ;)) - be a
mentor for GSoC to let D roll a bit more!

Further project info @ http://mono-d.alexanderbothe.com
For contact, you can speak to me in the #d and #d.mono-d
channel on freenode - I'm called 'alex|D-Guy' there

Bump.

This is a great project, and IMO, key to the popularity of D
among a wider audience. Best of luck, Alex. Sounds like you've
got some great ideas planned.

1 2 >

1 - 100 of 122 matches

Mail list logo