On Saturday, 8 September 2018 at 14:20:10 UTC, Laeeth Isharc
wrote:
Religions have believers but not supporters - in fact saying
you are a supporter says you are not a member of that faith or
community.
If you are a supporter of Jesus Christ's efforts, then you most
certainly are a christian.
On Saturday, September 8, 2018 8:05:04 AM MDT Laeeth Isharc via Digitalmars-
d wrote:
> On Thursday, 6 September 2018 at 20:15:22 UTC, Jonathan M Davis
>
> wrote:
> > On Thursday, September 6, 2018 1:04:45 PM MDT aliak via
> >
> > Digitalmars-d wrote:
> >> D makes the code-point case default and he
On Thursday, September 6, 2018 3:15:59 PM MDT aliak via Digitalmars-d wrote:
> On Thursday, 6 September 2018 at 20:15:22 UTC, Jonathan M Davis
>
> wrote:
> > On Thursday, September 6, 2018 1:04:45 PM MDT aliak via
> >
> > Digitalmars-d wrote:
> >> D makes the code-point case default and hence that
On Thursday, 6 September 2018 at 14:42:14 UTC, Chris wrote:
On Thursday, 6 September 2018 at 14:30:38 UTC, Guillaume Piolat
wrote:
On Thursday, 6 September 2018 at 13:30:11 UTC, Chris wrote:
And autodecode is a good example of experts getting it wrong,
because, you know, you cannot be an expert
On Thursday, 6 September 2018 at 20:15:22 UTC, Jonathan M Davis
wrote:
On Thursday, September 6, 2018 1:04:45 PM MDT aliak via
Digitalmars-d wrote:
D makes the code-point case default and hence that becomes the
simplest to use. But unfortunately, the only thing I can think
of
that requires cod
On Thursday, 6 September 2018 at 17:19:01 UTC, Joakim wrote:
No, Swift counts grapheme clusters by default, so it gives 1. I
suggest you read the linked Swift chapter above. I think it's
the wrong choice for performance, but they chose to emphasize
intuitiveness for the common case.
I like to
On Thursday, 6 September 2018 at 20:15:22 UTC, Jonathan M Davis
wrote:
On Thursday, September 6, 2018 1:04:45 PM MDT aliak via
Digitalmars-d wrote:
D makes the code-point case default and hence that becomes the
simplest to use. But unfortunately, the only thing I can think
of
that requires cod
On Thursday, September 6, 2018 1:04:45 PM MDT aliak via Digitalmars-d wrote:
> D makes the code-point case default and hence that becomes the
> simplest to use. But unfortunately, the only thing I can think of
> that requires code point representations is when dealing
> specifically with unicode al
On Thursday, 6 September 2018 at 16:44:11 UTC, H. S. Teoh wrote:
On Thu, Sep 06, 2018 at 02:42:58PM +, Dukc via
Digitalmars-d wrote:
On Thursday, 6 September 2018 at 14:17:28 UTC, aliak wrote:
> // D
> auto a = "á";
> auto b = "á";
> auto c = "\u200B";
> auto x = a ~ c ~ a;
> auto y = b ~ c
On Thursday, September 6, 2018 10:44:11 AM MDT H. S. Teoh via Digitalmars-d
wrote:
> On Thu, Sep 06, 2018 at 02:42:58PM +, Dukc via Digitalmars-d wrote:
> > On Thursday, 6 September 2018 at 14:17:28 UTC, aliak wrote:
> > > // D
> > > auto a = "á";
> > > auto b = "á";
> > > auto c = "\u200B";
On Thursday, 6 September 2018 at 16:44:11 UTC, H. S. Teoh wrote:
On Thu, Sep 06, 2018 at 02:42:58PM +, Dukc via
Digitalmars-d wrote:
On Thursday, 6 September 2018 at 14:17:28 UTC, aliak wrote:
> // D
> auto a = "á";
> auto b = "á";
> auto c = "\u200B";
> auto x = a ~ c ~ a;
> auto y = b ~ c
On Thu, Sep 06, 2018 at 02:42:58PM +, Dukc via Digitalmars-d wrote:
> On Thursday, 6 September 2018 at 14:17:28 UTC, aliak wrote:
> > // D
> > auto a = "á";
> > auto b = "á";
> > auto c = "\u200B";
> > auto x = a ~ c ~ a;
> > auto y = b ~ c ~ b;
> >
> > writeln(a.length); // 2 wtf
> > writeln
On Thu, Sep 6, 2018 at 4:45 PM Dukc via Digitalmars-d <
digitalmars-d@puremagic.com> wrote:
> On Thursday, 6 September 2018 at 14:17:28 UTC, aliak wrote:
> > // D
> > auto a = "á";
> > auto b = "á";
> > auto c = "\u200B";
> > auto x = a ~ c ~ a;
> > auto y = b ~ c ~ b;
> >
> > writeln(a.length);
On Thursday, 6 September 2018 at 14:42:14 UTC, Chris wrote:
Usually a sign to move on...
You have said that at least 10 times in this very thread.
Doomsayers are as old as D. It will be doing OK.
On Thursday, 6 September 2018 at 14:17:28 UTC, aliak wrote:
Hehe, it's already a bit laughable that correctness is not
preferred.
// Swift
let a = "á"
let b = "á"
let c = "\u{200B}" // zero width space
let x = a + c + a
let y = b + c + b
print(a.count) // 1
print(b.count) // 1
print(x.count)
On Thursday, 6 September 2018 at 14:30:38 UTC, Guillaume Piolat
wrote:
On Thursday, 6 September 2018 at 13:30:11 UTC, Chris wrote:
And autodecode is a good example of experts getting it wrong,
because, you know, you cannot be an expert in all fields. I
think the problem was that it was discover
On Thursday, 6 September 2018 at 14:17:28 UTC, aliak wrote:
// D
auto a = "á";
auto b = "á";
auto c = "\u200B";
auto x = a ~ c ~ a;
auto y = b ~ c ~ b;
writeln(a.length); // 2 wtf
writeln(b.length); // 3 wtf
writeln(x.length); // 7 wtf
writeln(y.length); // 9 wtf
writeln(a == b); // false wtf
On Thursday, 6 September 2018 at 14:33:27 UTC, rikki cattermole
wrote:
Either decide a list of conditions before we can break to
remove it, or yes lets let this idea go. It isn't helping
anyone.
Can't you just let mark it as deprecated and provide a library
compatibility range (100% compatibl
On 07/09/2018 2:30 AM, Guillaume Piolat wrote:
On Thursday, 6 September 2018 at 13:30:11 UTC, Chris wrote:
And autodecode is a good example of experts getting it wrong, because,
you know, you cannot be an expert in all fields. I think the problem
was that it was discovered too late.
There are
On Thursday, 6 September 2018 at 13:30:11 UTC, Chris wrote:
And autodecode is a good example of experts getting it wrong,
because, you know, you cannot be an expert in all fields. I
think the problem was that it was discovered too late.
There are very valid reasons not to talk about auto-decod
On Wednesday, 5 September 2018 at 22:00:27 UTC, H. S. Teoh wrote:
Because grapheme decoding is SLOW, and most of the time you
don't even need it anyway. SLOW as in, it will easily add a
factor of 3-5 (if not worse!) to your string processing time,
which will make your natively-compiled D code
On Thursday, 6 September 2018 at 11:01:55 UTC, Guillaume Piolat
wrote:
So Unicode in D works EXACTLY as expected, yet people in this
thread act as if the house is on fire.
Expected by who? The Unicode expert or the user?
D dying because of auto-decoding? Who can possibly think that
in its
On Thursday, 6 September 2018 at 11:01:55 UTC, Guillaume Piolat
wrote:
Let me break that to you: core developer are language experts.
The rest of us are users, that yes it doesn't make us
necessarily qualified to design a language.
Who?
On Thursday, 6 September 2018 at 11:43:31 UTC, ag0aep6g wrote:
You say that D users shouldn't need a '"Unicode license" before
they do anything with strings'. And you say that Python 3 gets
it right (or maybe less wrong than D).
But here we see that Python requires a similar amount of
Unico
On 09/06/2018 12:40 PM, Chris wrote:
To avoid this you have to normalize and recompose any decomposed
characters. I remember that Mac OS X used (and still uses?) decomposed
characters by default, so when you typed 'á' into your cli, it would
automatically decompose it to 'a' + acute. `string` h
On Thursday, 6 September 2018 at 11:19:14 UTC, Chris wrote:
One problem imo is that they mixed the terms up: "Grapheme: A
minimally distinctive unit of writing in the context of a
particular writing system." In linguistics a grapheme is not a
single character like "á" or "g". It may also be
On Thursday, 6 September 2018 at 10:44:45 UTC, Joakim wrote:
[snip]
You're not being fair here, Chris. I just saw this SO question
that I think exemplifies how most programmers react to Unicode:
"Trying to understand the subtleties of modern Unicode is
making my head hurt. In particular, the
On Wednesday, 5 September 2018 at 07:48:34 UTC, Chris wrote:
import std.array : array;
import std.stdio : writefln;
import std.uni : byCodePoint, byGrapheme;
import std.utf : byCodeUnit;
void main() {
string first = "á";
writefln("%d", first.length); // prints 2
auto firstCU = "á".byC
On Thursday, 6 September 2018 at 09:35:27 UTC, Chris wrote:
On Thursday, 6 September 2018 at 08:44:15 UTC, nkm1 wrote:
On Wednesday, 5 September 2018 at 07:48:34 UTC, Chris wrote:
On Tuesday, 4 September 2018 at 21:36:16 UTC, Walter Bright
wrote:
Autodecode - I've suffered under that, too. Th
On Thursday, 6 September 2018 at 10:22:22 UTC, ag0aep6g wrote:
On 09/06/2018 09:23 AM, Chris wrote:
Python 3 gives me this:
print(len("á"))
1
Python 3 also gives you this:
print(len("á"))
2
(The example might not survive transfer from me to you if
Unicode normalization happens along the w
On 09/06/2018 09:23 AM, Chris wrote:
Python 3 gives me this:
print(len("á"))
1
Python 3 also gives you this:
print(len("á"))
2
(The example might not survive transfer from me to you if Unicode
normalization happens along the way.)
That's when you enter the 'á' as 'a' followed by U+0301
On Thursday, 6 September 2018 at 08:44:15 UTC, nkm1 wrote:
On Wednesday, 5 September 2018 at 07:48:34 UTC, Chris wrote:
On Tuesday, 4 September 2018 at 21:36:16 UTC, Walter Bright
wrote:
Autodecode - I've suffered under that, too. The solution was
fairly simple. Append .byCodeUnit to strings
On Wednesday, 5 September 2018 at 07:48:34 UTC, Chris wrote:
On Tuesday, 4 September 2018 at 21:36:16 UTC, Walter Bright
wrote:
Autodecode - I've suffered under that, too. The solution was
fairly simple. Append .byCodeUnit to strings that would
otherwise autodecode. Annoying, but hardly a sho
On Thursday, 6 September 2018 at 07:54:09 UTC, Joakim wrote:
On Thursday, 6 September 2018 at 07:23:57 UTC, Chris wrote:
On Wednesday, 5 September 2018 at 22:00:27 UTC, H. S. Teoh
wrote:
//
Seriously, people need to get over the fantasy that they can
just use Unicode without understanding
On 06/09/2018 7:54 PM, Joakim wrote:
On Thursday, 6 September 2018 at 07:23:57 UTC, Chris wrote:
On Wednesday, 5 September 2018 at 22:00:27 UTC, H. S. Teoh wrote:
//
Seriously, people need to get over the fantasy that they can just use
Unicode without understanding how Unicode works. Most o
On Thursday, 6 September 2018 at 07:23:57 UTC, Chris wrote:
On Wednesday, 5 September 2018 at 22:00:27 UTC, H. S. Teoh
wrote:
//
Seriously, people need to get over the fantasy that they can
just use Unicode without understanding how Unicode works.
Most of the time, you can get the illusio
On Thursday, 6 September 2018 at 07:23:57 UTC, Chris wrote:
Seriously, people need to get over the fantasy that they can
just use Unicode without understanding how Unicode works.
Most of the time, you can get the illusion that it's working,
but actually 99% of the time the code is actually wr
On Wednesday, 5 September 2018 at 22:00:27 UTC, H. S. Teoh wrote:
//
Seriously, people need to get over the fantasy that they can
just use Unicode without understanding how Unicode works. Most
of the time, you can get the illusion that it's working, but
actually 99% of the time the code is
On Wed, Sep 05, 2018 at 09:33:27PM +, aliak via Digitalmars-d wrote:
[...]
> The dstring is only ok because the 2 code units fit in a dchar right?
> But all the other ones are as expected right?
And dstring will be wrong once you have non-precomposed diacritics and
other composing sequences.
On Wednesday, 5 September 2018 at 07:48:34 UTC, Chris wrote:
On Tuesday, 4 September 2018 at 21:36:16 UTC, Walter Bright
wrote:
Autodecode - I've suffered under that, too. The solution was
fairly simple. Append .byCodeUnit to strings that would
otherwise autodecode. Annoying, but hardly a sho
On 9/4/2018 5:37 PM, bachmeier wrote:
Having to deal with the
possibility that others might have any of twelve different compiler versions
installed just isn't sustainable.
Back in the bad old DOS days, my compiler depended on the Microsoft linker,
which was helpfully included on the DOS dist
On Tuesday, 4 September 2018 at 21:36:16 UTC, Walter Bright wrote:
Autodecode - I've suffered under that, too. The solution was
fairly simple. Append .byCodeUnit to strings that would
otherwise autodecode. Annoying, but hardly a showstopper.
import std.array : array;
import std.stdio : write
On Friday, 24 August 2018 at 19:26:40 UTC, Walter Bright wrote:
On 8/24/2018 6:04 AM, Chris wrote:
For about a year I've had the feeling that D is moving too
fast and going nowhere at the same time. D has to slow down
and get stable. D is past the experimental stage. Too many
people use it for
On Tuesday, 4 September 2018 at 21:36:16 UTC, Walter Bright wrote:
On 9/1/2018 4:12 AM, Chris wrote:
Hope is usually the last thing to die. But one has to be wise
enough to see that sometimes there is nothing one can do. As
things are now, for me personally D is no longer an option,
because of
On 9/4/2018 12:59 PM, Timon Gehr wrote:
[...]
Thanks for the great explanation! Not sure I thoroughly understand it, though.
Therefore, D immutable/pure are both too strong and too weak: they prevent
@system code from implementing value representations that internally use
mutation (therefor
On 9/1/2018 4:12 AM, Chris wrote:
Hope is usually the last thing to die. But one has to be wise enough to see that
sometimes there is nothing one can do. As things are now, for me personally D is
no longer an option, because of simple basic things, like autodecode, a flaw
that will be there for
On 29.08.2018 22:01, Walter Bright wrote:
On 8/29/2018 10:50 AM, Timon Gehr wrote:
D const/immutable is stronger than immutability in Haskell (which is
usually _lazy_).
I know Haskell is lazy, but don't see the connection with a weaker
immutability guarantee.
In D, you can't have a lazy val
On Tuesday, 4 September 2018 at 13:34:03 UTC,
TheSixMillionDollarMan wrote:
I think D's 'core' problem, is that it's trying to compete
with, what are now, widely used, powerful, and well supported
languages, with sophisticate ecosystems in place already.
C/C++/Java/C# .. just for beginners.
Y
On Friday, 24 August 2018 at 13:21:25 UTC, Jonathan M Davis wrote:
On Friday, August 24, 2018 6:05:40 AM MDT Mike Franklin via
Digitalmars-d wrote:
> You're basically trying to bypass the OS' public API if
> you're trying to bypass libc.
No I'm trying to bypass libc and use the OS API directly
The first search engines were created in 1993, google came
along in 1998 after at least two dozen others in that list, and
didn't make a profit till 2001. Some of those early competitors
were giant "billion dollar global companies," yet it's google
that dominates the web search engine market to
On Tuesday, 4 September 2018 at 14:23:33 UTC, Joakim wrote:
The first search engines were created in 1993, google came
along in 1998 after at least two dozen others in that list, and
didn't make a profit till 2001. Some of those early competitors
were giant "billion dollar global companies," ye
On Tuesday, 4 September 2018 at 13:34:03 UTC,
TheSixMillionDollarMan wrote:
On Tuesday, 4 September 2018 at 01:36:53 UTC, Mike Parker wrote:
On Monday, 3 September 2018 at 18:26:57 UTC, Chris wrote:
And of course, low manpower and funding aren't the complete
picture. Management also play a rol
On Tuesday, 4 September 2018 at 01:36:53 UTC, Mike Parker wrote:
On Monday, 3 September 2018 at 18:26:57 UTC, Chris wrote:
And of course, low manpower and funding aren't the complete
picture. Management also play a role. Both Walter and Andrei
have freely admitted they are not managers and tha
On Tuesday, 4 September 2018 at 09:40:23 UTC, Ecstatic Coder
wrote:
But it seems that the latest version of "std.file.copy" now
completely ignores the "PreserveAttributes.no" argument on
Windows, which made recent Windows builds of Resync fail on
read-only files.
Very typical...
While D rema
On Thursday, 23 August 2018 at 03:50:44 UTC, Shachar Shemesh
wrote:
On 22/08/18 21:34, Ali wrote:
On Wednesday, 22 August 2018 at 17:42:56 UTC, Joakim wrote:
Pretty positive overall, and the negatives he mentions are
fairly obvious to anyone paying attention.
Yea, I agree, the negatives are n
On Tuesday, 4 September 2018 at 05:38:49 UTC, Iain Buclaw wrote:
On 4 September 2018 at 04:19, Laeeth Isharc via Digitalmars-d
wrote:
On Monday, 3 September 2018 at 16:07:21 UTC, RhyS wrote:
A good example being the resources going into DMD, LDC,
GDC... 3 Compilers for one language, when eve
On Monday, 3 September 2018 at 16:41:32 UTC, Iain Buclaw wrote:
15 years ago, people were complaining that there was only one D
compiler. It is ironic that people now complain that there's
too many.
One needs multiple implementations to confirm the accuracy of the
language specification. D s
On Tuesday, 4 September 2018 at 01:36:53 UTC, Mike Parker wrote:
On Monday, 3 September 2018 at 18:26:57 UTC, Chris wrote:
I think this sort of misunderstanding is the source of a lot
of friction on this forum. Some users think (or in my case:
thought) that D will be a sound and stable langu
On Tuesday, 4 September 2018 at 01:36:53 UTC, Mike Parker wrote:
D is not a petri dish for testing ideas. It's not an experiment.
Well, the general consensus for programming languages is that it
a language is experimental
(or proprietary) until it is fully specced out as a stable
formal stan
On Tuesday, 4 September 2018 at 02:19:20 UTC, Laeeth Isharc wrote:
On Monday, 3 September 2018 at 16:07:21 UTC, RhyS wrote:
On Monday, 3 September 2018 at 15:41:48 UTC, Laurent Tréguier
wrote:
Yes. It almost sounds like a smooth experience would be a bad
thing to have, especially with the class
On Monday, 3 September 2018 at 22:30:47 UTC, Chris wrote:
On Monday, 3 September 2018 at 18:52:45 UTC, Laurent Tréguier
wrote:
On Monday, 3 September 2018 at 18:26:57 UTC, Chris wrote:
it should come with a warning label that says "D is in many
parts still at an experimental stage and ships wit
On 4 September 2018 at 04:19, Laeeth Isharc via Digitalmars-d
wrote:
> On Monday, 3 September 2018 at 16:07:21 UTC, RhyS wrote:
>>
>> A good example being the resources going into DMD, LDC, GDC... 3 Compilers
>> for one language, when even well funded languages stick to one compiler. And
>> now so
On Mon, 3 Sep 2018 at 19:35, Laeeth Isharc via Digitalmars-d
wrote:
>
> On Tuesday, 4 September 2018 at 02:24:25 UTC, Manu wrote:
> > On Mon, 3 Sep 2018 at 18:45, Laeeth Isharc via Digitalmars-d
> > wrote:
> >>
> >> On Monday, 3 September 2018 at 17:15:03 UTC, Laurent Tréguier
> >> wrote:
> >> >
On Tuesday, 4 September 2018 at 02:24:25 UTC, Manu wrote:
On Mon, 3 Sep 2018 at 18:45, Laeeth Isharc via Digitalmars-d
wrote:
On Monday, 3 September 2018 at 17:15:03 UTC, Laurent Tréguier
wrote:
> On Monday, 3 September 2018 at 16:55:10 UTC, Jonathan M
> Davis wrote:
>> Most of the work that
On Mon, 3 Sep 2018 at 18:45, Laeeth Isharc via Digitalmars-d
wrote:
>
> On Monday, 3 September 2018 at 17:15:03 UTC, Laurent Tréguier
> wrote:
> > On Monday, 3 September 2018 at 16:55:10 UTC, Jonathan M Davis
> > wrote:
> >> Most of the work that gets done is the stuff that the folks
> >> contribu
On Monday, 3 September 2018 at 16:07:21 UTC, RhyS wrote:
On Monday, 3 September 2018 at 15:41:48 UTC, Laurent Tréguier
wrote:
Yes. It almost sounds like a smooth experience would be a bad
thing to have, especially with the classic "you don't need an
IDE anyway" speech. Editing experience seems
On Monday, 3 September 2018 at 17:15:03 UTC, Laurent Tréguier
wrote:
On Monday, 3 September 2018 at 16:55:10 UTC, Jonathan M Davis
wrote:
Most of the work that gets done is the stuff that the folks
contributing think is the most important - frequently what is
most important for them for what th
On Monday, 3 September 2018 at 18:26:57 UTC, Chris wrote:
I think this sort of misunderstanding is the source of a lot of
friction on this forum. Some users think (or in my case:
thought) that D will be a sound and stable language one day, a
language they can use for loads of stuff, while th
On Monday, 3 September 2018 at 18:52:45 UTC, Laurent Tréguier
wrote:
On Monday, 3 September 2018 at 18:26:57 UTC, Chris wrote:
it should come with a warning label that says "D is in many
parts still at an experimental stage and ships with no
guarantees whatsoever. Use at your own risk."
Well
On Monday, September 3, 2018 12:26:57 PM MDT Chris via Digitalmars-d wrote:
> There is no real plan and
> only problems that someone deems interesting or challenging at a
> given moment are tackled. If they solve a problem for a lot of
> users, it's only a side effect. The advent of a D Foundation
On Monday, 3 September 2018 at 14:26:46 UTC, Laeeth Isharc wrote:
I just spoke with Dicebot about work stuff. He incidentally
mentioned what I said before based on my impressions. The
people doing work with a language have better things to do than
spend a lot of time on forums. And I think i
On Monday, 3 September 2018 at 14:26:46 UTC, Laeeth Isharc wrote:
I just spoke with Dicebot about work stuff. He incidentally
mentioned what I said before based on my impressions. The
people doing work with a language have better things to do than
spend a lot of time on forums. And I think
On Monday, 3 September 2018 at 18:26:57 UTC, Chris wrote:
it should come with a warning label that says "D is in many
parts still at an experimental stage and ships with no
guarantees whatsoever. Use at your own risk."
Well it comes with the Boost license that says: `THE SOFTWARE IS
PROVIDED
On Monday, 3 September 2018 at 16:55:10 UTC, Jonathan M Davis
wrote:
Most of the work that gets done is the stuff that the folks
contributing think is the most important - frequently what is
most important for them for what they do, and very few (if any)
of the major contributors use or care
On Monday, September 3, 2018 11:15:03 AM MDT Laurent Tréguier via
Digitalmars-d wrote:
> It just baffles me a bit to see the state of D in this
> department, when languages like Go or Rust (hooray for yet
> another comparison to Go and Rust) are a lot younger, but already
> have what looks like ve
On Monday, 3 September 2018 at 16:55:10 UTC, Jonathan M Davis
wrote:
Most of the work that gets done is the stuff that the folks
contributing think is the most important - frequently what is
most important for them for what they do, and very few (if any)
of the major contributors use or care ab
On Monday, September 3, 2018 9:41:48 AM MDT Laurent Tréguier via
Digitalmars-d wrote:
> On Monday, 3 September 2018 at 15:23:12 UTC, Chris wrote:
> > On Monday, 3 September 2018 at 14:26:46 UTC, Laeeth Isharc
> >
> > wrote:
> >> On Monday, 3 September 2018 at 11:32:42 UTC, Chris wrote:
> >>> [...]
On 3 September 2018 at 18:07, RhyS via Digitalmars-d
wrote:
>
> Too much resources split among too many distributions, graphical desktops
> etc. Choice is good but too much choice means projects are starved for
> resources, comparability are issues, bugs are even more present, ...
>
> A good examp
On Monday, 3 September 2018 at 15:41:48 UTC, Laurent Tréguier
wrote:
Yes. It almost sounds like a smooth experience would be a bad
thing to have, especially with the classic "you don't need an
IDE anyway" speech. Editing experience seems often dismissed as
unimportant, when it's one of the firs
On Monday, 3 September 2018 at 15:23:12 UTC, Chris wrote:
On Monday, 3 September 2018 at 14:26:46 UTC, Laeeth Isharc
wrote:
On Monday, 3 September 2018 at 11:32:42 UTC, Chris wrote:
[...]
D has never been about smooth experiences! That's a
commercial benefit if you think that hormesis b
On Monday, 3 September 2018 at 14:26:46 UTC, Laeeth Isharc wrote:
On Monday, 3 September 2018 at 11:32:42 UTC, Chris wrote:
[...]
D has never been about smooth experiences! That's a commercial
benefit if you think that hormesis brings benefits and you are
not looking for programmers of
On Monday, 3 September 2018 at 11:32:42 UTC, Chris wrote:
On Sunday, 2 September 2018 at 12:07:17 UTC, Laeeth Isharc
wrote:
That's why the people that adopt D will inordinately be
principals not agents in the beginning. They will either be
residual claimants on earnings or will have acquire
On Monday, 3 September 2018 at 11:32:42 UTC, Chris wrote:
On Sunday, 2 September 2018 at 12:07:17 UTC, Laeeth Isharc
wrote:
That's why the people that adopt D will inordinately be
principals not agents in the beginning. They will either be
residual claimants on earnings or will have acquire
On Monday, 3 September 2018 at 06:29:02 UTC, Pjotr Prins wrote:
One thing I want to add that we ought to be appreciative of the
work people put in - much of it in their spare time. I wonder
if W&A and others sometimes despair for the lack of
appreciation they get. Guido van Rossum burning out (
On Monday, 3 September 2018 at 06:29:02 UTC, Pjotr Prins wrote:
Hear, hear!
Even though some languages like Julia, Rust and Go are much
better funded than D - and their creators have excellent taste
in different ways - they still have to go through similar
evolutionary steps. There is no fas
On Sunday, 2 September 2018 at 12:07:17 UTC, Laeeth Isharc wrote:
That's why the people that adopt D will inordinately be
principals not agents in the beginning. They will either be
residual claimants on earnings or will have acquired the
authority to make decisions without persuading a comm
On Sunday, 2 September 2018 at 12:07:17 UTC, Laeeth Isharc wrote:
I've only been programming since 1983 so I had the benefit of
high level languages like BBC BASIC, C, a Forth I wrote myself,
and Modula 3. And although I had to write a disassembler at
least I has assemblers built in. Programm
On Sunday, 2 September 2018 at 14:48:34 UTC, lurker wrote:
after the beta i tried it the final again - just to be fair.
1.) install d, install visual d.
2.) trying to to look at options under visual d without a
project crashes VS2017 - latest
service pack.
3.) VS2017 - displays a problem o
On Sunday, 2 September 2018 at 14:48:34 UTC, lurker wrote:
after the beta i tried it the final again - just to be fair.
1.) install d, install visual d.
2.) trying to to look at options under visual d without a
project crashes VS2017 - latest
service pack.
3.) VS2017 - displays a problem o
On Sun, 2 Sep 2018 at 16:05, Andre Pany via Digitalmars-d
wrote:
>
> On Sunday, 2 September 2018 at 14:48:34 UTC, lurker wrote:
> > after the beta i tried it the final again - just to be fair.
> >
> > 1.) install d, install visual d.
> > 2.) trying to to look at options under visual d without a
>
On Sunday, 2 September 2018 at 14:48:34 UTC, lurker wrote:
after the beta i tried it the final again - just to be fair.
1.) install d, install visual d.
2.) trying to to look at options under visual d without a
project crashes VS2017 - latest
service pack.
3.) VS2017 - displays a problem o
On Sunday, 2 September 2018 at 14:48:34 UTC, lurker wrote:
after the beta i tried it the final again - just to be fair.
1.) install d, install visual d.
2.) trying to to look at options under visual d without a
project crashes VS2017 - latest
service pack.
3.) VS2017 - displays a problem o
after the beta i tried it the final again - just to be fair.
1.) install d, install visual d.
2.) trying to to look at options under visual d without a project
crashes VS2017 - latest
service pack.
3.) VS2017 - displays a problem on startup
4.) creating the dummy project - compile for x64.
On Saturday, 1 September 2018 at 12:33:49 UTC, rjframe wrote:
On Thu, 23 Aug 2018 15:35:45 +, Joakim wrote:
* Language complexity
Raise your hand if you know how a class with both opApply and
the
get/next/end functions behaves when you pass it to foreach.
How about a struct? Does it matt
On Saturday, 1 September 2018 at 18:35:30 UTC,
TheSixMillionDollarMan wrote:
On Saturday, 1 September 2018 at 12:33:49 UTC, rjframe wrote:
[...]
Stroustrup also said, that "achieving any degree of
compatibility [with C/C++] is very hard, as the C/C++
experience shows."
(reference => http:/
On Saturday, 1 September 2018 at 21:18:27 UTC, Nick Sabalausky
(Abscissa) wrote:
On 09/01/2018 07:12 AM, Chris wrote:
Hope is usually the last thing to die. But one has to be wise
enough to see that sometimes there is nothing one can do. As
things are now, for me personally D is no longer an
On 09/01/2018 07:12 AM, Chris wrote:
Hope is usually the last thing to die. But one has to be wise enough to
see that sometimes there is nothing one can do. As things are now, for
me personally D is no longer an option, because of simple basic things,
like autodecode, a flaw that will be ther
On Saturday, 1 September 2018 at 12:33:49 UTC, rjframe wrote:
C++ is sometimes used for projects in which Stroustrup would
say it's obviously the wrong language for the job.
D is far more likely to require justification based on
technical merit. If D becomes another C++, why bother taking a
c
On Thu, 23 Aug 2018 14:29:23 +, bachmeier wrote:
> Weka is an awesome project, but I don't know that most people
> considering D should use your experience as the basis of their decision.
> At least in my areas, I expect considerable growth in the usage of D
> over the next 10 years. Maybe it
On Thu, 23 Aug 2018 15:35:45 +, Joakim wrote:
>> * Language complexity
>>
>> Raise your hand if you know how a class with both opApply and the
>> get/next/end functions behaves when you pass it to foreach.
>> How about a struct? Does it matter if it allows copying or not?
>>
>> The language wa
1 - 100 of 332 matches
Mail list logo
