Re: When will we have std.log?

On Sat, Oct 6, 2012 at 11:47 PM, domain wrote: > It has been suspended for a long time. Any plan? > I have been working on it in my spare time. I have fixed some basic API issues that were outlined during the review process but not enough to put it through another review process. std.log was or

Re: RFC: DConf 2013

On Sat, Oct 6, 2012 at 4:20 PM, Era Scarecrow wrote: > On Wednesday, 3 October 2012 at 17:08:25 UTC, Andrei Alexandrescu wrote: > >> I hear you. We have a detailed budget model and we're not splurging in >> any way. Organizing a conference has quite a few odds and ends and weird >> pricing. As an

Re: It seems pure ain't so pure after all

On Mon, Oct 1, 2012 at 4:19 PM, Tommi wrote: > On Monday, 1 October 2012 at 22:23:51 UTC, Jonathan M Davis wrote: > >> Keywords are considered to be incredibly expensive. Being able to use a >> name >> starting with @ rather than a keyword does reduce the cost, but you're >> still >> going to hav

Re: Rust and D

On Fri, Sep 28, 2012 at 3:21 PM, Nick Sabalausky < seewebsitetocontac...@semitwist.com> wrote: > (My apologies if the article's author is reading this, no offense was > intended.) Doubt it. I believe the author was Rob Pike.

Re: Embedded non-assignable containers

On Sat, Sep 1, 2012 at 6:40 PM, bearophile wrote: > José Armando García Sancio: > > I recently read an interesting blog Why should I have written ZeroMQ in C, >> not C++ (part II) <http://www.250bpm.com/blog:8> by Martin Sústrik. The >> >> title is misleading; t

Re: Embedded non-assignable containers

On Sun, Sep 2, 2012 at 12:39 AM, Philippe Sigaud wrote: > > > To make a type "double linkable" the developer needs to mixin the > following mixin template: > > > >> mixin template DoubleLinkable() > >> { > >> typeof(this) next; > >> typeof(this) prev; > >> } > > > > > > The next and prev point

Embedded non-assignable containers

Hey, I recently read an interesting blog Why should I have written ZeroMQ in C, not C++ (part II) by Martin Sústrik. The title is misleading; to me its main observation is that object oriented program may not lead to the most performant implementation. After reading

Re: The review of std.hash package

On Wed, Aug 15, 2012 at 8:11 AM, ReneSac wrote: > > Note that in the Python passlib, there is no mention to CRC, FNV, ROT13, > etc. Their place is different. Thats because it is a "password module" and nobody or a small percentage of the population uses CRC for password digest. Note that the Pyth

Re: The review of std.hash package

On Wed, Aug 15, 2012 at 2:40 AM, RivenTheMage wrote: > Another example is a systematic error-correcting codes. The > "only" difference between them and checksums is the ability to > correct errors, not just detect them. CRC or MD5 can be viewed as > systematic code with zero error-correcting abili

Re: Why won't this compile using DMD?

On Sun, Aug 12, 2012 at 1:18 PM, Simen Kjaeraas wrote: > On Sun, 12 Aug 2012 19:57:16 +0200, José Armando García Sancio > wrote: > >> On Sun, Aug 12, 2012 at 7:31 AM, Simen Kjaeraas >> wrote: >>> >>> On Sun, 12 Aug 2012 09:39:13 +0200, Ivan Trombley &

Re: Why won't this compile using DMD?

On Sun, Aug 12, 2012 at 7:31 AM, Simen Kjaeraas wrote: > On Sun, 12 Aug 2012 09:39:13 +0200, Ivan Trombley >> auto data = new Data(count); > > > should be > > auto data = cast(shared)new Data(count); Or auto data = new shared(Data)(count);

Re: finish function for output ranges

On Sat, Aug 11, 2012 at 4:29 PM, Andrei Alexandrescu wrote: > For files, finish() should close the file (or at least flush it - unclear on > that). I also wonder whether there exists a better name than finish(), and > how to handle cases in which e.g. you finish() an output range and then you > pu

Re: Example of Rust code

On Fri, Aug 10, 2012 at 4:35 PM, Walter Bright wrote: > On 8/10/2012 4:19 PM, Walter Bright wrote: >> >> You can also use templates with overloading to get stack allocated >> parametric >> polymorphism and zero runtime overhead. > > > It appears that Rust does not have function overloading. Is thi

Re: @property

On Tue, Aug 7, 2012 at 1:52 PM, José Armando García Sancio wrote: > On Tue, Aug 7, 2012 at 12:27 PM, Timon Gehr wrote: >> On 08/07/2012 08:37 PM, José Armando García Sancio wrote: >>> >>> On Tue, Aug 7, 2012 at 10:39 AM, Timon Gehr wrote: >>>> >>&

Re: @property

On Tue, Aug 7, 2012 at 12:27 PM, Timon Gehr wrote: > On 08/07/2012 08:37 PM, José Armando García Sancio wrote: >> >> On Tue, Aug 7, 2012 at 10:39 AM, Timon Gehr wrote: >>> >>> On 08/07/2012 07:59 AM, José Armando García Sancio wrote: >>> >>>&

Re: @property

On Tue, Aug 7, 2012 at 10:39 AM, Timon Gehr wrote: > On 08/07/2012 07:59 AM, José Armando García Sancio wrote: >> >> On Sun, Aug 5, 2012 at 2:32 PM, Kapps wrote: >>> >>> On Sunday, 5 August 2012 at 14:32:50 UTC, Adam D. Ruppe wrote: >>>> >&

Re: @property

On Mon, Aug 6, 2012 at 11:31 PM, Brad Anderson wrote: > On Mon, Aug 6, 2012 at 11:59 PM, José Armando García Sancio > wrote: >> >> On Sun, Aug 5, 2012 at 2:32 PM, Kapps wrote: >> > On Sunday, 5 August 2012 at 14:32:50 UTC, Adam D. Ruppe wrote: >> >> >

Re: @property

On Sun, Aug 5, 2012 at 2:32 PM, Kapps wrote: > On Sunday, 5 August 2012 at 14:32:50 UTC, Adam D. Ruppe wrote: >> >> On Sunday, 5 August 2012 at 04:12:23 UTC, Jonathan M Davis wrote: >>> >>> I'd be very surprised if all that many people compile with -property. >> >> >> Indeed. Sometimes I try it ju

Re: std.d.lexer requirements

On Thu, Aug 2, 2012 at 1:26 PM, Jonathan M Davis wrote: > On Thursday, August 02, 2012 01:44:18 Walter Bright wrote: >> On 8/2/2012 1:38 AM, Jonathan M Davis wrote: >> > On Thursday, August 02, 2012 01:14:30 Walter Bright wrote: >> >> On 8/2/2012 12:43 AM, Jonathan M Davis wrote: >> >>> It is for

Re: @trusted considered harmful

On Fri, Jul 27, 2012 at 5:08 PM, David Nadlinger wrote: > 2) The first step is necessary, but mainly of cosmetic nature (think > `pure`, `pure2`). We still need to address for the granularity and attribute > inference problem. The obvious solution is to add a "@trusted" > declaration/block, which

