February 10, 2006
You fixed the template 'private' bug?  Hallelujah!


Sean
February 10, 2006
In article <dsii3b$1dtc$1@digitaldaemon.com>, Sean Kelly says...
>
>You fixed the template 'private' bug?  Hallelujah!
>
>
>Sean

I agree - great work Walter!!


February 10, 2006
"Jarrett Billingsley" <kb3ctd2@yahoo.com> wrote in message news:dsib37$16ed$1@digitaldaemon.com...
> "Walter Bright" <newshound@digitalmars.com> wrote in message news:dshdns$a6s$1@digitaldaemon.com...
>> Added features to make D useable as a scripting language on unix.
>>
>> http://www.digitalmars.com/d/changelog.html
>
> Oh happiness :)  Only problem is, I'll have to recompile phobos as, as far as I know, shinchiro hasn't made a new version of the backtrace phobos yet.. _damn_, have I become dependent on that sweet, sweet backtrace!  Not just for AVs, but for all kinds of exceptions..

I plan on integrating shinchiro's stuff. It's just too cool.


February 10, 2006
"Nick" <Nick_member@pathlink.com> wrote in message news:dshm2d$igt$1@digitaldaemon.com...
> Thanks for a(nother) great update! However, scripting (#! at the first
> line)
> doesn't seem to work correctly. I assume I am supposed to supply the -run
> parameter, but consider a file that contains
>
> #!/usr/bin/dmd -run
>
> The actual command exectued is "/usr/bin/dmd -run filename.d", where
> filename.d
> is parsed as an argument to -run.

Oh darn.


February 10, 2006
"Derek Parnell" <derek@psych.ward> wrote in message news:1w3d76hg5iw1n$.1420iwc0ce5dn.dlg@40tude.net...
> Nice one ... and I see that at least one Build featurette has now migrated
> to D (-run) <g>

I've started using it myself and darn if it isn't handy. I should have done it long ago.


February 10, 2006
Walter Bright wrote:
> I plan on integrating shinchiro's stuff. It's just too cool. 

Excellent ! Maybe people will complain less about null pointers ;)



-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/M d-pu s+: a-->----- C+++$>++++ UL P+ L+ E--- W++ N++ o? K? w++ !O !M V? PS- PE- Y PGP t 5 X? R tv-- b DI- D+ G e>+++ h>++ !r !y
------END GEEK CODE BLOCK------

Tomasz Stachowiak  /+ a.k.a. h3r3tic +/
February 10, 2006
"Jarrett Billingsley" <kb3ctd2@yahoo.com> wrote in message news:dsib37$16ed$1@digitaldaemon.com...
> Only problem is, I'll have to recompile phobos

And I've done just that.  All credits of course go to shinchiro, and also to James Dunne for hosting my crap :)

http://jamesdunne.no-ip.org/nonagon/phobos_backtrace_146.zip


February 10, 2006
In article <dsim0k$1hm3$1@digitaldaemon.com>, Walter Bright says...
>
>
>"Jarrett Billingsley" <kb3ctd2@yahoo.com> wrote in message news:dsib37$16ed$1@digitaldaemon.com...
>> "Walter Bright" <newshound@digitalmars.com> wrote in message news:dshdns$a6s$1@digitaldaemon.com...
>>> Added features to make D useable as a scripting language on unix.
>>>
>>> http://www.digitalmars.com/d/changelog.html
>>
>> Oh happiness :)  Only problem is, I'll have to recompile phobos as, as far as I know, shinchiro hasn't made a new version of the backtrace phobos yet.. _damn_, have I become dependent on that sweet, sweet backtrace!  Not just for AVs, but for all kinds of exceptions..
>
>I plan on integrating shinchiro's stuff. It's just too cool.

I took a look at it myself.  It looks like he has a custom Exception hook in there along with OMF and COFF debug data parsers to recover symbol and address information.  Definately a smooth hack.

But it does bring to mind one question: will this mean that stack traces in D will only be available in debug builds?

- Eric Anderton at yahoo
February 10, 2006
"pragma" <pragma_member@pathlink.com> wrote in message news:dsit7q$1rfc$1@digitaldaemon.com...
> But it does bring to mind one question: will this mean that stack traces
> in D
> will only be available in debug builds?

Yup.


February 10, 2006
"pragma" <pragma_member@pathlink.com> wrote in message
> But it does bring to mind one question: will this mean that stack traces
> in D
> will only be available in debug builds?

When else would you need one?  A stack dump is a debugging tool, no?  I doubt that a stack dump would be of much use to normal users (unless, of course, the normal users for your program are *nixheads, in which case they're _all_ developers and would understand what a stack dump is, but if your program runs in *nix, there's a 99.999% probably that it's open-source anyway, so they can build a debug build and get a stack dump if they want one ;)  whoo).