Re: Not receiving emails from issues.dlang.org

Thank you, I'm all set now.

On Wednesday, 16 April 2014 at 00:51:37 UTC, Brad Roberts via 
Digitalmars-d wrote:
> I've kicked things a little, but need to figure out better why 
> it didn't go out on it's own.
>
> On 4/15/14, 5:26 PM, Kevin Lamonte via Digitalmars-d wrote:
>> I am trying to reset my password on the bug tracker in order 
>> to file a new bug, but the reset emails
>> appear to be disappearing in the ether.  Anyone else have this 
>> problem?

via Digitalmars-d | 16 Apr 10:46 2014

Re: DIP60: <at> nogc attribute

On Tuesday, 15 April 2014 at 23:54:24 UTC, Matej Nanut via 
Digitalmars-d wrote:
> This shouldn't be a problem if you plonk  <at> nogc: at the top of 
> your own file, as it won't compile anymore if you try to call 
>  <at> gc functions.

It is a problem if you are allowed to override  <at> nogc with  <at> gc, 
which is what the post I responded to suggested.

Not receiving emails from issues.dlang.org

I am trying to reset my password on the bug tracker in order to 
file a new bug, but the reset emails appear to be disappearing in 
the ether.  Anyone else have this problem?

XCB Bindings?

Does anyone know of any (preferably complete) XCB bindings for D?

Re: DIP60: <at> nogc attribute

On 4/15/2014 1:10 PM, H. S. Teoh via Digitalmars-d wrote:
> Is automatic inference of  <at> nogc anywhere within our reach right now?

Yes, it's no harder than pure or nothrow inference is.

Function Literals

Valid, but rejected by DMD:

void function() a = {writeln("a");}, b = body {writeln("b");};

Valid, but rejected by DMD:

void function() a {writeln("a");}

Invalid, accepted by DMD:

void function() a = {writeln("a");};

Invalid, accepted by DMD:

// No semicolon needed if there's only one
void function() a = {writeln("a");}

For fun, accepted by DMD:

void function() bar[](alias t)(int x, int y) = { writeln("wat"); 
};

DIP60: <at> nogc attribute

http://wiki.dlang.org/DIP60

Start on implementation:

https://github.com/D-Programming-Language/dmd/pull/3455

Re: on interfacing w/C++

On 4/15/14, 2:22 AM, Manu via Digitalmars-d wrote:
> We still have no member function pointers either.

I'd advocate against supporting C++ member function pointers. -- Andrei

Re: on interfacing w/C++

"Manu via Digitalmars-d" <digitalmars-d <at> puremagic.com> wrote in message 
news:mailman.9.1397553786.2763.digitalmars-d <at> puremagic.com...

> Huh? Do methods work now? Since when?

Since I needed them for DDMD.

> We still have no member function pointers either.

Meh. 

Kagamin via Digitalmars-d | 15 Apr 10:07 2014

Re: mail list bounces

support <at> yahoo.com?

What's the deal with "Warning: explicit element-wise assignment..."

We've just enabled warnings as errors in our build system at work and 
suddenly:

Warning: explicit element-wise assignment <exprnew> is better than <expr>

where <exprnew> and <expr> are expressions picked from the code. For 
example, this wasn't accepted:

writeAvail_[0 .. buf.length] = buf;

but this was:

writeAvail_[0 .. buf.length] = buf[];

The type of the involved variables were as trivial as ubyte[] and in 
ubyte[] respectively.

What's the idea?

Andrei


Gmane