Re: D support in Exuberant Ctags 5.8 for Windows

On Thu, Jul 26, 2012 at 4:59 PM, Brian Schott wrote: > On Thursday, 26 July 2012 at 23:51:34 UTC, José Armando García Sancio wrote: >> >> On Thu, Jul 26, 2012 at 3:34 PM, dnewbie wrote: >>> >>> There is --ctags output in Dscanner >>> https://git

Re: D support in Exuberant Ctags 5.8 for Windows

On Thu, Jul 26, 2012 at 3:34 PM, dnewbie wrote: > There is --ctags output in Dscanner > https://github.com/Hackerpilot/Dscanner Very interesting. Is this Dscanner pluggable? I would be interesting to use Dscanner for localization. For example it would be nice if it could generate a list of all th

Re: Take and website

On Tue, Jul 24, 2012 at 11:47 AM, Russel Winder wrote: > On Tue, 2012-07-24 at 14:21 -0400, Andrei Alexandrescu wrote: > […] > Is the website documentation generated from the Phobos source or is it a > separate repository? That particular example should be in the ddoc block for that function/tem

Re: Creator of ZeroMQ and AMQP comments on error handling

On Sun, Jul 15, 2012 at 3:00 PM, Tobias Pankrath wrote: >> What do you all think? > > > All his arguments about C++ exceptions hold for plain return values, too. > Yes but he would said that is not the point of his article. I think his point is that if you decide not to use exception in C++, for

Re: Creator of ZeroMQ and AMQP comments on error handling

On Sun, Jul 15, 2012 at 1:31 PM, José Armando García Sancio wrote: > Why should I have written ZeroMQ in C, not C++ - http://www.250bpm.com/blog:4 Reddit thread if you are interested: http://www.reddit.com/r/programming/comments/tggnn/why_should_i_have_written_zeromq_in_c_not_c/

Creator of ZeroMQ and AMQP comments on error handling

Hey everyone, Apologies for sending this to the D mailing list but I just read a very interesting article on error handling and was interested in your opinion. I just read an article by Martin Sústrik, one of the creators of AMQP and ZeroMQ, on using C++ for writing infrastructure/system software

Re: synchronized (this[.classinfo]) in druntime and phobos

On Wed, May 30, 2012 at 5:30 PM, Steven Schveighoffer wrote: > All deadlocks involving A and B mutexes.  Or if not, can you show how?  I > can't see it. > > -Steve This can cause a deadlock because locking order is not guaranteed, no? synchronized class A { void delegate(B b) { b.call() } vo