Re: Why not flag away the mistakes of the past?

2018-03-09 Thread Chris via Digitalmars-d
#x27;m willing to try it on my code (that is almost 100% string processing). Why not _try_ it, later we can still philosophize

Re: Why not flag away the mistakes of the past?

2018-03-09 Thread Gary Willoughby via Digitalmars-d
On Wednesday, 7 March 2018 at 17:11:55 UTC, H. S. Teoh wrote: Kill autodecoding, I say. Kill it with fire!! T Please!!!

Re: Why not flag away the mistakes of the past?

2018-03-09 Thread Guillaume Piolat via Digitalmars-d
On Thursday, 8 March 2018 at 17:35:11 UTC, H. S. Teoh wrote: Yeah, the only reason autodecoding survived in the beginning was because Andrei (wrongly) thought that a Unicode code point was equivalent to a grapheme. If that had been the case, the cost associated with auto-decoding may have been

Re: Why not flag away the mistakes of the past?

2018-03-08 Thread Jonathan M Davis via Digitalmars-d
On Friday, March 09, 2018 03:16:03 Taylor Hillegeist via Digitalmars-d wrote: > I wasn't so much asking about auto-decoding in particular more > about the mentality and methods of breaking changes. > > In a way any change to the compiler is a breaking change when it > comes to the configuration.

Re: Why not flag away the mistakes of the past?

2018-03-08 Thread Taylor Hillegeist via Digitalmars-d
On Thursday, 8 March 2018 at 17:14:16 UTC, Jonathan M Davis wrote: On Thursday, March 08, 2018 16:34:11 Guillaume Piolat via Digitalmars-d wrote: On Wednesday, 7 March 2018 at 13:24:25 UTC, Jonathan M Davis wrote: > On Wednesday, March 07, 2018 12:53:16 Guillaume Piolat via > > Digitalmars-d wr

Re: Why not flag away the mistakes of the past?

2018-03-08 Thread Henrik via Digitalmars-d
On Thursday, 8 March 2018 at 17:35:11 UTC, H. S. Teoh wrote: On Thu, Mar 08, 2018 at 10:14:16AM -0700, Jonathan M Davis via Digitalmars-d wrote: [...] [...] [...] [...] Yeah, the only reason autodecoding survived in the beginning was because Andrei (wrongly) thought that a Unicode code poin

Re: Why not flag away the mistakes of the past?

2018-03-08 Thread H. S. Teoh via Digitalmars-d
On Thu, Mar 08, 2018 at 10:14:16AM -0700, Jonathan M Davis via Digitalmars-d wrote: > On Thursday, March 08, 2018 16:34:11 Guillaume Piolat via Digitalmars-d > wrote: [...] > > I'd agree with you, hate the special casing. However it seems to > > me this has been debated to death already, and that

Re: Why not flag away the mistakes of the past?

2018-03-08 Thread Jonathan M Davis via Digitalmars-d
On Thursday, March 08, 2018 16:34:11 Guillaume Piolat via Digitalmars-d wrote: > On Wednesday, 7 March 2018 at 13:24:25 UTC, Jonathan M Davis > > wrote: > > On Wednesday, March 07, 2018 12:53:16 Guillaume Piolat via > > > > Digitalmars-d wrote: > >> On Wednesday, 7 March 2018 at 06:00:30 UTC, Tayl

Re: Why not flag away the mistakes of the past?

2018-03-08 Thread Guillaume Piolat via Digitalmars-d
On Wednesday, 7 March 2018 at 13:24:25 UTC, Jonathan M Davis wrote: On Wednesday, March 07, 2018 12:53:16 Guillaume Piolat via Digitalmars-d wrote: On Wednesday, 7 March 2018 at 06:00:30 UTC, Taylor Hillegeist wrote: > That way the breaking change was easily fixable, and the > mistakes of the

Re: Why not flag away the mistakes of the past?

2018-03-08 Thread Dukc via Digitalmars-d
On Wednesday, 7 March 2018 at 16:29:33 UTC, Seb wrote: Well, I tried that already: https://github.com/dlang/phobos/pull/5513 In short: very easy to do, but not much interest at the time. No. The main problem with that (and the idea of using a compiler flag in general) is that it affects the

Re: why not use git rebase instead of git merge in dlang repos?

2018-03-07 Thread timotheecour via Digitalmars-d
On Wednesday, 7 March 2018 at 22:28:26 UTC, ketmar wrote: H. S. Teoh wrote: I've pestered Brad about it before, but the real trouble is the Mailman software. If you feel motivated enough, pestering the upstream Mailman authors about it might actually get us closer to fixing this problem, as

Re: why not use git rebase instead of git merge in dlang repos?

2018-03-07 Thread ketmar via Digitalmars-d
H. S. Teoh wrote: I've pestered Brad about it before, but the real trouble is the Mailman software. If you feel motivated enough, pestering the upstream Mailman authors about it might actually get us closer to fixing this problem, as it really isn't a problem on Brad's end either. It's not unfi

