Those are some cool new features.
The std.cover documentation isn't on the site yet. 

Chris

> Some things of note:
> 
> 1) This includes a new code coverage analyzer for dmd (I think gcov
> should work for gdc users). I've been wanting to add this for 20
> years, I finally realized it was a piece of cake. Took me 3 hours to
> write, 3 hours to tweak. I shoulda done it a long time ago. I can't
> believe some third party tools to do this cost $800+.
> 
> 2) The submissions for bug reports on complex numbers has risen a lot
> lately, and I never get them for the C compiler. This means that
> nobody uses complex numbers in C, but they do in D. Interesting!
> 
> 3) This incorporates a new 'header' generator capability, written by
> Dave Fladebo. I goofed it up merging it in, so it is disabled at the
> moment (just the source for it is included). I hope to get it working
> by the next update.
> 
> http://www.digitalmars.com/d/changelog.html
> 

Okay, I've tried the .mangleof property:

> module test;
>
> import std.stdio;
>
> int funcA()
> {
> }
> 
> class A {
> }
>
> void main()
> {
> 	
> 	A a = new A;
>
> 	alias long B;
> 	
> 	writefln( A.mangleof );
>	writefln( a.mangleof ); 
> 	writefln( B.mangleof );
> 	writefln( funcA.mangleof );
> }


OUTPUT:

C4test1A
C4test1A
l
i

So I see that functions still aren't really supported, since the mangled output just returns the return type. It would be fairly useful if we could get the actual mangled name of the whole function somehow.

-JJR

Walter Bright wrote:
> Some things of note:
> 
> 1) This includes a new code coverage analyzer for dmd (I think gcov should
> work for gdc users). I've been wanting to add this for 20 years, I finally
> realized it was a piece of cake. Took me 3 hours to write, 3 hours to tweak.
> I shoulda done it a long time ago. I can't believe some third party tools to
> do this cost $800+.

Hm, for one of my projects -cov crashes dmd, and for some of the others .lst file isn't created. What could be the problem?

John Reimer wrote:
> Okay, I've tried the .mangleof property:
>> int funcA()
>> {
>> }
>> void main()
>> {
>>     writefln( funcA.mangleof );
>> }
> 

> OUTPUT:
> 
> C4test1A
> C4test1A
> l
> i
> 
> So I see that functions still aren't really supported, since the mangled output just returns the return type. It would be fairly useful if we could get the actual mangled name of the whole function somehow.

It works for function pointers. So you can say:
writefln((&funcA).mangleof)
and get:
PFZi.

AWESOME!!
I think in your example, funcA was evaluated as a property, hence it's an int. Looks like DMD is correct.

"Derek Parnell" <derek@psych.ward> wrote in message news:1wsrogqlqzr5u$.csgg5emymae2$.dlg@40tude.net...
> analyzation (n): The act of analyzing anything past the point of diminishing returns. A natural behaviour.

lol :)

"kris" <fu@bar.org> wrote in message news:dn0nnf$2ulb$1@digitaldaemon.com...
> Nice! The -cov is gonna be *really* useful

I know. When I've used them before, the results were very rewarding.

"Ivan Senji" <ivan.senji_REMOVE_@_THIS__gmail.com> wrote in message news:dn11qv$dr0$1@digitaldaemon.com...
> Walter Bright wrote:
> > Some things of note:
> >
> > 1) This includes a new code coverage analyzer for dmd (I think gcov
should
> > work for gdc users). I've been wanting to add this for 20 years, I
finally
> > realized it was a piece of cake. Took me 3 hours to write, 3 hours to
tweak.
> > I shoulda done it a long time ago. I can't believe some third party
tools to
> > do this cost $800+.
>
> Hm, for one of my projects -cov crashes dmd, and for some of the others .lst file isn't created. What could be the problem?

I don't know. Can you cut it down to size and file a bug report?

In article <dn1e5b$u70$1@digitaldaemon.com>, Don Clugston says...
>
>John Reimer wrote:
>> Okay, I've tried the .mangleof property:
>>> int funcA()
>>> {
>>> }
>>> void main()
>>> {
>>>     writefln( funcA.mangleof );
>>> }
>> 
>
>> OUTPUT:
>> 
>> C4test1A
>> C4test1A
>> l
>> i
>> 
>> So I see that functions still aren't really supported, since the mangled output just returns the return type. It would be fairly useful if we could get the actual mangled name of the whole function somehow.
>
>It works for function pointers. So you can say:
>writefln((&funcA).mangleof)
>and get:
>PFZi.
>
>AWESOME!!
>I think in your example, funcA was evaluated as a property, hence it's
>an int. Looks like DMD is correct.

I'm going to file this under "really freaking awesome" myself.

- EricAnderton at yahoo

In article <dn0i6d$2pgk$1@digitaldaemon.com>, Walter Bright says...
>
>Some things of note:
>
>1) This includes a new code coverage analyzer for dmd (I think gcov should work for gdc users). I've been wanting to add this for 20 years, I finally realized it was a piece of cake. Took me 3 hours to write, 3 hours to tweak. I shoulda done it a long time ago. I can't believe some third party tools to do this cost $800+.
>
>2) The submissions for bug reports on complex numbers has risen a lot lately, and I never get them for the C compiler. This means that nobody uses complex numbers in C, but they do in D. Interesting!
>
>3) This incorporates a new 'header' generator capability, written by Dave Fladebo. I goofed it up merging it in, so it is disabled at the moment (just the source for it is included). I hope to get it working by the next update.
>
>http://www.digitalmars.com/d/changelog.html

Walter, this is a fantastic release, thank you!

- EricAnderton at yahoo

Walter Bright wrote:
> I don't know. Can you cut it down to size and file a bug report?

It's done. From ~4000 to <30 lines of code. In bugs NG.