On Wednesday, 25 June 2014 at 17:32:06 UTC, Gary Willoughby wrote:
On Wednesday, 25 June 2014 at 15:16:03 UTC, FrankLike wrote:
How about the DGui's status?
https://bitbucket.org/dgui/dgui/issues
#1to#5,those were built by me.
On Thursday, 26 June 2014 at 15:24:17 UTC, FrankLike wrote:
On Wednesday, 25 June 2014 at 17:32:06 UTC, Gary Willoughby
wrote:
On Wednesday, 25 June 2014 at 15:16:03 UTC, FrankLike wrote:
How about the DGui's status?
https://bitbucket.org/dgui/dgui/issues
#1to#5,those were built by me.
On Tuesday, 20 May 2014 at 07:20:16 UTC, Denis Shelomovskij wrote:
DGui is a lightweight graphic library for Windows with API
close to .NET's Windows Forms.
The library is written by Trogu Antonio Davide, but he isn't
supporting it any longer so you can refer me as a current
project manager.
https://github.com/economicmodeling
Stuff that's been made available:
* D implementation of the DDoc macro processor
* Documentation generator that doesn't need the compiler
- No more requirement to use all the -I options to just get
docs.
- Template constraints don't vanish.
-
On 25/06/2014 5:16 PM, Walter Bright wrote:
I agree with Russel. I think we've had good success with the D With
Moons logo, and it's use is pervasive and recognizable as being D.
Perhaps just a subtle clean up then?
https://drive.google.com/file/d/0B3i8FWPuOpryTjFybHNYYVVtc1k/edit
A...
Walter Bright:
It's an interesting list, and an opportunity for D. I once said
that my job was to put Coverity out of business.
Even if D has wide success, I don't think D will delete all the C
and C++ code out of existence, so I don't think D will ever put
Coverity out of business :-)
Walter Bright:
It's an interesting list, and an opportunity for D. I once said
that my job was to put Coverity out of business. The more of
these issues D can automatically prevent with @safe, the better.
One kind of problem left is to avoid stack overflows. I have had
several such cases in
On Thursday, 26 June 2014 at 00:36:58 UTC, Walter Bright wrote:
http://samate.nist.gov/SRD/view.php?count=20first=0sort=asc
This is a list of security vulnerabilities in languages
including C/C++. 88,737 of them (!).
It's an interesting list, and an opportunity for D. I once said
that my
On 6/26/2014 2:19 AM, bearophile wrote:
One kind of problem left is to avoid stack overflows.
In general, stack overflow checking at compile time is the halting problem. It
needs a runtime check.
Stack overflows are not safety problems when a guard page is used past the end
of the stack.
Walter Bright:
In general, stack overflow checking at compile time is the
halting problem. It needs a runtime check.
There are several systems, including SPARK, that perform a
conservative and apparently acceptable stack overflow check at
compile time. If you don't agree with what I've
On 06/26/2014 11:35 AM, Walter Bright wrote:
On 6/26/2014 2:19 AM, bearophile wrote:
One kind of problem left is to avoid stack overflows.
In general, stack overflow checking at compile time is the halting
problem.
That is irrelevant to his point because he is not suggesting to solve
the
I /think/ this is a bug, but I'm not 100% sure. The following
compiles without any problems, as it should:
import std.typecons;
alias Handle(T) = RefCounted!(T, RefCountedAutoInitialize.no);
auto initialized(T)() if(is(T == RefCounted!S, S...))
{
T refCounted;
For people that are not following closely what's happening in
GitHub, there are some nice or very nice patches waiting to be
fixed and/or accepted, among the last ones:
This proposes a __traits(documentation, expr):
https://github.com/D-Programming-Language/dmd/pull/3531
On 2014-06-26 10:38:53 +, bearophile said:
For people that are not following closely what's happening in GitHub,
there are some nice or very nice patches waiting to be fixed and/or
accepted, among the last ones:
This proposes a __traits(documentation, expr):
I've increased the bounty on this bug. Fast CTFE is very important.
https://www.bountysource.com/issues/1325927-ctfe-copy-on-write-is-slow-and-causes-huge-memory-usage
-Shammah
Walter Bright:
I suggest that your issues with global variables can be
mitigated by adopting a distinct naming convention for your
globals. Frankly, I think a global variable named x is
execrable style - such short names should be reserved for
locals.
I don't use names like 'x' for the
But having something enforced by the compiler is better.
I meant, it could be better.
Bye,
bearophile
On Thursday, 26 June 2014 at 10:09:53 UTC, Rene Zwanenburg wrote:
I /think/ this is a bug, but I'm not 100% sure. The following
compiles without any problems, as it should:
import std.typecons;
alias Handle(T) = RefCounted!(T, RefCountedAutoInitialize.no);
auto initialized(T)() if(is(T ==
On Thursday, 26 June 2014 at 10:09:53 UTC, Rene Zwanenburg wrote:
I /think/ this is a bug, but I'm not 100% sure. The following
compiles without any problems, as it should:
import std.typecons;
alias Handle(T) = RefCounted!(T, RefCountedAutoInitialize.no);
auto initialized(T)() if(is(T ==
On Thursday, 26 June 2014 at 10:09:53 UTC, Rene Zwanenburg wrote:
I /think/ this is a bug, but I'm not 100% sure. The following
compiles without any problems, as it should:
import std.typecons;
alias Handle(T) = RefCounted!(T, RefCountedAutoInitialize.no);
auto initialized(T)() if(is(T ==
On Thursday, 26 June 2014 at 12:38:40 UTC, John Colvin wrote:
On Thursday, 26 June 2014 at 10:09:53 UTC, Rene Zwanenburg
wrote:
I /think/ this is a bug, but I'm not 100% sure. The following
compiles without any problems, as it should:
import std.typecons;
alias Handle(T) = RefCounted!(T,
On Thursday, 26 June 2014 at 10:38:54 UTC, bearophile wrote:
// pointer type
auto* p1 = new int(3); // int*
const* p2 = new int(3); // const(int)*
Won't some people, especially those coming from C++, mistake this
for being syntax to create a constant pointer to a mutable int?
On Thursday, 26 June 2014 at 10:52:22 UTC, Shammah Chancellor
wrote:
On 2014-06-26 10:38:53 +, bearophile said:
For people that are not following closely what's happening in
GitHub, there are some nice or very nice patches waiting to be
fixed and/or accepted, among the last ones:
...
On Thursday, 26 June 2014 at 13:25:00 UTC, Meta wrote:
Yes, this is a bug. This code should work. If it doesn't
compile with Git HEAD, you should file a bug report.
Apparently it does. I'm not set up to build DMD myself so I'm
always just using the latest release.
On Thursday, 26 June 2014 at 12:52:54 UTC, hane wrote:
DMD 2.066(git head) compiled both without error.
Thanks for checking!
Meta:
const* p2 = new int(3); // const(int)*
Won't some people, especially those coming from C++, mistake
this for being syntax to create a constant pointer to a mutable
int?
C/C++ const is very different from D one (transitive), so C++
programmers must learn the differences.
If a C++
On Thu, Jun 26, 2014 at 10:38:53AM +, bearophile via Digitalmars-d wrote:
[...]
This proposes a __traits(documentation, expr):
https://github.com/D-Programming-Language/dmd/pull/3531
Something similar is used in Python and Lisp, it allows to introspect
the
H. S. Teoh:
What's wrong with just writing auto?
auto sqr = a = a^^2;
auto r = [1,2,3].map!sqr;
auto is used to use the type of the value on the right. But a =
a^^2 is not a value, it can't be assigned to a variable, because
it's not a lambda.
To use auto you need to give
On Thu, Jun 26, 2014 at 02:45:05PM +, bearophile via Digitalmars-d wrote:
H. S. Teoh:
What's wrong with just writing auto?
auto sqr = a = a^^2;
auto r = [1,2,3].map!sqr;
auto is used to use the type of the value on the right. But a =
a^^2 is not a value, it can't be
On Thursday, 26 June 2014 at 08:15:35 UTC, Alix Pexton wrote:
On 25/06/2014 5:16 PM, Walter Bright wrote:
I agree with Russel. I think we've had good success with the D
With
Moons logo, and it's use is pervasive and recognizable as
being D.
Perhaps just a subtle clean up then?
On Thursday, 26 June 2014 at 10:38:54 UTC, bearophile wrote:
https://github.com/D-Programming-Language/dmd/pull/3638
Allows to write code like:
void main() {
import std.algorithm;
alias sqr = a = a ^^ 2;
auto r = [1, 2, 3].map!sqr;
}
So if this pull request gets merged, should
On Thursday, 26 June 2014 at 16:05:24 UTC, bearophile wrote:
Meta:
So if this pull request gets merged, should we deprecate
std.functional.unaryFun and binaryFun? I don't see much need
for them with this pull merged.
perhaps unaryFun is to convert the strings like q{a * a}.
Bye,
bearophile
Meta:
So if this pull request gets merged, should we deprecate
std.functional.unaryFun and binaryFun? I don't see much need
for them with this pull merged.
perhaps unaryFun is to convert the strings like q{a * a}.
Bye,
bearophile
Meta:
There has been discussion before about doing away with string
lambdas. Maybe this is a good time to do that.
If they get deprecated I will have to manually fix a _ton_ of
code :-)
Bye,
bearophile
On 6/26/2014 7:02 AM, Shammah Chancellor wrote:
I've increased the bounty on this bug. Fast CTFE is very important.
https://www.bountysource.com/issues/1325927-ctfe-copy-on-write-is-slow-and-causes-huge-memory-usage
This is great news, and I'm sure very much appreciated by all.
I can't
On Thursday, 26 June 2014 at 17:26:02 UTC, bearophile wrote:
Meta:
There has been discussion before about doing away with string
lambdas. Maybe this is a good time to do that.
If they get deprecated I will have to manually fix a _ton_ of
code :-)
Bye,
bearophile
I guess instead of
I am actually in favour of adding more @ symbols. I think it
makes it clear which things are attributes, and it makes user
defined attributes look like the built in ones. So the built in
ones look less special.
On Thu, Jun 26, 2014 at 05:45:23PM +, Meta via Digitalmars-d wrote:
On Thursday, 26 June 2014 at 17:26:02 UTC, bearophile wrote:
Meta:
There has been discussion before about doing away with string
lambdas. Maybe this is a good time to do that.
If they get deprecated I will have to
On Thursday, 26 June 2014 at 10:38:54 UTC, bearophile wrote:
For people that are not following closely what's happening in
GitHub, there are some nice or very nice patches waiting to be
fixed and/or accepted
I'm pretty biased, but am quite excited about:
On Thursday, 26 June 2014 at 18:55:38 UTC, H. S. Teoh via
Digitalmars-d wrote:
Care to submit a PR to remove mentions of string lambdas from
the Phobos
docs? They're still all over the place.
I feel like this is a bad idea, we shouldn't be deleting
documentation. It will just end up causing
On Thursday, 26 June 2014 at 19:30:38 UTC, Tofu Ninja wrote:
On Thursday, 26 June 2014 at 18:55:38 UTC, H. S. Teoh via
Digitalmars-d wrote:
Care to submit a PR to remove mentions of string lambdas from
the Phobos
docs? They're still all over the place.
I feel like this is a bad idea, we
On Sunday, 15 June 2014 at 15:37:51 UTC, Caligo via Digitalmars-d
wrote:
I can't take a blog post seriously when it's poorly written and
full of
grammatical errors. If you are in an engineering field of any
kind, and
you can't construct a paragraph in your favorite natural
language, you're
Sean Kelly:
I'm pretty biased, but am quite excited about:
Mine was only a partial list :-)
void main() {
auto r = new Generator!string({
yield(the);
yield(quick);
yield(brown);
yield(fox);
});
Do you need the new there? Is that a
On Thursday, 26 June 2014 at 19:42:46 UTC, bearophile wrote:
Sean Kelly:
I'm pretty biased, but am quite excited about:
Mine was only a partial list :-)
void main() {
auto r = new Generator!string({
yield(the);
yield(quick);
yield(brown);
yield(fox);
On Thursday, 26 June 2014 at 08:15:35 UTC, Alix Pexton wrote:
On 25/06/2014 5:16 PM, Walter Bright wrote:
I agree with Russel. I think we've had good success with the D
With
Moons logo, and it's use is pervasive and recognizable as
being D.
Perhaps just a subtle clean up then?
On 6/26/2014 5:38 AM, bearophile wrote:
For people that are not following closely what's happening in GitHub,
there are some nice or very nice patches waiting to be fixed and/or
accepted, among the last ones:
While we're on the subject, I've been meaning to make a post about it,
but just
On Thu, 26 Jun 2014 16:21:24 -0400, Orvid King blah38...@gmail.com wrote:
On 6/26/2014 5:38 AM, bearophile wrote:
For people that are not following closely what's happening in GitHub,
there are some nice or very nice patches waiting to be fixed and/or
accepted, among the last ones:
While
On 6/26/2014 2:50 AM, bearophile wrote:
Walter Bright:
In general, stack overflow checking at compile time is the halting problem. It
needs a runtime check.
There are several systems, including SPARK, that perform a conservative and
apparently acceptable stack overflow check at compile time.
On 6/26/2014 2:52 AM, Timon Gehr wrote:
On 06/26/2014 11:35 AM, Walter Bright wrote:
On 6/26/2014 2:19 AM, bearophile wrote:
One kind of problem left is to avoid stack overflows.
In general, stack overflow checking at compile time is the halting
problem.
That is irrelevant to his point
Very often I use associative array as the simple syntactic way of
representing of pairs of some values. But AAs are slightly
complicated for this task and they don't preserve order inside
it. I could use some struct for example
struct P(T, N)
{
T first;
N second;
}
and write something
On Thu, Jun 26, 2014 at 08:15:46PM +, Wyatt via Digitalmars-d wrote:
On Thursday, 26 June 2014 at 08:15:35 UTC, Alix Pexton wrote:
On 25/06/2014 5:16 PM, Walter Bright wrote:
I agree with Russel. I think we've had good success with the D With
Moons logo, and it's use is pervasive and
On Thursday, 26 June 2014 at 20:36:01 UTC, Meta wrote:
On Thursday, 26 June 2014 at 18:55:38 UTC, H. S. Teoh via
Digitalmars-d wrote:
Care to submit a PR to remove mentions of string lambdas from
the Phobos
docs? They're still all over the place.
Sure, as soon as it gets merged.
I mean the
On Thursday, 26 June 2014 at 18:55:38 UTC, H. S. Teoh via
Digitalmars-d wrote:
Care to submit a PR to remove mentions of string lambdas from
the Phobos
docs? They're still all over the place.
Sure, as soon as it gets merged.
On Thu, Jun 26, 2014 at 04:27:16PM -0400, Steven Schveighoffer via
Digitalmars-d wrote:
On Thu, 26 Jun 2014 16:21:24 -0400, Orvid King blah38...@gmail.com wrote:
On 6/26/2014 5:38 AM, bearophile wrote:
For people that are not following closely what's happening in
GitHub, there are some nice
Uranuz:
I'd like to see any comments
Built-in tuple literals: good. Just pair literals: no, thanks.
Bye,
bearophile
Spark is a research language that does not work, as I've
discovered and discussed with you before. It cannot be
determined the max stack usage at compile time, again, this is
the halting problem.
What?! It's easily solvable: Forbid recursion and indirect
function calls and it's guaranteed
Thanks for response. I was thinking that adding new statement for
such feature is not very good too. Is there any recent
discussions about tuble literals. There is proposal in wiki but I
don't know if it will be accepted or not for some time. For now
seems like it's better to alias tuple and
Sent: Thursday, June 26, 2014 at 10:52 AM
From: Nick Sabalausky via Digitalmars-d digitalmars-d@puremagic.com
To: digitalmars-d@puremagic.com
Subject: Re: Bounty Increase on Issue #1325927
On 6/26/2014 7:02 AM, Shammah Chancellor wrote:
I've increased the bounty on this bug. Fast CTFE
On Thu, Jun 26, 2014 at 09:08:24PM +, Uranuz via Digitalmars-d wrote:
Thanks for response. I was thinking that adding new statement for such
feature is not very good too. Is there any recent discussions about
tuble literals. There is proposal in wiki but I don't know if it will
be accepted
On Thursday, 26 June 2014 at 17:52:13 UTC, Nick Sabalausky wrote:
On 6/26/2014 7:02 AM, Shammah Chancellor wrote:
I've increased the bounty on this bug. Fast CTFE is very
important.
https://www.bountysource.com/issues/1325927-ctfe-copy-on-write-is-slow-and-causes-huge-memory-usage
This
On Thursday, 26 June 2014 at 18:55:38 UTC, H. S. Teoh via
Digitalmars-d wrote:
On Thu, Jun 26, 2014 at 05:45:23PM +, Meta via
Digitalmars-d wrote:
On Thursday, 26 June 2014 at 17:26:02 UTC, bearophile wrote:
Meta:
There has been discussion before about doing away with string
lambdas.
On 6/26/2014 1:15 AM, Alix Pexton wrote:
On 25/06/2014 5:16 PM, Walter Bright wrote:
I agree with Russel. I think we've had good success with the D With
Moons logo, and it's use is pervasive and recognizable as being D.
Perhaps just a subtle clean up then?
Recently, very nice syntactic sugar was added for eponymous templates
that expand to enums or aliases:
// Original verbose form
template myEnum(T) {
enum myEnum = T.someStaticValue;
}
// New concise form:
enum myEnum(T) = T.someStaticValue;
On 6/26/2014 2:01 PM, Araq wrote:
Spark is a research language that does not work, as I've discovered and
discussed with you before. It cannot be determined the max stack usage at
compile time, again, this is the halting problem.
What?! It's easily solvable: Forbid recursion and indirect
On Thursday, 19 June 2014 at 05:35:06 UTC, Nick Sabalausky wrote:
That's why I inadvertently learned to love printf debugging. I
get to see the whole chart at one.
Yep. A lot of this is probably because as a server programmer
I've just gotten used to finding bugs this way as a matter of
On 06/26/2014 10:29 PM, Walter Bright wrote:
On 6/26/2014 2:52 AM, Timon Gehr wrote:
On 06/26/2014 11:35 AM, Walter Bright wrote:
On 6/26/2014 2:19 AM, bearophile wrote:
One kind of problem left is to avoid stack overflows.
In general, stack overflow checking at compile time is the halting
On Thu, Jun 26, 2014 at 10:57:28PM +, Sean Kelly via Digitalmars-d wrote:
On Thursday, 19 June 2014 at 05:35:06 UTC, Nick Sabalausky wrote:
That's why I inadvertently learned to love printf debugging. I get to
see the whole chart at one.
Yep. A lot of this is probably because as a
On 6/26/14, 2:01 PM, Araq wrote:
Spark is a research language that does not work, as I've discovered
and discussed with you before. It cannot be determined the max stack
usage at compile time, again, this is the halting problem.
What?! It's easily solvable: Forbid recursion and indirect
On 6/26/14, 4:16 PM, Timon Gehr wrote:
- Annotations can include a formal proof.
If a function can be annotated with what other functions it calls
(non-transitively), I agree that it can be guaranteed with local
semantic checking that a program won't overflow. However requiring such
On Thu, Jun 26, 2014 at 04:43:33PM -0700, Andrei Alexandrescu via Digitalmars-d
wrote:
On 6/26/14, 2:01 PM, Araq wrote:
Spark is a research language that does not work, as I've discovered
and discussed with you before. It cannot be determined the max stack
usage at compile time, again, this
On 06/27/2014 01:47 AM, Andrei Alexandrescu wrote:
On 6/26/14, 4:16 PM, Timon Gehr wrote:
...
You can say out of scope or not a priority or this should be
realized in third-party tool support but not it is impossible.
I also seem to reckon Walter is in the other extreme (he asserts it
can't
On Thu, Jun 26, 2014 at 04:47:24PM -0700, Andrei Alexandrescu via Digitalmars-d
wrote:
On 6/26/14, 4:16 PM, Timon Gehr wrote:
- Annotations can include a formal proof.
If a function can be annotated with what other functions it calls
(non-transitively), I agree that it can be guaranteed
On 6/26/2014 4:16 PM, Timon Gehr wrote:
On 06/26/2014 10:29 PM, Walter Bright wrote:
When you're dealing with security issues, which is what this about,
This is about _avoiding stack overflows_. It's written down literally in the
quoted passage.
Check the title of this thread, the linked
On 6/26/2014 7:24 PM, H. S. Teoh via Digitalmars-d wrote:
On Thu, Jun 26, 2014 at 10:57:28PM +, Sean Kelly via Digitalmars-d wrote:
On Thursday, 19 June 2014 at 05:35:06 UTC, Nick Sabalausky wrote:
That's why I inadvertently learned to love printf debugging. I get to
see the whole chart
Hi all,
right now, the use of std.math over core.stdc.math can cause a
huge performance problem in typical floating point graphics code.
An instance of this has recently been discussed here in the
Perlin noise benchmark speed thread [1], where even LDC, which
already beat DMD by a factor of
On Friday, 27 June 2014 at 01:31:17 UTC, David Nadlinger wrote:
Hi all,
right now, the use of std.math over core.stdc.math can cause a
huge performance problem in typical floating point graphics
code. An instance of this has recently been discussed here in
the Perlin noise benchmark speed
On Thu, Jun 26, 2014 at 09:16:27PM -0400, Nick Sabalausky via Digitalmars-d
wrote:
[...]
Aye. Sometimes in embedded work, you're *lucky* if you can even do
printf at all, let alone a debugger. I've had to debug with as little
as one LED. It's...umm...interesting. And time consuming.
On Fri, Jun 27, 2014 at 02:09:59AM +, Tofu Ninja via Digitalmars-d wrote:
On Friday, 27 June 2014 at 01:31:17 UTC, David Nadlinger wrote:
[...]
Because of this, I propose to add float and double overloads (at the
very least the double ones) for all of the commonly used functions in
On Monday, 23 June 2014 at 20:23:52 UTC, Brian Schott wrote:
On Monday, 23 June 2014 at 20:08:41 UTC, Gary Willoughby wrote:
All are having the @ added: http://wiki.dlang.org/DIP64
This hasn't been decided on. It's just a proposal right now.
While I agree with the original statement that
H. S. Teoh via Digitalmars-d digitalmars-d@puremagic.com writes:
On Fri, Jun 27, 2014 at 02:09:59AM +, Tofu Ninja via Digitalmars-d wrote:
On Friday, 27 June 2014 at 01:31:17 UTC, David Nadlinger wrote:
[...]
Because of this, I propose to add float and double overloads (at the
very least
On 6/26/14, 5:29 PM, Timon Gehr wrote:
On 06/27/2014 01:47 AM, Andrei Alexandrescu wrote:
On 6/26/14, 4:16 PM, Timon Gehr wrote:
...
You can say out of scope or not a priority or this should be
realized in third-party tool support but not it is impossible.
I also seem to reckon Walter is in
On 23/06/14 04:51, Nordlöw wrote:
That will only work now if you use an else.
So you mean something like
if(xbyte.min || xbyte.max)
throw new InvalidArgumentException(...
else {}
?
That seems like a strange restriction. Why is that?
I meant, else return x;
Because
On Thursday, 26 June 2014 at 09:19:05 UTC, bearophile wrote:
Walter Bright:
It's an interesting list, and an opportunity for D. I once
said that my job was to put Coverity out of business. The more
of these issues D can automatically prevent with @safe, the
better.
One kind of problem left
On Thu, 2014-06-26 at 23:28 -0400, Jerry via Digitalmars-d wrote:
H. S. Teoh via Digitalmars-d digitalmars-d@puremagic.com writes:
On Fri, Jun 27, 2014 at 02:09:59AM +, Tofu Ninja via Digitalmars-d
wrote:
On Friday, 27 June 2014 at 01:31:17 UTC, David Nadlinger wrote:
[...]
On Thursday, 26 June 2014 at 21:17:45 UTC, H. S. Teoh via
Digitalmars-d wrote:
On Thu, Jun 26, 2014 at 09:08:24PM +, Uranuz via
Digitalmars-d wrote:
Thanks for response. I was thinking that adding new statement
for such
feature is not very good too. Is there any recent discussions
about
On Fri, Jun 27, 2014 at 05:35:40AM +, deadalnix via Digitalmars-d wrote:
On Thursday, 26 June 2014 at 21:17:45 UTC, H. S. Teoh via Digitalmars-d
wrote:
On Thu, Jun 26, 2014 at 09:08:24PM +, Uranuz via Digitalmars-d wrote:
Thanks for response. I was thinking that adding new statement
Here are some of the items I voted on that I see have been
resolved:
https://issues.dlang.org/show_bug.cgi?id=1528
overloading template and non-template functions
https://issues.dlang.org/show_bug.cgi?id=5700
Allow dup in nothrow functions
https://issues.dlang.org/show_bug.cgi?id=5893
Allow
Are there any precompiled binaries for windows?
But if I write
@(hello) struct Hello {}
so all of the variables that have type Hello will have attribute
@(hello) like come type qualifier because attribute is a part
of declaration of Hello. Do I understand correctly?
Hi,
I'm using scriptlike, which imports everything from std.process
for convienience, but I also need to import another module, which
contains a class `Config`, it conflicts with std.process.Config.
I don't actually need std.process.Config, but I need many other
symbols in scriptlike and
Puming:
I'm using scriptlike, which imports everything from std.process
for convienience, but I also need to import another module,
which contains a class `Config`, it conflicts with
std.process.Config. I don't actually need std.process.Config,
but I need many other symbols in scriptlike and
On Thursday, 26 June 2014 at 08:36:15 UTC, Chris wrote:
On Wednesday, 25 June 2014 at 09:29:35 UTC, Orfeo wrote:
I wanted to create a simple application to display and edit
data from postgresql database using GtkD and ddb
(https://github.com/pszturmaj/ddb)
The application should run on
On Wednesday, 25 June 2014 at 09:29:35 UTC, Orfeo wrote:
I wanted to create a simple application to display and edit
data from postgresql database using GtkD and ddb
(https://github.com/pszturmaj/ddb)
The application should run on WinXp or Win7. After a week of
work I throw in the towel ...
On Thursday, 26 June 2014 at 08:39:46 UTC, Chris wrote:
On Thursday, 26 June 2014 at 08:36:15 UTC, Chris wrote:
On Wednesday, 25 June 2014 at 09:29:35 UTC, Orfeo wrote:
I wanted to create a simple application to display and edit
data from postgresql database using GtkD and ddb
On Thursday, 26 June 2014 at 02:33:43 UTC, Mathias LANG wrote:
On Wednesday, 25 June 2014 at 18:49:27 UTC, Stefan Frijters
wrote:
Let me preface this by admitting that I'm not sure I'm using
the DDoc functionality properly at all, so let me know if my
questions are bogus.
Is it possible to:
Stefan Frijters:
I found a pull request to add __traits(documentation, ...)[1]
which would also allow me to solve my problem as a workaround,
does anyone know if this is still moving forward?
You can state in that GitHub thread that you could use that
feature. There are many stalled nice
How can i close my application by code?
+ 1 for own GUI + graphics module for D
On Wednesday, 25 June 2014 at 14:17:50 UTC, Meta wrote:
If you want something like a hash table that preserves
insertion order, you could try using an array of tuples
instead. Then to pop the first element, just do 'arr =
arr[1..$]'.
Thank you, this is _exactly_ what I was looking for!
On Wednesday, 25 June 2014 at 14:17:50 UTC, Meta wrote:
Then to pop the first element, just do 'arr = arr[1..$]'.
Or import std.array to get the range primitives for slices:
import std.array;
void main()
{
auto arr = [1, 2, 3, 4];
arr.popFront();
assert(arr.front == 2);
}
1 - 100 of 165 matches
Mail list logo