Re: why not use git rebase instead of git merge in dlang repos?

2018-03-07 Thread H. S. Teoh via Digitalmars-d
On Thu, Mar 08, 2018 at 12:10:28AM +0200, ketmar via Digitalmars-d wrote: > Seb wrote: > > > OT: I don't know what you are doing, but you seem to be the only one > > who always creates new threads when replying. I assume you use nntp? > > Maybe something wrong with your client? > > it was already

Re: why not use git rebase instead of git merge in dlang repos?

2018-03-07 Thread ketmar via Digitalmars-d
Seb wrote: OT: I don't know what you are doing, but you seem to be the only one who always creates new threads when replying. I assume you use nntp? Maybe something wrong with your client? it was already discussed several times: this is the issue with mailing list processor: it cannot proper

Re: why not use git rebase instead of git merge in dlang repos?

2018-03-07 Thread Seb via Digitalmars-d
On Wednesday, 7 March 2018 at 21:03:52 UTC, H. S. Teoh wrote: On Wed, Mar 07, 2018 at 12:42:52PM -0800, Timothee Cour via Digitalmars-d wrote: [...] On the contrary, I find using merge is easier to understand, because it shows clearly individual commits within a single PR, and also a linear

Re: why not use git rebase instead of git merge in dlang repos?

2018-03-07 Thread H. S. Teoh via Digitalmars-d
On Wed, Mar 07, 2018 at 12:42:52PM -0800, Timothee Cour via Digitalmars-d wrote: > There are lots of articles on this topic, eg: > https://blog.carbonfive.com/2017/08/28/always-squash-and-rebase-your-git-commits/ > (note that squashing down to 1 commit shouldn't be necessary but at > least rebasing

why not use git rebase instead of git merge in dlang repos?

2018-03-07 Thread Timothee Cour via Digitalmars-d
There are lots of articles on this topic, eg: https://blog.carbonfive.com/2017/08/28/always-squash-and-rebase-your-git-commits/ (note that squashing down to 1 commit shouldn't be necessary but at least rebasing should be done) github UI also allows to rebase (instead of merge) would really simpli

Re: Why not flag away the mistakes of the past?

2018-03-07 Thread Jon Degenhardt via Digitalmars-d
On Wednesday, 7 March 2018 at 16:33:25 UTC, Seb wrote: On Wednesday, 7 March 2018 at 15:26:40 UTC, Jon Degenhardt wrote: On Wednesday, 7 March 2018 at 06:00:30 UTC, Taylor Hillegeist wrote: [...] Auto-decoding is a significant issue for the applications I work on (search engines). There is a

Re: Why not flag away the mistakes of the past?

2018-03-07 Thread H. S. Teoh via Digitalmars-d
On Wed, Mar 07, 2018 at 04:29:33PM +, Seb via Digitalmars-d wrote: > On Wednesday, 7 March 2018 at 14:59:35 UTC, Steven Schveighoffer wrote: > > On 3/7/18 1:00 AM, Taylor Hillegeist wrote: > > > [...] > > > > Note, autodecoding is NOT a feature of the language, but rather a > > feature of Phob

Re: Why not flag away the mistakes of the past?

2018-03-07 Thread H. S. Teoh via Digitalmars-d
On Wed, Mar 07, 2018 at 04:33:25PM +, Seb via Digitalmars-d wrote: > On Wednesday, 7 March 2018 at 15:26:40 UTC, Jon Degenhardt wrote: [...] > > Auto-decoding is a significant issue for the applications I work on > > (search engines). There is a lot of string manipulation in these > > environme

Re: Why not flag away the mistakes of the past?

2018-03-07 Thread Seb via Digitalmars-d
On Wednesday, 7 March 2018 at 15:26:40 UTC, Jon Degenhardt wrote: On Wednesday, 7 March 2018 at 06:00:30 UTC, Taylor Hillegeist wrote: [...] Auto-decoding is a significant issue for the applications I work on (search engines). There is a lot of string manipulation in these environments, and

Re: Why not flag away the mistakes of the past?

2018-03-07 Thread Seb via Digitalmars-d
On Wednesday, 7 March 2018 at 14:59:35 UTC, Steven Schveighoffer wrote: On 3/7/18 1:00 AM, Taylor Hillegeist wrote: [...] Note, autodecoding is NOT a feature of the language, but rather a feature of Phobos. It would be quite interesting I think to create a modified phobos where autodecodin

Re: Why not flag away the mistakes of the past?

2018-03-07 Thread Jon Degenhardt via Digitalmars-d
And I always wonder why not make a solution to the tune of a flag that makes things work as they used too, and make the new behavior default. dmd --UseAutoDecoding That way the breaking change was easily fixable, and the mistakes of the past not forever. Is it just the cost of maintenance?

