On 2014-12-08 08:12, Andrei Alexandrescu wrote:
I'm in Australia with limited connectivity (bandwidth cap etc). Walter?
Walter has already taken care of it.
--
/Jacob Carlborg
On 12/3/14 10:10 AM, Martin Nowak wrote:
On Tuesday, 2 December 2014 at 17:10:12 UTC, Jacob Carlborg wrote:
DMD 2.066.1 is missing in the Digitalmars FTP. The release candidates
are present but the final release is missing. This breaks DVM.
I asked several times that it gets uploaded, but neve
On 12/3/14 8:00 AM, H. S. Teoh via Digitalmars-d wrote:
I'm finding it harder and harder to accept Walter's stance that symbol
lookups should be kept simple and free from complications and convoluted
corner cases, etc.. Except that it is*already* full of convoluted
pitfalls and corner cases you
On Monday, 8 December 2014 at 04:09:19 UTC, deadalnix wrote:
On Sunday, 7 December 2014 at 15:46:59 UTC, John Colvin wrote:
On Sunday, 7 December 2014 at 15:44:55 UTC, Ola Fosheim
Grøstad wrote:
On Sunday, 7 December 2014 at 15:41:12 UTC, H. S. Teoh via
Digitalmars-d wrote:
On the same stati
On Saturday, 6 December 2014 at 13:54:23 UTC, Vic wrote:
On Saturday, 6 December 2014 at 01:37:03 UTC, deadalnix wrote:
On Friday, 5 December 2014 at 20:08:30 UTC, Vic wrote:
http://www.meetup.com/D-Lang-Sillicon-Valley
in Sunnyvale.
First meeting in Jan., and then every 6 weeks
Room holds 2
On Sunday, 7 December 2014 at 15:46:59 UTC, John Colvin wrote:
On Sunday, 7 December 2014 at 15:44:55 UTC, Ola Fosheim Grøstad
wrote:
On Sunday, 7 December 2014 at 15:41:12 UTC, H. S. Teoh via
Digitalmars-d wrote:
Haha, oops. I meant 40 hours * 5 days a week * 50 people =
1 man hours of wor
While I hear a lot of experienced programmers take this point of
view, I still don't really understand or agree with it. I believe
a good language should facilitate good design, but I don't think
it should force it. I imagine this type of principal may simplify
code review for large projects, b
On Mon, 08 Dec 2014 02:58:45 +
bitwise via Digitalmars-d wrote:
> > if you want to allow external pragmas that allows poking
> > private module
> > data... well, just make everything in that module public, you
> > just
> > killed the whole protection thing. ;-)
>
> This is what I mean, but
if you want to allow external pragmas that allows poking
private module
data... well, just make everything in that module public, you
just
killed the whole protection thing. ;-)
This is what I mean, but I don't think it would 'kill' anything.
It's not like I'm suggesting that cast(public) be
On Mon, 08 Dec 2014 02:29:49 +
Freddy via Digitalmars-d wrote:
> On Monday, 8 December 2014 at 02:04:58 UTC, ketmar via
> Digitalmars-d wrote:
> > On Mon, 08 Dec 2014 01:50:44 +
> > Freddy via Digitalmars-d wrote:
> >
> >> I would like if usize wasn't implictly convertable to uint or
> >
On Monday, 8 December 2014 at 02:04:58 UTC, ketmar via
Digitalmars-d wrote:
On Mon, 08 Dec 2014 01:50:44 +
Freddy via Digitalmars-d wrote:
I would like if usize wasn't implictly convertable to uint or
ulong
me too, but this change is too radical. it will not break any
of my
own code ('cau
On Mon, 08 Dec 2014 01:50:44 +
Freddy via Digitalmars-d wrote:
> I would like if usize wasn't implictly convertable to uint or
> ulong
me too, but this change is too radical. it will not break any of my
own code ('cause i used to write casts for that stupid 64-bit systems to
shut up), but i d
On Monday, 8 December 2014 at 01:30:35 UTC, ketmar via
Digitalmars-d wrote:
Hello.
i don't like `size_t`. for many month i avoied using it
wherever that
was possible, 'cause i feel something wrong with it. and today
i found
the soultion!
let's see how other D types are named: `int`, `uint`,
Hello.
i don't like `size_t`. for many month i avoied using it wherever that
was possible, 'cause i feel something wrong with it. and today i found
the soultion!
let's see how other D types are named: `int`, `uint`, `byte` (oh, well,
this name sux), `ulong`. see the pattern? so i decided to renam
On Sunday, 7 December 2014 at 12:35:00 UTC, Peter Alexander wrote:
We don't need the subreddit. We have these forums.
Rust has their own forum, but it's for implementers. Most of
their discussions/announcements happen at reddit. That's why it
is more active and maintained.
We already have an
On Sun, 7 Dec 2014 20:55:04 +0530
Shriramana Sharma via Digitalmars-d wrote:
> I wonder if it is me or everyone is receiving some sort of
> kitchen-related spam via the mailing list?
not that many. something about 5-6 letters withing a month (at it's
maximum).
> The email ID or keywords
> they a
On Sun, 07 Dec 2014 21:44:51 +
bitwise via Digitalmars-d wrote:
> I would like to be able to reflect private members though... Is
> there any way to give a module private access to an unrelated
> module?
nope. and i hope there will be no such thing. ;-)
> I understand that packages are meant
On 12/7/2014 2:58 PM, bearophile wrote:
When C++ programmers say that D-style ranges can't do everything C++ iterators
can do, they seem to miss that sometimes it's a good idea to adopt a simpler
language feature, that doesn't cover 100% usages, if it covers 80-90% of the
cases, and has a simpler
On 12/7/2014 4:34 AM, Peter Alexander wrote:
We don't need the subreddit. We have these forums.
Rust has their own forum, but it's for implementers. Most of their
discussions/announcements happen at reddit. That's why it is more active and
maintained.
We already have an active forum here for ev
On Sun, Dec 07, 2014 at 06:08:51PM +, Sean Kelly via Digitalmars-d wrote:
> On Saturday, 6 December 2014 at 16:32:30 UTC, H. S. Teoh via Digitalmars-d
> wrote:
> >On Sat, Dec 06, 2014 at 05:10:09PM +0100, Joseph Rushton Wakeling via
> >Digitalmars-d wrote:
> >>On 05/12/14 23:03, deadalnix via D
On Sun, Dec 07, 2014 at 04:58:23PM +, via Digitalmars-d wrote:
> On Sunday, 7 December 2014 at 16:08:27 UTC, H. S. Teoh via Digitalmars-d
> wrote:
> >Hahaha... you're right, I'm not thinking straight. OK, so it's 40*50
> >= 200 man-hours per week. Hmph... I'm about two orders of magnitude
> >of
Walter Bright:
There are probably only a handful of people on the planet who
actually understand C++ ref. I wished very hard to avoid that
with D ref.
When C++ programmers say that D-style ranges can't do everything
C++ iterators can do, they seem to miss that sometimes it's a
good idea to
Nick Treleaven:
This might also make the proposed 'int[$] = [...];' syntax
unnecessary.
Or might not. The [$] proposal is very refined.
Bye,
bearophile
08-Dec-2014 01:38, John Colvin пишет:
On Sunday, 7 December 2014 at 22:13:50 UTC, Dmitry Olshansky wrote:
08-Dec-2014 00:36, John Colvin пишет:
On Sunday, 7 December 2014 at 19:56:49 UTC, Dmitry Olshansky wrote:
06-Dec-2014 18:33, H. S. Teoh via Digitalmars-d пишет:
On Sat, Dec 06, 2014 at 03
On Sunday, 7 December 2014 at 22:13:50 UTC, Dmitry Olshansky
wrote:
08-Dec-2014 00:36, John Colvin пишет:
On Sunday, 7 December 2014 at 19:56:49 UTC, Dmitry Olshansky
wrote:
06-Dec-2014 18:33, H. S. Teoh via Digitalmars-d пишет:
On Sat, Dec 06, 2014 at 03:26:08PM +, Russel Winder via
Digit
08-Dec-2014 00:36, John Colvin пишет:
On Sunday, 7 December 2014 at 19:56:49 UTC, Dmitry Olshansky wrote:
06-Dec-2014 18:33, H. S. Teoh via Digitalmars-d пишет:
On Sat, Dec 06, 2014 at 03:26:08PM +, Russel Winder via
Digitalmars-d wrote:
[...]
primitive are passed by value; arrays and u
On Sat, Dec 6, 2014 at 7:26 AM, Russel Winder via Digitalmars-d <
digitalmars-d@puremagic.com> wrote:
>
> Primitive types are scheduled for removal, leaving only reference
> types.
>
>
Are you referring to: http://openjdk.java.net/jeps/169 ?
On Sunday, 7 December 2014 at 06:25:48 UTC, ketmar via
Digitalmars-d wrote:
On Sun, 07 Dec 2014 05:42:31 +
bitwise via Digitalmars-d wrote:
what you actually want is some cross-module compile-time data
storage.
this is impossible to implement. at least to make it reliable.
with separate
On Sunday, 7 December 2014 at 19:56:49 UTC, Dmitry Olshansky
wrote:
06-Dec-2014 18:33, H. S. Teoh via Digitalmars-d пишет:
On Sat, Dec 06, 2014 at 03:26:08PM +, Russel Winder via
Digitalmars-d wrote:
[...]
primitive are passed by value; arrays and user defined
types are
passed by refer
On 12/7/2014 6:12 AM, Dicebot wrote:
But from existing cases it doesn't seem working good enough. For example, not
being able to represent idiom of `scope ref int foo(scope ref int x) { return x;
}` seems very limiting.
scope ref int foo(ref int x);
will do it.
I also don't consider `ref`
On 12/7/2014 7:25 AM, Shriramana Sharma via Digitalmars-d wrote:
I wonder if it is me or everyone is receiving some sort of
kitchen-related spam via the mailing list? The email ID or keywords
they are using seem to be relatively predictable and unrelated to
programming so I wonder whether the lis
06-Dec-2014 18:33, H. S. Teoh via Digitalmars-d пишет:
On Sat, Dec 06, 2014 at 03:26:08PM +, Russel Winder via Digitalmars-d wrote:
[...]
primitive are passed by value; arrays and user defined types are
passed by reference only (killing memory usage)
Primitive types are scheduled for r
07-Dec-2014 16:39, Dicebot пишет:
On Saturday, 6 December 2014 at 09:07:34 UTC, Dmitry Olshansky wrote:
Solved in Scala:
- operator overloading
- properties - that + optional (), a library writer still can enforce
() to be used
- only and exactly one class - any number in any combination
- every
On Sunday, 7 December 2014 at 13:39:38 UTC, Dicebot wrote:
On Saturday, 6 December 2014 at 09:07:34 UTC, Dmitry Olshansky
wrote:
Solved in Scala:
- operator overloading
- properties - that + optional (), a library writer still can
enforce () to be used
- only and exactly one class - any number
On Saturday, 6 December 2014 at 16:32:30 UTC, H. S. Teoh via
Digitalmars-d wrote:
On Sat, Dec 06, 2014 at 05:10:09PM +0100, Joseph Rushton
Wakeling via Digitalmars-d wrote:
On 05/12/14 23:03, deadalnix via Digitalmars-d wrote:
>http://www.reddit.com/r/programming/comments/2ocmvb/stdstring_is_res
On 04/12/2014 12:55, bearophile wrote:
Regarding array literals, some people proposed a syntax for fixed-size
arrays to avoid heap-allocations (the "s" after the array literal):
void foo(int[2]) {}
void bar(scope int[]) {}
void main() @nogc {
foo([1, 2]s);
bar([1, 2]s);
}
I think eve
On 05/12/2014 23:58, Walter Bright wrote:
2) `scope ref` return values cannot be stored.
scope ref int foo();
void bar(scope ref int a);
foo().bar();// allowed
scope tmp = foo(); // not allowed
tmp.bar();
Right
From the DIP:
"The lifetime of a scope return
On Sunday, 7 December 2014 at 16:08:27 UTC, H. S. Teoh via
Digitalmars-d wrote:
Hahaha... you're right, I'm not thinking straight. OK, so it's
40*50 =
200 man-hours per week. Hmph... I'm about two orders of
magnitude off.
log10(40/8) = 0.6989700043360189 orders of magnitude…
On 2014-12-07 11:50, Iain Buclaw via Digitalmars-d wrote:
You can add shorthand aliases for them too. :)
@forceinline void foo ();
Good point.
--
/Jacob Carlborg
On Sun, Dec 07, 2014 at 04:01:36PM +, via Digitalmars-d wrote:
> On Sunday, 7 December 2014 at 15:41:12 UTC, H. S. Teoh via Digitalmars-d
> wrote:
> >On Sun, Dec 07, 2014 at 11:03:13AM +, via Digitalmars-d wrote:
> >>>That's 40 hours * 7 days * 50
> >>>developers = 14000 man-hours worth of
On Sunday, 7 December 2014 at 15:41:12 UTC, H. S. Teoh via
Digitalmars-d wrote:
On Sun, Dec 07, 2014 at 11:03:13AM +, via Digitalmars-d
wrote:
>That's 40 hours * 7 days * 50
>developers = 14000 man-hours worth of work.
Poor guys, working 7 days a week, 40 hours a day...
Haha, oops. I mean
On Sunday, 7 December 2014 at 15:46:59 UTC, John Colvin wrote:
IIRC the country with longest working hours in the EU is Greece.
The hours seem longer when it is hot…
On Sunday, 7 December 2014 at 15:44:55 UTC, Ola Fosheim Grøstad
wrote:
On Sunday, 7 December 2014 at 15:41:12 UTC, H. S. Teoh via
Digitalmars-d wrote:
Haha, oops. I meant 40 hours * 5 days a week * 50 people =
1 man hours of work. Still a lot.
The long work hours is why the US is ahead of
On Sunday, 7 December 2014 at 15:41:12 UTC, H. S. Teoh via
Digitalmars-d wrote:
Haha, oops. I meant 40 hours * 5 days a week * 50 people =
1 man hours of work. Still a lot.
The long work hours is why the US is ahead of Europe.
On Sun, Dec 07, 2014 at 11:03:13AM +, via Digitalmars-d wrote:
> >That's 40 hours * 7 days * 50
> >developers = 14000 man-hours worth of work.
>
> Poor guys, working 7 days a week, 40 hours a day...
Haha, oops. I meant 40 hours * 5 days a week * 50 people = 1 man
hours of work. Still a lo
I wonder if it is me or everyone is receiving some sort of
kitchen-related spam via the mailing list? The email ID or keywords
they are using seem to be relatively predictable and unrelated to
programming so I wonder whether the listadmin hasn't had the time to
kick out this intruder?
--
Shrirama
On Sunday, 7 December 2014 at 13:47:09 UTC, Dicebot wrote:
However I was not speaking about plain procedural/imperative
paradigm as better alternative but functional and generic ones.
First one helps with eliminating state in general. Second one
allows to use the very same mocks in much more li
On Thursday, 4 December 2014 at 09:25:11 UTC, Walter Bright wrote:
http://wiki.dlang.org/DIP69
Despite its length, this is a fairly simple proposal. It adds
the missing semantics for the 'scope' storage class in order to
make it possible to pass a reference to a function without it
being poss
On Saturday, 6 December 2014 at 07:56:48 UTC, Paulo Pinto wrote:
On Saturday, 6 December 2014 at 01:53:03 UTC, Rikki Cattermole
wrote:
On 6/12/2014 5:45 a.m., Dicebot wrote:
In my opinion OOP is very unfriendly for testing as a
paradigm in
general. The very necessity to create mocks is usually
On Saturday, 6 December 2014 at 09:07:34 UTC, Dmitry Olshansky
wrote:
Solved in Scala:
- operator overloading
- properties - that + optional (), a library writer still can
enforce () to be used
- only and exactly one class - any number in any combination
- everything class - sort of, it has 'ob
I wonder if Copr could be used to create a Fedora project repository
for all the D bits and pieces in the way that D-Apt does things for
Debian?
https://fedorahosted.org/copr/wiki/UserDocs
--
Russel.
=
Dr Russel Wind
On Friday, 5 December 2014 at 23:25:11 UTC, Walter Bright wrote:
https://www.reddit.com/r/d_language/
It's the default, and is kinda boring. Compare with the rust
subreddit:
http://www.reddit.com/r/rust/
While not great, it's much better than ours.
We don't need the subreddit. We have
On Sunday, 7 December 2014 at 06:52:38 UTC, Sebastiaan Koppe
wrote:
How would it break anything though? Wouldn't functions eligible
for `consume` already have the programmer ensuring the
arguments haven't escaped before/after the function call? In
case they did a bad job - sure it would break -
That's 40 hours * 7 days * 50
developers = 14000 man-hours worth of work.
Poor guys, working 7 days a week, 40 hours a day...
On 6/12/2014 5:45 a.m., Dicebot wrote:
In my opinion OOP is very unfriendly for testing as a paradigm
in general. The very necessity to create mocks is usually an
alarm.
I am curious how you would write tests without mocks.
On 7 Dec 2014 10:40, "Jacob Carlborg via Digitalmars-d" <
digitalmars-d@puremagic.com> wrote:
>
> On 2014-12-07 01:49, Manu via Digitalmars-d wrote:
>
>> I have std.simd sitting here, and I really want to finish it, but I
>> still don't have the tools to do so.
>> I need, at least, forceinline to c
On Friday, 5 December 2014 at 23:58:41 UTC, Walter Bright wrote:
On 12/5/2014 8:48 AM, "Marc Schütz" " wrote:
scope ref int foo();
scope ref int bar1(ref int a) {
return a;
}
scope ref int bar2(scope ref int a) {
return a;
}
ref int bar3(ref int a) {
On 2014-12-07 01:49, Manu via Digitalmars-d wrote:
I have std.simd sitting here, and I really want to finish it, but I
still don't have the tools to do so.
I need, at least, forceinline to complete it, but that one *is*
controversial - we've talked about this for years.
GDC and LDC both have a
On Sunday, 7 December 2014 at 06:52:38 UTC, Sebastiaan Koppe
wrote:
On Saturday, 6 December 2014 at 12:38:24 UTC, Ola Fosheim
Grøstad wrote:
On Saturday, 6 December 2014 at 04:31:48 UTC, Sebastiaan Koppe
wrote:
I am a big proponent of dataflow analyses, but I got the
feeling people think is i
59 matches
Mail list logo
