is, however, that may not be a severe issue.
-- Chris NS
recall there being a
response.
-- Chris NS
);
}
##
With output:
false, 600
Gosh, that'd sure be swell. (Either that or find a way to sanely
allow non-static struct initializers, at least for rvalue
arguments.)
-- Chris NS
On Tuesday, 24 July 2012 at 23:03:39 UTC, Adam D. Ruppe wrote:
On Tuesday, 24 July 2012 at 07:03:05 UTC, Chris NS wrote:
I can't help thinking it sounds rather like a job for... named
parameters. Just imagine it:
Yeah, that could do it too, but named parameters have been
brought up a few
On Tuesday, 24 July 2012 at 22:38:07 UTC, Era Scarecrow wrote:
[code]
//remember, java
String toGuid(byte input[16]) {
String ID = {;
if (Integer.toHexString(input[5]).length 2)
ID = ID + 0;
ID = ID + Integer.toHexString(input[5]);
if (Integer.toHexString(input[6]).length 2)
);
}
##
-- Chris NS
, then I'm
honestly not sure what the main obstacle to this is.
-- Chris NS
Not sure yet what your exactly issue is, but have you tried to
reproduce it using register/lookup?
It certainly makes sense. Maybe the long term solution would be
a way to embed those assertions in the conditions, but in the
meantime the proposal would alleviate the error message issue. I
know I've often enough stared long and hard at a volume of
template instantiation errors waiting for
:
foreach ( decl ; __traits( allMembers, data ) ) {
if ( is( typeof( mixin( decl ) ) == class )
!__traits( isAbstractclass, mixin( decl ) ) ) {
// ...some code in here...
}
}
-- Chris NS
On Tuesday, 17 July 2012 at 18:12:28 UTC, Iain Buclaw wrote:
On 17 July 2012 12:05, Wouter Verhelst wou...@grep.be wrote:
Chris NS ibisbase...@gmail.com writes:
+1 for a 2.breaking.bugfix scheme. I've used this scheme on
anything serious for years, and know many others who have; so
On Tuesday, 17 July 2012 at 06:29:46 UTC, Jacob Carlborg wrote:
On 2012-07-16 23:36, SomeDude wrote:
It's *not* textual search and replace. It's compiler checked
semantic
refactoring.
Yet again we need a compiler as a library :)
I find myself agreeing more and more.
... but I'm not so sure
it is such a good idea anymore -- assuming this-params will work
on the class declaration.
-- Chris NS
+1 for a 2.breaking.bugfix scheme. I've used this scheme on
anything serious for years, and know many others who have; so it
is not only popular but also quite tried and proven. Not for
every project, of course (although I don't understand why the
Linux kernel team dropped it with 3.x), but
/discussion of @property and -property
to be... well, moot. But hey, I'm just one crazy among an army
of crazies.
-- Chris NS
On Monday, 16 July 2012 at 23:13:54 UTC, Timon Gehr wrote:
On 07/16/2012 10:55 AM, Chris NS wrote:
Having been around long enough to remember when the ability to
call
foo() as foo first appeared, I feel it necessary to point
out that
this was *not* in fact a deliberate design, but rather
I say: finally. I've long felt that Object was already too
heavy, but hadn't worried about it much in years (since there was
no apparent solution at that time). Just as
notifyRegister/notifyUnRegister were eventually moved out to the
runtime, it should be possible to do the same for these,
On Thursday, 12 July 2012 at 00:37:22 UTC, H. S. Teoh wrote:
On Thu, Jul 12, 2012 at 02:14:30AM +0200, Minas Mina wrote:
[...]
** wall o' text **
You forgot about their quantum uncertainty loving transvestite
cousin: inout.
I second the request for a PNG encoder. You just saved me a lot
of trouble, as I was about to implement my own PNG loader... and
now I don't have to. ^_^ I'll glance over your code in full
sometime and see if I notice any readily apparent improvements.
On Sunday, 17 June 2012 at 20:10:28 UTC, cal wrote:
though I have worlds of trouble with const-ness, I will
endeavour to add those guarantees :)
What I usually do, unless it's just an obvious case, is write
code without concern for const-ness, then write a thorough test
and step through one
I've been playing around with vibe in my free time the last few
days, and here are the beginnings of a stab at REST:
https://github.com/csauls/zeal.d/blob/master/source/zeal/http/router.d
Admittedly it rips off the Rails way of recognizing and pathing
the REST actions, but I admit a small bias
On Saturday, 31 March 2012 at 06:39:07 UTC, Nick Sabalausky wrote:
Chris NS ibisbase...@gmail.com wrote in message
news:ugopmohijjcnnrchu...@forum.dlang.org...
I'm pretty impressed with the idea, and look forward to its
implementation, but I do have one question. How does this
affect
have access to
each other's private members?
I'm not sure whether I favor them losing or keeping their
friend status.
--
Chris NS
On Friday, 30 March 2012 at 22:28:40 UTC, H. S. Teoh wrote:
On Fri, Mar 30, 2012 at 11:17:47PM +0100, Stewart Gordon wrote:
On 26/03/2012 02:18, dnewbie wrote:
Just out of curiosity, is D attracting new users? Are the old
users running? Place your vote here
24 matches
Mail list logo