Re: Why not flag away the mistakes of the past?

2018-03-07 Thread Steven Schveighoffer via Digitalmars-d
On 3/7/18 1:00 AM, Taylor Hillegeist wrote: So i've seen on the forum over the years arguments about auto-decoding (mostly) and some other things. Things that have been considered mistakes, and cannot be corrected because of the breaking changes it would create. And I always wonder wh

Re: Why not flag away the mistakes of the past?

2018-03-07 Thread Jonathan M Davis via Digitalmars-d
On Wednesday, March 07, 2018 13:40:20 Nick Treleaven via Digitalmars-d wrote: > On Wednesday, 7 March 2018 at 13:24:25 UTC, Jonathan M Davis > > wrote: > > I'd actually argue that that's the lesser of the problems with > > auto-decoding. The big problem is that it's auto-decoding. Code > > points

Re: Why not flag away the mistakes of the past?

2018-03-07 Thread Nick Treleaven via Digitalmars-d
On Wednesday, 7 March 2018 at 13:24:25 UTC, Jonathan M Davis wrote: I'd actually argue that that's the lesser of the problems with auto-decoding. The big problem is that it's auto-decoding. Code points are almost always the wrong level to be operating at. For me the fundamental problem is havi

Re: Why not flag away the mistakes of the past?

2018-03-07 Thread Jonathan M Davis via Digitalmars-d
On Wednesday, March 07, 2018 12:53:16 Guillaume Piolat via Digitalmars-d wrote: > On Wednesday, 7 March 2018 at 06:00:30 UTC, Taylor Hillegeist > > wrote: > > That way the breaking change was easily fixable, and the > > mistakes of the past not forever. Is it just the cost of > > maintenance? > >

Re: Why not flag away the mistakes of the past?

2018-03-07 Thread Guillaume Piolat via Digitalmars-d
On Wednesday, 7 March 2018 at 06:00:30 UTC, Taylor Hillegeist wrote: That way the breaking change was easily fixable, and the mistakes of the past not forever. Is it just the cost of maintenance? auto-decoding problem was mostly that it couldn't be @nogc since throwing, but with further relea

Re: Why not flag away the mistakes of the past?

2018-03-07 Thread jmh530 via Digitalmars-d
And I always wonder why not make a solution to the tune of a flag that makes things work as they used too, and make the new behavior default. dmd --UseAutoDecoding That way the breaking change was easily fixable, and the mistakes of the past not forever. Is it just the cost of maintenance? T

Re: Why not flag away the mistakes of the past?

2018-03-07 Thread FeepingCreature via Digitalmars-d
For what it's worth, I like autodecoding. I worry we could be in a situation where a moderate number of people are strong opponents and a lot of people are weak fans, none of which individually care enough to post. Hopefully the D survey results will shed some light on this, though I don't re

Why not flag away the mistakes of the past?

2018-03-06 Thread Taylor Hillegeist via Digitalmars-d
So i've seen on the forum over the years arguments about auto-decoding (mostly) and some other things. Things that have been considered mistakes, and cannot be corrected because of the breaking changes it would create. And I always wonder why not make a solution to the tune of a flag

Re: dmd: why not use fully qualified names for types in error messages?

2017-06-14 Thread Jonathan M Davis via Digitalmars-d
On Wednesday, June 14, 2017 08:33:26 Jacob Carlborg via Digitalmars-d wrote: > On 2017-06-14 06:50, Timothee Cour via Digitalmars-d wrote: > > eg: > > Error: no property 'IF_gray' for type 'ImageFormat' > > => > > Error: no property 'IF_gra

Re: dmd: why not use fully qualified names for types in error messages?

2017-06-14 Thread Daniel Kozak via Digitalmars-d
> On Wednesday, 14 June 2017 at 06:33:26 UTC, Jacob Carlborg wrote: > >> On 2017-06-14 06:50, Timothee Cour via Digitalmars-d wrote: >> >>> eg: >>> Error: no property 'IF_gray' for type 'ImageFormat' >>> => >>> Error: no propert

Re: dmd: why not use fully qualified names for types in error messages?

2017-06-14 Thread Nicholas Wilson via Digitalmars-d
On Wednesday, 14 June 2017 at 06:33:26 UTC, Jacob Carlborg wrote: On 2017-06-14 06:50, Timothee Cour via Digitalmars-d wrote: eg: Error: no property 'IF_gray' for type 'ImageFormat' => Error: no property 'IF_gray' for type 'foo.bar.ImageFormat'

Re: dmd: why not use fully qualified names for types in error messages?

2017-06-13 Thread Jacob Carlborg via Digitalmars-d
On 2017-06-14 06:50, Timothee Cour via Digitalmars-d wrote: eg: Error: no property 'IF_gray' for type 'ImageFormat' => Error: no property 'IF_gray' for type 'foo.bar.ImageFormat' and also, why not show where the symbol is defined? would PR's

