On 2012-12-14 01:17, David Nadlinger wrote:
1. How much work would it be for the guys at Remedy Games to convert
their codebase from [] to @()?
Basically none. Just do a global search-and-replace with regular
expression. Search for @\[(.+)\] replace with @($1). It won't cover 100%
percent bu
On 2012-12-14 01:19, Walter Bright wrote:
It was the D community that selected the @(attribute) syntax, and the
overall design was based on extensive public discussion threads here
about it.
And you still implemented the [attribute] syntax first.
--
/Jacob Carlborg
http://dpaste.dzfl.pl/64025e0a
contains updated code. When the offset of the struct is 0 it
contains an actual ptr to the class(the standard way) and hence
can be "orphaned". When the offset is not 0 then it is part of a
class object and can use a calculation to get the parent.
Both methods
On 2012-12-13 23:49, H. S. Teoh wrote:
The compilation steps work fine, but when it should be running ar to
create the library archive, it runs a non-existent 'lib' instead, which
fails.
Isn't "lib" what Windows uses? You know that you can also use the "-lib"
flag directly with dmd.
--
/Jac
Hi,
I can't look at this today as I am at Groovy and Grails eXchange 2012
and have to give a talk which needs some reworking in the light of
happenings yesterday. Ping me a couple of times over the weekend to
make sure I get this looked into by Monday morning.
Thanks.
On Thu, 2012-12-13 at 14:4
On Fri, 2012-12-14 at 05:19 +0100, Nick B wrote:
[…]
> Correction. The answer to this question is actually YES.
> Read the martinfowler article. See the link below.
[…]
Whilst the Martin Fowler article is a good one, it is an analysts
perspective on it given some study. Can I suggest that people i
On 2012-12-13 22:26, Walter Bright wrote:
CTFE would catch it.
Didn't you just say that flow analysis is needed for that?
--
/Jacob Carlborg
On Friday, 14 December 2012 at 06:27:39 UTC, Rob T wrote:
I guess the complicating factor is that a nested struct could
not be copied out of one class into another of a different
type, so I can see why it's not implemented. The compiler would
have to prevent copies out, or the language would ha
I guess the complicating factor is that a nested struct could not
be copied out of one class into another of a different type, so I
can see why it's not implemented. The compiler would have to
prevent copies out, or the language would have to be modified to
allow nesting but with some new conve
On Thu, Dec 13, 2012 at 05:44:23PM -0800, Walter Bright wrote:
> On 12/13/2012 6:30 AM, Simen Kjaeraas wrote:
> >Walter does not seem to agree (see his post in this discussion).
>
> Note that the following implementation of halffloat does work,
> allowing explicit cast to halffloat and implicit co
On Monday, 10 December 2012 at 23:04:56 UTC, Nick B wrote:
On Monday, 10 December 2012 at 20:08:32 UTC, Andrei
Alexandrescu wrote:
On 12/9/12 10:58 PM, Nick B wrote:
[about the Disruptor framework]
Would Andrei like to comment on any of the comments so far ??
Sorry, I'd need to acquire expert
This is maybe of interest of the persons working (or willing to
work) on custom allocators for Phobos:
"Reconsidering Custom Memory Allocation" (2002) by Emery D.
Berger, Benjamin G. Zorn, Kathryn S.McKinley:
http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.7.6505
They show the "reap"
On Fri, Dec 14, 2012 at 03:33:31AM +0100, Chris Williams wrote:
[...]
> I also notice that the compiler is unable to detect struct
> initializers when I try to init my DList.
>
> E.g.:
>
> struct SomeData {
> string a;
> string b;
> }
> alias DList!(SomeData) SomeList;
>
> SomeList queue
On Fri, Dec 14, 2012 at 04:39:49AM +0100, Jonathan M Davis wrote:
[...]
> And if Remedy really needs special stuff which isn't necessarily ready
> for primetime, maybe he should create a branch specifically for them
> rather than doing it all in master.
[...]
Again, this highlights the need for a
On Friday, 14 December 2012 at 01:37:22 UTC, Walter Bright wrote:
On 12/13/2012 4:55 PM, deadalnix wrote:
You'll go nowhere without a community.
And we need major users, too.
Indeed ! That why I'm all for supporting such user, and I'm
pretty most people that are unhappy with the situation
On Thursday, December 13, 2012 22:19:18 Andrei Alexandrescu wrote:
> On 12/13/12 8:55 PM, kenji hara wrote:
> > I think we should have -future/-f switch and @future attribute.
> > It is a rough idea, but seems a required compiler feature.
> >
> > Kenji Hara
>
> That sounds interesting.
I believe
On Thursday, 13 December 2012 at 23:41:32 UTC, RenatoUtsch wrote:
Please, lets not release something not thoroughly tested when
we are in the middle of the new development process discussion,
we are trying to avoid exactly this kind of thing.
The process must be defined before we can use it an
On 12/13/12 8:55 PM, kenji hara wrote:
I think we should have -future/-f switch and @future attribute.
It is a rough idea, but seems a required compiler feature.
Kenji Hara
That sounds interesting.
Regarding attributes, a simple solution is to release it but without
official documentation. W
Greetings,
I was attempting to use DList as a queue, for allowing data to be
processed among a group of threads.
The first problem, here, is of course that I can't synchronize on
a struct. This can be resolved easily enough by creating a second
object like:
Object lock = new Object();
Whi
On Tuesday, 4 January 2011 at 16:03:28 UTC, Adam D. Ruppe wrote:
Lutger Blijdestijn wrote:
The restriction with calling zero-args functions is
unfortunate,
could this be solved by turning it into a class and dynamically
checking whether the type is a function and then invoke it if
it is?
May
I think we should have -future/-f switch and @future attribute.
It is a rough idea, but seems a required compiler feature.
Kenji Hara
2012/12/14 Walter Bright
> On 12/13/2012 5:33 PM, kenji hara wrote:
>
>> Yet not released feature is not visible for almost D users.
>> What you are going to do
On 12/13/2012 6:30 AM, Simen Kjaeraas wrote:
Walter does not seem to agree (see his post in this discussion).
Note that the following implementation of halffloat does work, allowing explicit
cast to halffloat and implicit conversion from.
(The halffloat literals don't work at the moment becaus
On 12/13/2012 5:33 PM, kenji hara wrote:
Yet not released feature is not visible for almost D users.
What you are going to do in 2.061 is to add a warned feature suddenly.
But, it is certainly no problem for almost D users (unless users use old @[]
syntax, compiler never warn). I think what you
On 12/13/2012 4:55 PM, deadalnix wrote:
You'll go nowhere without a community.
And we need major users, too.
It's a balancing act. And I wish to point out, again, that the design was based
on extensive discussion threads right here in the ng, and the design was
modified based on feedback rig
Yet not released feature is not visible for almost D users.
What you are going to do in 2.061 is to add a warned feature suddenly.
But, it is certainly no problem for almost D users (unless users use old
@[] syntax, compiler never warn). I think what you must to do is to cut the
time limit of remo
On 12/13/2012 5:10 PM, H. S. Teoh wrote:
Remedy adopting D
Saying that would be premature and incorrect at the moment. We still have to
ensure that Remedy wins with D. This is an ongoing thing.
On Fri, Dec 14, 2012 at 01:05:21AM +0100, deadalnix wrote:
> On Thursday, 13 December 2012 at 23:47:56 UTC, Walter Bright wrote:
> >It's Remedy Games. It's a big deal for them, and their use of D is
> >a big deal for us, big enough that we can bend our procedure for
> >them. They were also under se
On Friday, December 14, 2012 01:17:08 David Nadlinger wrote:
> For 1., I would guess at most something like half an hour for a
> large codebase where the feature is used pervasively (you just
> keep editing/compiling until there are no more syntax errors),
> which is why I can't quite understand th
On Friday, 14 December 2012 at 00:42:58 UTC, Walter Bright wrote:
Like any major user of a language, they want confidence in our
full support of them. Asking them to use a patched or branch
version of the compiler does not inspire confidence.
But nobody agreed here on supporting that ! It ne
On Friday, 14 December 2012 at 00:42:58 UTC, Walter Bright wrote:
For 1., I would guess at most something like half an hour for
a large codebase
where the feature is used pervasively (you just keep
editing/compiling until
there are no more syntax errors), which is why I can't quite
understand t
On 12/13/2012 4:17 PM, David Nadlinger wrote:
1. How much work would it be for the guys at Remedy Games to convert their
codebase from [] to @()?
I don't know. All I know is it's a lot of code.
2. What is your plan moving forward, i.e. how to you intend to handle
deprecation/removal of the f
On 12/13/2012 4:05 PM, deadalnix wrote:
You have to understand that this isn't their need that is important here. They
need stuff that we mostly all need, so I tend to agree. The fact is that you
unilaterally decide to give that priority, when we are not even aware of them or
of their needs. And
On Thursday, 13 December 2012 at 23:47:56 UTC, Walter Bright
wrote:
I understand that some of you may be frustrated by my giving
their needs priority, […]
It's *not* your choice of priorities which strikes me as odd,
it's that the situations seems like you made an objectively bad
technical de
On Thursday, 13 December 2012 at 23:47:56 UTC, Walter Bright
wrote:
They began using UDAs the same day I implemented them.
I intend to start using them the day 2.061 comes out... the UDA
feature is going to be incredibly useful for me too, and the
implementation you've made is substantially i
On Fri, Dec 14, 2012 at 12:34:13AM +0100, deadalnix wrote:
> On Thursday, 13 December 2012 at 20:48:30 UTC, deadalnix wrote:
[...]
> Updated to follow the idea, plus added bunch of process description.
> Feel free to comment in order to refine this.
>
> http://wiki.dlang.org/Release_Process
I've
On Thursday, 13 December 2012 at 23:47:56 UTC, Walter Bright
wrote:
It's Remedy Games. It's a big deal for them, and their use of D
is a big deal for us, big enough that we can bend our procedure
for them. They were also under severe time pressure. They began
using UDAs the same day I implement
On Thursday, 13 December 2012 at 20:56:05 UTC, Mafi wrote:
On Wednesday, 12 December 2012 at 22:58:47 UTC, Max Samukha
wrote:
On Wednesday, 12 December 2012 at 22:19:54 UTC, js.mdnq wrote:
Also, I initially tried to do
B!(A.b1.offsetof) b1;
a'la
http://forum.dlang.org/thread/mailman.
On Thursday, 13 December 2012 at 23:47:56 UTC, Walter Bright
wrote:
On 12/13/2012 1:44 PM, deadalnix wrote:
You are engaging the whole community into something you
dropped here by surprise
and then claiming that some people uses. We don't even know
who they are ! How
can we support your point
On 12/13/12 6:02 PM, Denis Koroskin wrote:
On Thu, 13 Dec 2012 13:37:07 -0800, Walter Bright
wrote:
On 12/13/2012 12:46 PM, Jacob Carlborg wrote:
On 2012-12-13 18:27, Iain Buclaw wrote:
I am confused at this commit also.
Walter argues that people are already using it so it can't just be
r
On Thursday, 13 December 2012 at 23:32:44 UTC, Nick B wrote:
what does O-o-O mean ? >
Out-of-order.
David
On 12/13/2012 1:44 PM, deadalnix wrote:
You are engaging the whole community into something you dropped here by surprise
and then claiming that some people uses. We don't even know who they are ! How
can we support your point ?
It's Remedy Games. It's a big deal for them, and their use of D is
On Thursday, 13 December 2012 at 21:37:07 UTC, Walter Bright
wrote:
On 12/13/2012 12:46 PM, Jacob Carlborg wrote:
On 2012-12-13 18:27, Iain Buclaw wrote:
I am confused at this commit also.
Walter argues that people are already using it so it can't
just be removed. I
say, they're using an un
On Thursday, 13 December 2012 at 16:07:13 UTC, Dmitry Olshansky
wrote:
12/13/2012 4:59 AM, David Piepgrass пишет:
Maybe, but I'm still not clear what are the differences
between a
normal ring buffer (not a new concept) and this "disruptor"
pattern..
Key differences with a typical lock-free qu
On Thursday, 13 December 2012 at 20:48:30 UTC, deadalnix wrote:
On Thursday, 13 December 2012 at 20:04:50 UTC, Dmitry Olshansky
wrote:
I think it's good.
But personally I'd expect:
* master to be what you define as dev, because e.g. GitHub
puts master as default target branch when making pull
On Thu, 13 Dec 2012 13:37:07 -0800, Walter Bright
wrote:
On 12/13/2012 12:46 PM, Jacob Carlborg wrote:
On 2012-12-13 18:27, Iain Buclaw wrote:
I am confused at this commit also.
Walter argues that people are already using it so it can't just be
removed. I
say, they're using an unrelea
Hi Russel,
I've been using your BitBucket scons_d_tooling version of SCons for my D
projects, and it's been great! However, I needed to make a static
library today and I'm having some trouble with it. Here's a reduced
testcase:
env = Environment(
DC = '/usr/src/d/dmd/src/
On Thursday, 13 December 2012 at 21:28:52 UTC, SomeDude wrote:
On Thursday, 13 December 2012 at 01:51:27 UTC, Timon Gehr wrote:
And
if the standard library is twice as slow in implementation A
than in implemention B, then most programs will feel *at least*
twice as slow, and usually more, beca
On 13 December 2012 21:37, Walter Bright wrote:
> On 12/13/2012 12:46 PM, Jacob Carlborg wrote:
>>
>> On 2012-12-13 18:27, Iain Buclaw wrote:
>>
>>> I am confused at this commit also.
>>
>>
>> Walter argues that people are already using it so it can't just be
>> removed. I
>> say, they're using an
Walter Bright:
For errors, what I try to do is look at the kinds of patterns
of error that are commonplace, and try to devise ways to head
them off.
This was a bug commonly found, I think you accepted it, but it's
not fixed yet. I hope it's not forgotten, it's a little breaking
change:
ht
On Thu, Dec 13, 2012 at 10:36:17PM +0100, Rob T wrote:
> On Thursday, 13 December 2012 at 18:41:47 UTC, H. S. Teoh wrote:
> >Since each of us may have conflicting ideas about what the final
> >process should be, let's adopt the convention that if something on
> >the page is not how you understand t
On Thursday, 13 December 2012 at 21:37:07 UTC, Walter Bright
wrote:
On 12/13/2012 12:46 PM, Jacob Carlborg wrote:
On 2012-12-13 18:27, Iain Buclaw wrote:
I am confused at this commit also.
Walter argues that people are already using it so it can't
just be removed. I
say, they're using an un
On 12/13/2012 12:46 PM, Jacob Carlborg wrote:
On 2012-12-13 18:27, Iain Buclaw wrote:
I am confused at this commit also.
Walter argues that people are already using it so it can't just be removed. I
say, they're using an unreleased version of DMD, this is to be expected.
They have a large
On Thursday, 13 December 2012 at 18:41:47 UTC, H. S. Teoh wrote:
Since each of us may have conflicting ideas about what the
final process
should be, let's adopt the convention that if something on the
page is
not how you understand things should be, you should discuss on
the talk
page before ma
On 12/13/2012 11:33 AM, Andrei Alexandrescu wrote:
On 12/13/12 2:28 PM, Brad Roberts wrote:
On Thu, 13 Dec 2012, Jacob Carlborg wrote:
On 2012-12-13 10:01, Walter Bright wrote:
I thought we had that with github, but then they disabled downloads.
Yeah, we _had_, they just removed it:
https
On 12/13/2012 4:46 AM, Timon Gehr wrote:
Now they certainly are.
http://d.puremagic.com/issues/show_bug.cgi?id=9148
The following you can close if you think 'const' should not guarantee no
mutation. It does not break other parts of the type system:
http://d.puremagic.com/issues/show_bug.cgi?id=
On 12/13/2012 9:40 AM, H. S. Teoh wrote:
I wouldn't
be surprised if many (most?) programmers will be shocked to learn where
the real hotspots in their code are, contrary to whatever preconceived
notions they may have had.
I can vouch for this. I've been programming for 35 years, and I still get
On Thursday, 13 December 2012 at 01:51:27 UTC, Timon Gehr wrote:
Certainly, you can argue that the faster version should be in a
prominent place in the standard library, but the fact that it
is not does not indicate a fundamental performance problem in
the Haskell language. Also, note that I
On 12/13/2012 3:07 AM, bearophile wrote:
I agree that putting lot of similar special cased tests in the compiler is a bad
idea (also because code like $+$-$+1 is very uncommon).
But can't the already present expression range analysis be used to cover some
simple but common enough bugs?
I've see
On 12/13/2012 4:05 AM, Jacob Carlborg wrote:
On 2012-12-13 10:54, Walter Bright wrote:
I just don't see the point in adding flow analysis for that, and it'll
ding you at runtime anyway
What about code that is only executed at compile time?
CTFE would catch it.
On Wednesday, 12 December 2012 at 22:58:47 UTC, Max Samukha wrote:
On Wednesday, 12 December 2012 at 22:19:54 UTC, js.mdnq wrote:
Also, I initially tried to do
B!(A.b1.offsetof) b1;
a'la
http://forum.dlang.org/thread/mailman.2627.1355335532.5162.digitalmar...@puremagic.com
but dmd 2.
On Thursday, 13 December 2012 at 20:04:50 UTC, Dmitry Olshansky
wrote:
I think it's good.
But personally I'd expect:
* master to be what you define as dev, because e.g. GitHub puts
master as default target branch when making pull requests.
Yeah, I know it's their quirk that it's easy to miss.
On 2012-12-13 18:27, Iain Buclaw wrote:
I am confused at this commit also.
Walter argues that people are already using it so it can't just be
removed. I say, they're using an unreleased version of DMD, this is to
be expected.
--
/Jacob Carlborg
On Thursday, 13 December 2012 at 01:32:23 UTC, bearophile wrote:
Walter Bright:
Java makes no attempt to detect integer overflows.
There are various kinds of code. In some kinds of programs you
want to be more sure that the result is correct, while other
kinds of programs this need is less
On Wednesday, 12 December 2012 at 20:01:43 UTC, Timon Gehr wrote:
On 12/12/2012 03:45 AM, Walter Bright wrote:
On 12/11/2012 5:05 PM, bearophile wrote:
Walter Bright:
ML has been around for 30-40 years, and has failed to catch
on.
OcaML, Haskell, F#, and so on are all languages derived more
12/13/2012 12:13 AM, deadalnix пишет:
Let me do some proposal. If people are happy with them, I can start some
wikification.
First here are the branch already existing :
dev : development branch. It is used to merge new features.
master : is the branch where the next version is stabilized (righ
12/13/2012 6:25 PM, Simen Kjaeraas пишет:
As discussed deep in the thread "Is there any reason why arithmetic
operation
on shorts and bytes return int?"[1], D currently does not support this
behavior:
struct bbyte {
byte b;
alias b this;
}
void foo(bbyte b) {}
void baz() {
byte
On 12/13/12 2:28 PM, Brad Roberts wrote:
On Thu, 13 Dec 2012, Jacob Carlborg wrote:
On 2012-12-13 10:01, Walter Bright wrote:
I thought we had that with github, but then they disabled downloads.
Yeah, we _had_, they just removed it:
https://github.com/blog/1302-goodbye-uploads
--
/Jacob C
On Thu, 13 Dec 2012 00:22:55 -0800, Jeff Nowakowski
wrote:
On 12/12/2012 04:45 PM, Iain Buclaw wrote:
Though one of the downsides would be that if I were to leave, so would
the site.
For the stability of the project, D needs more commodity-based services
like Amazon S3, and less volun
On Thu, 13 Dec 2012, Jacob Carlborg wrote:
> On 2012-12-13 10:01, Walter Bright wrote:
>
> > I thought we had that with github, but then they disabled downloads.
>
> Yeah, we _had_, they just removed it:
>
> https://github.com/blog/1302-goodbye-uploads
>
> --
> /Jacob Carlborg
What they had
On Thursday, 13 December 2012 at 08:55:44 UTC, js.mdnq wrote:
It would be nice if D implements such a feature because it will
look more natural.
It sure would be nice. With D, you should not have to mess around
with a pointer like this.
Anyway, thanks for your efforts, we at least have a "ha
On Thursday, 13 December 2012 at 18:41:47 UTC, H. S. Teoh wrote:
On Thu, Dec 13, 2012 at 07:26:18PM +0100, Rob T wrote:
[...]
But IMO we're straying off-topic because what we really need
to do
first, is fire up a wiki page to write down and agree on (as
best as
we can) what we want to achieve (
On Thu, Dec 13, 2012 at 07:26:18PM +0100, Rob T wrote:
[...]
> But IMO we're straying off-topic because what we really need to do
> first, is fire up a wiki page to write down and agree on (as best as
> we can) what we want to achieve (a list of goals), and only after
> that can we continue on deci
On Thursday, 13 December 2012 at 15:44:25 UTC, Joseph Rushton
Wakeling wrote:
My feeling here was that as it stands Phobos is still somewhat
more in flux than D itself, not so much in terms of breaking
changes as in terms of new features being added. So, I was
wondering if it might be worthw
On Thu, Dec 13, 2012 at 09:51:44AM -0800, H. S. Teoh wrote:
> http://d.puremagic.com/issues/show_bug.cgi?id=9152
[...]
Oops, that was invalid. The real bug is here:
http://d.puremagic.com/issues/show_bug.cgi?id=9153
T
--
Right now I'm having amnesia and deja vu at the same time. I thi
H. S. Teoh:
Yeah, I think this is a case of premature optimization,
That part of the thread was not about compiler optimizations. It
was about bug detection.
Bye,
bearophile
On Thursday, 13 December 2012 at 16:57:10 UTC, David Nadlinger
wrote:
On Monday, 10 December 2012 at 00:34:33 UTC, Walter Bright
wrote:
It's time to do a release; to that end we should be working on
tidying up the regressions.
This will be the last official D1 release.
Two things which I thi
http://d.puremagic.com/issues/show_bug.cgi?id=9152
T
--
People tell me I'm stubborn, but I refuse to accept it!
On Thu, Dec 13, 2012 at 05:31:05PM +0100, Chris Cain wrote:
> On Thursday, 13 December 2012 at 09:38:18 UTC, bearophile wrote:
[...]
> >Right, but there are several cases where a little smarter compiler
> >is able to see at compile-time that something bad is present in
> >the code.
>
> The problem
On Thursday, 13 December 2012 at 15:44:25 UTC, Joseph Rushton
Wakeling wrote:
On 12/13/2012 10:07 AM, Jonathan M Davis wrote:
That makes a _lot_ more sense than the unstable => testing =>
stable model.
I like the idea of having an LTS release at some interval
(probably 1 year)
where that bran
On 13 December 2012 16:57, David Nadlinger wrote:
> On Monday, 10 December 2012 at 00:34:33 UTC, Walter Bright wrote:
>>
>> It's time to do a release; to that end we should be working on tidying up
>> the regressions.
>>
>> This will be the last official D1 release.
>
>
> Two things which I think
On Monday, 10 December 2012 at 00:34:33 UTC, Walter Bright wrote:
It's time to do a release; to that end we should be working on
tidying up the regressions.
This will be the last official D1 release.
Two things which I think we *must* address before the release,
otherwise they will hurt us i
On Thursday, 13 December 2012 at 16:15:16 UTC, Simen Kjaeraas
wrote:
But this is easily solved:
Hmmm, indeed. This might just work then...
On 2012-28-13 17:12, d coder wrote:
I do not know if I am missing something but consider:
struct Foo {
int r;
int i;
bool get() {
return true; // always return true
}
alias get this;
}
So I am wondering how it would be possible to construct Foo from a bool?
Otherwise how would
On Thursday, 13 December 2012 at 09:38:18 UTC, bearophile wrote:
That program seems to have a bug, unless the signature of foo
becomes (ref int[]).
Indeed. I'm learning how to type on a new keyboard, so most of my
brain power is being spent on figuring out where the keys are. It
took me over
I do not know if I am missing something but consider:
struct Foo {
int r;
int i;
bool get() {
return true; // always return true
}
alias get this;
}
So I am wondering how it would be possible to construct Foo from a bool?
Otherwise how would the compiler be able to figure out in wh
On 2012-38-13 15:12, Adam D. Ruppe wrote:
On Thursday, 13 December 2012 at 14:25:27 UTC, Simen Kjaeraas wrote:
foo(b); // Cannot implicitly convert byte to bbyte.
I think the way it is now is correct for alias this.. it is kinda like
implicitly casting to a base class. That's correct,
12/13/2012 4:59 AM, David Piepgrass пишет:
Maybe, but I'm still not clear what are the differences between a
normal ring buffer (not a new concept) and this "disruptor" pattern..
Key differences with a typical lock-free queue:
Nice summary. I wasn't sure where should I describing that it's no
On 12/13/2012 10:07 AM, Jonathan M Davis wrote:
That makes a _lot_ more sense than the unstable => testing => stable model.
I like the idea of having an LTS release at some interval (probably 1 year)
where that branch has bug fix releases more or less monthly. We then have a dev
release cycle wh
So if you are able to compile DMD you are able to test if the
new patch works in your case too.
The answer was negative:
http://d.puremagic.com/issues/show_bug.cgi?id=9150
Bye,
bearophile
Gopan:
Why didn't I get a compilation error? All the array sizes are
known at compile time. Right?
The good Hara and Don have teamed and they have already written a
patch and applied it:
http://d.puremagic.com/issues/show_bug.cgi?id=6883
So if you are able to compile DMD you are able to
import std.stdio;
void main()
{
int[3][2] matrix = [ [1,11,111], [2,22,222] ];
foreach(int[5] row; matrix) //if int[3], there is no error.
{
foreach(x; row)
write(x, " ");
writeln();
}
}
I get runtime er
On 12/12/2012 07:47 PM, deadalnix wrote:
No, no, please. As already stated, distro release systems intend to solve the
exact opposite problem of ours.
Yes, I did already read your earlier email objecting to a "Debian-like" model.
The thing is, it's not clear to me what actual details you're ob
On Thursday, 13 December 2012 at 14:25:27 UTC, Simen Kjaeraas
wrote:
foo(b); // Cannot implicitly convert byte to bbyte.
I think the way it is now is correct for alias this.. it is kinda
like implicitly casting to a base class. That's correct, but
going to a superclass isn't necessarily r
On Wednesday, 12 December 2012 at 20:55:52 UTC, Brad Roberts
wrote:
Generous offer. I've been meaning to build packaging into the
auto-tester
for both release builds and more frequent (nightly or maybe
even every
cycle) builds. I was going to toss them into s3 with a
cloudfront
distribution i
D does not support such implicit *construction* in return statement and
function argument.
It is a current language design, and not a bug.
Kenji Hara
2012/12/13 Simen Kjaeraas
> On 2012-22-13 04:12, Jonathan M Davis wrote:
>
> On Wednesday, December 12, 2012 13:35:59 Walter Bright wrote:
>>
On 12/13/2012 04:54 AM, Walter Bright wrote:
On 12/12/2012 5:16 PM, Timon Gehr wrote:
On 12/13/2012 12:43 AM, Walter Bright wrote:
On 12/12/2012 3:23 PM, Timon Gehr wrote:
It is somewhat similar to (the still quite broken) 'pure' in D,
Broken how?
- There is no way to specify that a deleg
On 12/13/2012 11:40 AM, bearophile wrote:
...
This thread is about spotting mistakes at compile-time, that is one of
the main advantages of having a static typing in the first place.
...
Static code analysis also works when there is no static type checking.
On 2012-12-13 10:54, Walter Bright wrote:
I just don't see the point in adding flow analysis for that, and it'll
ding you at runtime anyway
What about code that is only executed at compile time?
--
/Jacob Carlborg
On 2012-12-13 10:01, Walter Bright wrote:
I thought we had that with github, but then they disabled downloads.
Yeah, we _had_, they just removed it:
https://github.com/blog/1302-goodbye-uploads
--
/Jacob Carlborg
On Wednesday, 12 December 2012 at 08:25:04 UTC, Han wrote:
Walter Bright wrote:
Overlooked is the previous 10 years the band struggled in
obscurity.
You KNOW that D has not been "overlooked". Developers and users
with
applications give it a look (the former mostly) and then choose
something
1 - 100 of 117 matches
Mail list logo