Re: dmd: why not use fully qualified names for types in error messages?

2017-06-13 Thread H. S. Teoh via Digitalmars-d
here an issue filed in bugzilla for this? I'd add that this would be very useful with Voldemort types, esp. Phobos ones that are generally just named "Result". > and also, why not show where the symbol is defined? Might not be a bad idea, if you're dealing with overloads

dmd: why not use fully qualified names for types in error messages?

2017-06-13 Thread Timothee Cour via Digitalmars-d
eg: Error: no property 'IF_gray' for type 'ImageFormat' => Error: no property 'IF_gray' for type 'foo.bar.ImageFormat' and also, why not show where the symbol is defined? would PR's for that be accepted? is that hard to implement?

Re: Why not promoting team work?

2017-01-17 Thread solidstate1991 via Digitalmars-d
On Saturday, 14 January 2017 at 02:28:34 UTC, nbro wrote: Hi! I've been following D for at least one year. I like it and I think it's a very good programming language, even though I do not agree with everything it's being done. One thing that has saddened me is seeing a lot of D's users try

Re: Why not promoting team work?

2017-01-17 Thread Satoshi via Digitalmars-d
On Saturday, 14 January 2017 at 03:05:44 UTC, nbro wrote: On Saturday, 14 January 2017 at 02:57:05 UTC, ketmar wrote: On Saturday, 14 January 2017 at 02:28:34 UTC, nbro wrote: How could you do such a thing? freakin' easy: just pay people to do what you want. either that, or people will keep

Re: Why not promoting team work?

2017-01-17 Thread aberba via Digitalmars-d
On Saturday, 14 January 2017 at 03:26:40 UTC, ketmar wrote: On Saturday, 14 January 2017 at 03:05:44 UTC, nbro wrote: On Saturday, 14 January 2017 at 02:57:05 UTC, ketmar wrote: [...] Serious users, to whom I'm directing this post, who really believe in D's potential, should try to collabora

Re: Why not promoting team work?

2017-01-17 Thread strymon via Digitalmars-d
On Tuesday, 17 January 2017 at 12:45:09 UTC, rikki cattermole wrote: Ironically I wrote the only (e)book on CTFE[0]. Its a bit out of date and needs some work, but if you want to give me some feedback please email me and I'll get you a coupon (free). [0] https://leanpub.com/ctfe Thanks, I

Re: Why not promoting team work?

2017-01-17 Thread rikki cattermole via Digitalmars-d
On 18/01/2017 12:38 AM, strymon wrote: On Saturday, 14 January 2017 at 02:28:34 UTC, nbro wrote: Hi! I've been following D for at least one year. I like it and I think it's a very good programming language, even though I do not agree with everything it's being done. One thing that has saddened

Re: Why not promoting team work?

2017-01-17 Thread strymon via Digitalmars-d
On Saturday, 14 January 2017 at 02:28:34 UTC, nbro wrote: Hi! I've been following D for at least one year. I like it and I think it's a very good programming language, even though I do not agree with everything it's being done. One thing that has saddened me is seeing a lot of D's users try

Re: Why not promoting team work?

2017-01-17 Thread Chris via Digitalmars-d
On Saturday, 14 January 2017 at 02:28:34 UTC, nbro wrote: Hi! I've been following D for at least one year. I like it and I think it's a very good programming language, even though I do not agree with everything it's being done. One thing that has saddened me is seeing a lot of D's users try

Re: Why not promoting team work?

2017-01-16 Thread Jerry via Digitalmars-d
On Saturday, 14 January 2017 at 02:28:34 UTC, nbro wrote: These could be a few starting ideas and options. To me it sounds like we need better ways of programmers to connect with eachother and discuss. Maybe a library subforum or something?

Re: Why not promoting team work?

2017-01-14 Thread rikki cattermole via Digitalmars-d
On 15/01/2017 12:38 AM, nbro wrote: Nobody has understood yet the goal of this post. I'm not saying that everybody should work in a team or shouldn't try to create what one needs, if there isn't a better alternative. I'm suggesting that for a few interesting, useful and possibly valuable projec

Re: Why not promoting team work?

2017-01-14 Thread nbro via Digitalmars-d
Nobody has understood yet the goal of this post. I'm not saying that everybody should work in a team or shouldn't try to create what one needs, if there isn't a better alternative. I'm suggesting that for a few interesting, useful and possibly valuable projects, before they start (but eventua

Re: Why not promoting team work?

2017-01-13 Thread Chris Wright via Digitalmars-d
I tend to see projects in one of three states: 1. It doesn't exist. 2. It exists, but the last update was six months ago and it's broken. 3. It exists, does what I want, and I can use it with at most small workarounds. If it doesn't exist, I have to make it myself. If it's broken and apparently

Re: Why not promoting team work?

2017-01-13 Thread rikki cattermole via Digitalmars-d
On 14/01/2017 3:59 PM, nbro wrote: On Saturday, 14 January 2017 at 02:41:00 UTC, rikki cattermole wrote: The only way to get qualified to do these tasks like GUI toolkits is by doing. Keep this in mind. As somebody who does indeed do implement multiple libraries at one time you're looking at it

Re: Why not promoting team work?

2017-01-13 Thread ketmar via Digitalmars-d
On Saturday, 14 January 2017 at 03:05:44 UTC, nbro wrote: On Saturday, 14 January 2017 at 02:57:05 UTC, ketmar wrote: On Saturday, 14 January 2017 at 02:28:34 UTC, nbro wrote: How could you do such a thing? freakin' easy: just pay people to do what you want. either that, or people will keep

Re: Why not promoting team work?

2017-01-13 Thread nbro via Digitalmars-d
On Saturday, 14 January 2017 at 02:57:05 UTC, ketmar wrote: On Saturday, 14 January 2017 at 02:28:34 UTC, nbro wrote: How could you do such a thing? freakin' easy: just pay people to do what you want. either that, or people will keep working on the things *they* are interested (and not someo

Re: Why not promoting team work?

2017-01-13 Thread nbro via Digitalmars-d
On Saturday, 14 January 2017 at 02:41:00 UTC, rikki cattermole wrote: The only way to get qualified to do these tasks like GUI toolkits is by doing. Keep this in mind. As somebody who does indeed do implement multiple libraries at one time you're looking at it the wrong way. I switch between

Re: Why not promoting team work?

2017-01-13 Thread ketmar via Digitalmars-d
On Saturday, 14 January 2017 at 02:28:34 UTC, nbro wrote: How could you do such a thing? freakin' easy: just pay people to do what you want. either that, or people will keep working on the things *they* are interested (and not someone else).

Re: Why not promoting team work?

2017-01-13 Thread rikki cattermole via Digitalmars-d
The only way to get qualified to do these tasks like GUI toolkits is by doing. Keep this in mind. As somebody who does indeed do implement multiple libraries at one time you're looking at it the wrong way. I switch between projects over periods that last for years not days or weeks. The point

Why not promoting team work?

2017-01-13 Thread nbro via Digitalmars-d
Hi! I've been following D for at least one year. I like it and I think it's a very good programming language, even though I do not agree with everything it's being done. One thing that has saddened me is seeing a lot of D's users trying to implement their own library or maybe trying to impl

Re: Why not use the address of the TypeInfo symbol as TypeInfo.toHash()?

2016-03-03 Thread Yuxuan Shui via Digitalmars-d
On Friday, 4 March 2016 at 00:42:28 UTC, Walter Bright wrote: On 3/3/2016 4:29 PM, Yuxuan Shui wrote: After linking each _DxxTypeInfo___initZ symbol should have a unique address, so why are we using hash of type name as TypeInfo.toHash()? I don't think this has anything to do with compactin

Re: Why not use the address of the TypeInfo symbol as TypeInfo.toHash()?

2016-03-03 Thread Walter Bright via Digitalmars-d
On 3/3/2016 4:29 PM, Yuxuan Shui wrote: After linking each _DxxTypeInfo___initZ symbol should have a unique address, so why are we using hash of type name as TypeInfo.toHash()? I don't think this has anything to do with compacting GC. Is there something I'm missing? Because when working wit

Why not use the address of the TypeInfo symbol as TypeInfo.toHash()?

2016-03-03 Thread Yuxuan Shui via Digitalmars-d
After linking each _DxxTypeInfo___initZ symbol should have a unique address, so why are we using hash of type name as TypeInfo.toHash()? I don't think this has anything to do with compacting GC. Is there something I'm missing?

Why not run external DLL code at compile time?

2016-01-07 Thread Luke via Digitalmars-d
an expert on make/cmake/etc. but they certainly also allow calling out to executables on the system. So maybe the current compilers themselves, gcc / cl / etc. don't leave you with that security question in your head, but pretty much nothing you build from github etc. these days is pure comp

Re: Constructor inheritance? Why not?

2015-06-08 Thread Kapps via Digitalmars-d
On Monday, 8 June 2015 at 02:39:22 UTC, Tofu Ninja wrote: Is there any reason why constructors are not inherited? All other methods are inherited, why not constructors? It should be relatively easy to do this with a mixin in theory. Or even a CtorArgsTuple, allowing something like (not

Re: Constructor inheritance? Why not?

2015-06-08 Thread Paulo Pinto via Digitalmars-d
On Monday, 8 June 2015 at 09:20:06 UTC, Ola Fosheim Grøstad wrote: On Monday, 8 June 2015 at 06:35:33 UTC, Jonathan M Davis wrote: On Monday, 8 June 2015 at 06:04:23 UTC, Tofu Ninja wrote: No its definitely not something that alot of people seem to care about, but I always found it odd that con

Re: Constructor inheritance? Why not?

2015-06-08 Thread via Digitalmars-d
On Monday, 8 June 2015 at 09:20:06 UTC, Ola Fosheim Grøstad wrote: They can if you use type variables. Type variables can be virtual too. And IIRC you can emulate type variables in D too if you dig into RTTI, but I don't quite remember where I found that. I am sure you know how to do it. IIRC

Re: Constructor inheritance? Why not?

2015-06-08 Thread via Digitalmars-d
On Monday, 8 June 2015 at 06:35:33 UTC, Jonathan M Davis wrote: On Monday, 8 June 2015 at 06:04:23 UTC, Tofu Ninja wrote: No its definitely not something that alot of people seem to care about, but I always found it odd that constructors get certain special casing like this. I expect that it

Re: Constructor inheritance? Why not?

2015-06-08 Thread Tofu Ninja via Digitalmars-d
On Monday, 8 June 2015 at 06:35:33 UTC, Jonathan M Davis wrote: On Monday, 8 June 2015 at 06:04:23 UTC, Tofu Ninja wrote: No its definitely not something that alot of people seem to care about, but I always found it odd that constructors get certain special casing like this. I expect that it

Re: Constructor inheritance? Why not?

2015-06-08 Thread Shachar Shemesh via Digitalmars-d
On 08/06/15 06:35, Jonathan M Davis wrote: They're not polymorphic, and it doesn't make sense to call a base class constructor on a derived class. I think that I heard somewhere that C++11 added some sort of constructor inheritance No, it didn't. What C++11 added was the ability to use the imp

Re: Constructor inheritance? Why not?

2015-06-07 Thread Jonathan M Davis via Digitalmars-d
On Monday, 8 June 2015 at 06:04:23 UTC, Tofu Ninja wrote: No its definitely not something that alot of people seem to care about, but I always found it odd that constructors get certain special casing like this. I expect that it originally comes down to the fact that constructors aren't polym

Re: Constructor inheritance? Why not?

2015-06-07 Thread Tofu Ninja via Digitalmars-d
On Monday, 8 June 2015 at 04:32:41 UTC, Jonathan M Davis wrote: In most cases, you need to create a new constructor, because it's a different type with different data, even if some of the constructor parameters might be the same. Exceptions are a rare case where the constructors are frequently

Re: Constructor inheritance? Why not?

2015-06-07 Thread Atila Neves via Digitalmars-d
On Monday, 8 June 2015 at 03:35:52 UTC, Jonathan M Davis wrote: On Monday, 8 June 2015 at 02:39:22 UTC, Tofu Ninja wrote: Is there any reason why constructors are not inherited? All other methods are inherited, why not constructors? They're not polymorphic, and it doesn't make sense

Re: Constructor inheritance? Why not?

2015-06-07 Thread Jonathan M Davis via Digitalmars-d
On Monday, 8 June 2015 at 04:16:14 UTC, Tofu Ninja wrote: Their are plenty of examples where you would want a constructor to be inherited, exceptions being a good one. Currently if you have a base class with a constructor that you want all the sub classes to have as well, you simply have to jus

Re: Constructor inheritance? Why not?

2015-06-07 Thread Tofu Ninja via Digitalmars-d
On Monday, 8 June 2015 at 03:35:52 UTC, Jonathan M Davis wrote: On Monday, 8 June 2015 at 02:39:22 UTC, Tofu Ninja wrote: Is there any reason why constructors are not inherited? All other methods are inherited, why not constructors? They're not polymorphic, and it doesn't make sense

Re: Constructor inheritance? Why not?

2015-06-07 Thread Jonathan M Davis via Digitalmars-d
On Monday, 8 June 2015 at 02:39:22 UTC, Tofu Ninja wrote: Is there any reason why constructors are not inherited? All other methods are inherited, why not constructors? They're not polymorphic, and it doesn't make sense to call a base class constructor on a derived class. I think th

Constructor inheritance? Why not?

2015-06-07 Thread Tofu Ninja via Digitalmars-d
Is there any reason why constructors are not inherited? All other methods are inherited, why not constructors?

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-22 Thread Steven Schveighoffer via Digitalmars-d
On 1/22/15 12:03 PM, Walter Bright wrote: On 1/22/2015 4:44 AM, Steven Schveighoffer wrote: But I am surprised MS does not have some way to get reasonable paid support for their software. Apple gives you 1 year free software/hardware support when you buy a Mac. I can fully understand not offerin

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-22 Thread Walter Bright via Digitalmars-d
On 1/22/2015 4:44 AM, Steven Schveighoffer wrote: But I am surprised MS does not have some way to get reasonable paid support for their software. Apple gives you 1 year free software/hardware support when you buy a Mac. I can fully understand not offering "Free" support. Not everyone is a Walter

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-22 Thread Steven Schveighoffer via Digitalmars-d
On 1/21/15 1:39 PM, Walter Bright wrote: On 1/21/2015 8:23 AM, ketmar via Digitalmars-d wrote: this simply not work. Neither does Windows Moviemaker. It hung again on me. Just FYI iMovie works just fine ;) and not worth it. WMM is over a decade old, and it still hangs doing something as

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-22 Thread Kagamin via Digitalmars-d
On Wednesday, 21 January 2015 at 08:41:47 UTC, Walter Bright wrote: I wonder why software companies still make it impossible to submit bug reports. For example, google: "submit windows movie maker bug report" Click on "Reporting and solving computer problems - Windows": http://windows.microso

Re: Like Go/Rust, why not to have "func" keyword before function declaration

2015-01-21 Thread Danni Coy via Digitalmars-d
regular expression search FunctionName.*\{ or FunctionName.*$\s*\{ depending on brace style On Wed, Jan 21, 2015 at 4:37 AM, Joakim via Digitalmars-d wrote: > On Tuesday, 20 January 2015 at 00:13:37 UTC, Brian Schott wrote: >> >> On Monday, 19 January 2015 at 22:49:41 UTC, Ary Borenszweig wrote:

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread Walter Bright via Digitalmars-d
On 1/21/2015 11:03 AM, Brad Roberts via Digitalmars-d wrote: I'll note, for what it's worth, that there's open bug reports against D that are almost 9 years old... oldest open bug was filed in May of 2006. Some of them fairly fundamental. All software has bugs. But trimming a video is the most

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread Walter Bright via Digitalmars-d
On 1/21/2015 10:53 AM, Andrei Alexandrescu wrote: On 1/21/15 10:45 AM, Walter Bright wrote: It left such bad taste I was unwilling to try it again until recently. I'm disgusted that the problems remain. How hard can it be? "10 years is a long time" -- Andrei Right, which is why I'm disgusted

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread Brad Roberts via Digitalmars-d
On 1/21/2015 10:53 AM, Andrei Alexandrescu via Digitalmars-d wrote: On 1/21/15 10:45 AM, Walter Bright wrote: On 1/21/2015 7:40 AM, Andrei Alexandrescu wrote: there's plenty of video processing software in the free world. About 10 years ago, I needed to edit a movie. I downloaded about 10 dif

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread Andrei Alexandrescu via Digitalmars-d
On 1/21/15 10:45 AM, Walter Bright wrote: On 1/21/2015 7:40 AM, Andrei Alexandrescu wrote: there's plenty of video processing software in the free world. About 10 years ago, I needed to edit a movie. I downloaded about 10 different video editors. Every one would hang, crash, go berserk, genera

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread H. S. Teoh via Digitalmars-d
On Wed, Jan 21, 2015 at 10:45:26AM -0800, Walter Bright via Digitalmars-d wrote: > On 1/21/2015 7:40 AM, Andrei Alexandrescu wrote: > >there's plenty of video processing software in the free world. > > About 10 years ago, I needed to edit a movie. I downloaded about 10 > different video editors. E

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread Walter Bright via Digitalmars-d
On 1/21/2015 7:40 AM, Andrei Alexandrescu wrote: there's plenty of video processing software in the free world. About 10 years ago, I needed to edit a movie. I downloaded about 10 different video editors. Every one would hang, crash, go berserk, generate corrupt files, etc. I didn't do anythi

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread ketmar via Digitalmars-d
On Wed, 21 Jan 2015 10:39:14 -0800 Walter Bright via Digitalmars-d wrote: > Why even ship such a product you have no intention of fixing bugs for? It's a > net negative for one's image. ah, that's a different question! i don't know why they still shipping it instead of providing link to virtuald

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread Walter Bright via Digitalmars-d
On 1/21/2015 8:23 AM, ketmar via Digitalmars-d wrote: this simply not work. Neither does Windows Moviemaker. It hung again on me. and not worth it. WMM is over a decade old, and it still hangs doing something as simple as trimming off the start and the end. And not rarely, either. It does

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread ketmar via Digitalmars-d
On Wed, 21 Jan 2015 00:40:48 -0800 Walter Bright via Digitalmars-d wrote: > I find this utterly baffling. Why make it so difficult to report a bug? > Microsoft has always been like this, the only way I've ever been able to > submit > a bug report was if I had a friend on the inside who'd carry

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread Andrei Alexandrescu via Digitalmars-d
On 1/21/15 1:14 AM, Joakim wrote: On Wednesday, 21 January 2015 at 08:41:47 UTC, Walter Bright wrote: On 1/21/2015 12:19 AM, Russel Winder via Digitalmars-d wrote: The Emacs D-Mode will only improve if people provide bug reports and fixes. A number of people are doing this for their "pain point

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread Walter Bright via Digitalmars-d
On 1/21/2015 1:14 AM, Joakim wrote: Probably because Microsoft has so many millions of users that their bug tracker would be awash with noise. Google allows anybody with a google account to post bugs or comment on them for Chrome and Android, which has led to a ton of noise on their public bug t

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread Walter Bright via Digitalmars-d
On 1/21/2015 12:59 AM, Russel Winder via Digitalmars-d wrote: Whereas for Emacs D-Mode you rock up to https://github.com/Emacs-D-Mode-Maintainers/Emacs-D-Mode/issues and post. There is no guarantee of action though since there is no-one paid to do support, it's all volunteer activity. However

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread Joakim via Digitalmars-d
On Wednesday, 21 January 2015 at 08:41:47 UTC, Walter Bright wrote: On 1/21/2015 12:19 AM, Russel Winder via Digitalmars-d wrote: The Emacs D-Mode will only improve if people provide bug reports and fixes. A number of people are doing this for their "pain points". If the Emacs D-Mode is substan

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread Russel Winder via Digitalmars-d
Whereas for Emacs D-Mode you rock up to https://github.com/Emacs-D-Mode-Maintainers/Emacs-D-Mode/issues and post. There is no guarantee of action though since there is no-one paid to do support, it's all volunteer activity. However a number of people do hack on the ELisp and fix things. All co

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread Walter Bright via Digitalmars-d
On 1/21/2015 12:19 AM, Russel Winder via Digitalmars-d wrote: The Emacs D-Mode will only improve if people provide bug reports and fixes. A number of people are doing this for their "pain points". If the Emacs D-Mode is substandard for you, can you at least submit issues presenting the problems.

Re: Emacs D-Mode [was Like Go/Rust, why not to have "func" keyword before function declaration]

2015-01-21 Thread Russel Winder via Digitalmars-d
On Tue, 2015-01-20 at 20:30 +, Jonathan Marler via Digitalmars-d wrote: […] > Which editor do you use? I use emacs. It has some quirks. The > D-Mode doesn't work very well (I end up using Notepad++ when > working on phobos/druntime), but I can use it on every platform > and over a remote

Re: Like Go/Rust, why not to have "func" keyword before function declaration

2015-01-20 Thread Walter Bright via Digitalmars-d
On 1/20/2015 12:30 PM, Jonathan Marler wrote: Which editor do you use? https://github.com/DigitalMars/me

Re: Like Go/Rust, why not to have "func" keyword before function declaration

2015-01-20 Thread ketmar via Digitalmars-d
On Tue, 20 Jan 2015 20:30:00 + Jonathan Marler via Digitalmars-d wrote: > On Tuesday, 20 January 2015 at 03:28:29 UTC, Walter Bright wrote: > > On 1/19/2015 7:20 PM, Walter Bright wrote: > >> Yes. "Search Again" is a single button press. It really has > >> never occurred to me > >> that this

Re: Like Go/Rust, why not to have "func" keyword before function declaration

2015-01-20 Thread Jonathan Marler via Digitalmars-d
On Tuesday, 20 January 2015 at 03:28:29 UTC, Walter Bright wrote: On 1/19/2015 7:20 PM, Walter Bright wrote: Yes. "Search Again" is a single button press. It really has never occurred to me that this might be a problem needing a solution. I admit that I've never gotten in to using an IDE. I s

Re: Like Go/Rust, why not to have "func" keyword before function declaration

2015-01-20 Thread Danni Coy via Digitalmars-d
> So... how do you search for a function definition in D without an IDE? Regular Expression Search for FunctionName.*\n\s*\{ or FunctionName.*\{ depending on brace style being used.

Re: Like Go/Rust, why not to have "func" keyword before function declaration

2015-01-20 Thread Joakim via Digitalmars-d
On Tuesday, 20 January 2015 at 00:13:37 UTC, Brian Schott wrote: On Monday, 19 January 2015 at 22:49:41 UTC, Ary Borenszweig wrote: So... how do you search for a function definition in D without an IDE? Running `dscanner --help` prints this: --declaration | -d symbolName [sourceFiles sourceDi

Re: Like Go/Rust, why not to have "func" keyword before function declaration

2015-01-20 Thread ketmar via Digitalmars-d
On Tue, 20 Jan 2015 13:49:47 + MattCoder via Digitalmars-d wrote: > On Tuesday, 20 January 2015 at 13:47:11 UTC, ketmar via > Digitalmars-d wrote: > > void function foo () { ... } > > foo(); > > > > do you see the subtle difference? yes, that tiny whitespace in > > declaration. i borrowe

Re: Like Go/Rust, why not to have "func" keyword before function declaration

2015-01-20 Thread MattCoder via Digitalmars-d
On Tuesday, 20 January 2015 at 13:47:11 UTC, ketmar via Digitalmars-d wrote: void function foo () { ... } foo(); do you see the subtle difference? yes, that tiny whitespace in declaration. i borrowed that habit from some Oberon code decades ago, and it serves me well since then. Hmm, nice

  1   2   3   >