Value of Email User Segmentation

Marketing is a crucial function in doing business. Through this, the company and its products are made known to the general public. Apart from attracting customers to buy, it is a good vehicle to create a healthy relationship with them. Also, it is the means to understand well the target

Re: Dip Discussion

On Monday, 29 August 2016 at 01:09:47 UTC, Illuminati wrote: So, I'd rather hear something "Yes, great idea... we will work on it when we get a chance" as it lets me know that the proper attitudes are in effect that will help D go somewhere. If I here "No, that's too hard... too much work. Not

Re: Dip Discussion

On Monday, 29 August 2016 at 00:10:15 UTC, Dicebot wrote: On Sunday, 28 August 2016 at 22:16:47 UTC, Illuminati wrote: I don't know how you can make such an assertion. It's like saying that if there were no humans around to breath there would be no oxygen. You have to build something first for

Re: Battle-plan for CTFE

Hi Guys, First of all, parsers will not make it before September. I am sorry about that. Currently I am fixing issues with the design, that for example prevent slices of slices to work. Also I am writing analysis and debugging code to (such as generating a call-graph and primitive DFA) that

Re: Dip Discussion

On Sunday, 28 August 2016 at 22:16:47 UTC, Illuminati wrote: I don't know how you can make such an assertion. It's like saying that if there were no humans around to breath there would be no oxygen. You have to build something first for it to be used and grow, not the other way around, which

[Issue 15960] SetUnion should filter duplicates

https://issues.dlang.org/show_bug.cgi?id=15960 --- Comment #1 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/501a1d5f41ec980b2b8c67b7a1fc31b6e65991a9 fix issue 15960 - deprecate setUnion in favor of merge

Re: Dip Discussion

On Sunday, 28 August 2016 at 22:16:47 UTC, Illuminati wrote: On Sunday, 28 August 2016 at 18:43:05 UTC, Dicebot wrote: For now intention is to aggregate all discussion threads / reviews / mail list archives via links in DIP itself. Thanks for reminding about it btw, I have just added

Re: Dip Discussion

On Sunday, 28 August 2016 at 18:43:05 UTC, Dicebot wrote: On Sunday, 28 August 2016 at 18:17:51 UTC, Illuminati wrote: Maybe for each Dip it would be nice to have a discussion or comments section exposed in some way. A full fledged subforum(per DIP) would be better so contrasting threads could

Re: InterlockedIncrement, InterlockedCompareExchange, etc

On Sunday, 28 August 2016 at 21:52:48 UTC, Illuminati wrote: The interlocked functions generate memory barriers, does atomicOp do that? Also D doesn't seem to have a volitile keyword anymore which is required to prevent the compiler from prematurely optimizing critical code. I'm under the

Re: InterlockedIncrement, InterlockedCompareExchange, etc

On Sunday, 28 August 2016 at 21:52:48 UTC, Illuminati wrote: Also D doesn't seem to have a volitile keyword anymore which is required to prevent the compiler from prematurely optimizing critical code. It isn't. In fact, using volatile to achieve thread synchronisation (seeing as this is what

Re: InterlockedIncrement, InterlockedCompareExchange, etc

On Sunday, 28 August 2016 at 20:38:30 UTC, Lodovico Giaretta wrote: On Sunday, 28 August 2016 at 19:53:51 UTC, Illuminati wrote: What are the D equivalents to these types of functions? I do not see anything in core.atomic that can accomplish this. I have tried to include

Re: InterlockedIncrement, InterlockedCompareExchange, etc

On Sunday, 28 August 2016 at 20:38:30 UTC, Lodovico Giaretta wrote: On Sunday, 28 August 2016 at 19:53:51 UTC, Illuminati wrote: What are the D equivalents to these types of functions? I do not see anything in core.atomic that can accomplish this. I have tried to include

[Issue 16443] std.getopt: segmentation fault with empty string option

https://issues.dlang.org/show_bug.cgi?id=16443 --- Comment #3 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/024b751547479b1ff973b0929c2aac34343f4de1 Fix Issue 16443 - Prevent segmentation fault If the

[Issue 16443] std.getopt: segmentation fault with empty string option

https://issues.dlang.org/show_bug.cgi?id=16443 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED

Re: InterlockedIncrement, InterlockedCompareExchange, etc

On Sunday, 28 August 2016 at 19:53:51 UTC, Illuminati wrote: What are the D equivalents to these types of functions? I do not see anything in core.atomic that can accomplish this. I have tried to include core.sys.windows.winbase but still get linker errors(I've also directly tried importing

InterlockedIncrement, InterlockedCompareExchange, etc

What are the D equivalents to these types of functions? I do not see anything in core.atomic that can accomplish this. I have tried to include core.sys.windows.winbase but still get linker errors(I've also directly tried importing kernel32 using various methods and still nothing). Regardless,

[Issue 16439] Non-typesafe variadic functions can never be @safe

https://issues.dlang.org/show_bug.cgi?id=16439 Walter Bright changed: What|Removed |Added Status|RESOLVED|REOPENED

Re: Dip Discussion

On Sunday, 28 August 2016 at 18:17:51 UTC, Illuminati wrote: Maybe for each Dip it would be nice to have a discussion or comments section exposed in some way. A full fledged subforum(per DIP) would be better so contrasting threads could be followed easier. How about using the pull request?

[Issue 14848] [REG 1.012] template alias on struct field without instance requires 'this'

https://issues.dlang.org/show_bug.cgi?id=14848 Andrej Mitrovic changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 6842] Can't use alias of instance member

https://issues.dlang.org/show_bug.cgi?id=6842 Andrej Mitrovic changed: What|Removed |Added CC|

Re: Dip Discussion

On Sunday, 28 August 2016 at 18:17:51 UTC, Illuminati wrote: Maybe for each Dip it would be nice to have a discussion or comments section exposed in some way. A full fledged subforum(per DIP) would be better so contrasting threads could be followed easier. For now intention is to aggregate

[Issue 16436] Implement pragma(switches, "")

https://issues.dlang.org/show_bug.cgi?id=16436 --- Comment #6 from b2.t...@gmx.com --- (In reply to Andrej Mitrovic from comment #5) > I don't see why `rdmd` couldn't try to parse the file manually for shebangs > and do something special on Windows. This could be an RDMD enhancement > request. I

[Issue 16443] std.getopt: segmentation fault with empty string option

https://issues.dlang.org/show_bug.cgi?id=16443 --- Comment #2 from Jean-Mathieu Deschenes --- Hi, I have already created a PR for it. Let me know what you think: https://github.com/dlang/phobos/pull/4753 --

Dip Discussion

Maybe for each Dip it would be nice to have a discussion or comments section exposed in some way. A full fledged subforum(per DIP) would be better so contrasting threads could be followed easier.

[Issue 11051] Unmatched case in a final switch should throw in both release and non-release mode

https://issues.dlang.org/show_bug.cgi?id=11051 Andrej Mitrovic changed: What|Removed |Added Assignee|nob...@puremagic.com

[Issue 16443] std.getopt: segmentation fault with empty string option

https://issues.dlang.org/show_bug.cgi?id=16443 Robert Schadek changed: What|Removed |Added CC||rburn...@gmail.com ---

[Issue 11051] Unmatched case in a final switch should throw in both release and non-release mode

https://issues.dlang.org/show_bug.cgi?id=11051 --- Comment #10 from Andrej Mitrovic --- (In reply to Orvid King from comment #9) > This seems like another case where a check should stay present in release > mode, > but only if it's in @safe code. I like this idea!

[Issue 16443] New: std.getopt: segmentation fault with empty string option

https://issues.dlang.org/show_bug.cgi?id=16443 Issue ID: 16443 Summary: std.getopt: segmentation fault with empty string option Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW

Re: if-expressions

On Sunday, 28 August 2016 at 13:48:43 UTC, Tomer Filiba wrote: Python uses `x = 5 if cond else 6`, which is by far more readable -tomer conseq1 if cond1 else conseq2 if cond2 else conseq3 if cond3 else conseq4 I dunno man, it seems all backwards to me. If you're gonna do it this way,

[Issue 16440] wrong code with -main -c -of

https://issues.dlang.org/show_bug.cgi?id=16440 --- Comment #3 from Andrej Mitrovic --- > dmd happily compiles multiple source files to one object file. Ah I thought this was only a feature of -lib. I forgot about the mix of -c and -of, otherwise it would indeed be

[Issue 16442] New: FrontTransversal fails with empty ranges

https://issues.dlang.org/show_bug.cgi?id=16442 Issue ID: 16442 Summary: FrontTransversal fails with empty ranges Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: normal Priority:

[Issue 16440] wrong code with -main -c -of

https://issues.dlang.org/show_bug.cgi?id=16440 --- Comment #2 from ag0ae...@gmail.com --- (In reply to Andrej Mitrovic from comment #1) > The problem is the compiler allows -c and -main. It will generate the D main > function in a separate module but later when you try to link via `dmd >

[Issue 16441] Implement the __FILE_FULL_PATH__ trait

https://issues.dlang.org/show_bug.cgi?id=16441 Andrej Mitrovic changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 16441] New: Implement the __FILE_FULL_PATH__ trait

https://issues.dlang.org/show_bug.cgi?id=16441 Issue ID: 16441 Summary: Implement the __FILE_FULL_PATH__ trait Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: enhancement

[Issue 10549] Default object equality test not properly implemented

https://issues.dlang.org/show_bug.cgi?id=10549 --- Comment #2 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/dlang.org https://github.com/dlang/dlang.org/commit/cbd6d46b0034eb0b4757c693a71566d64d19a850 default opEquals does not compare object contents

[Issue 16436] Implement pragma(switches, "")

https://issues.dlang.org/show_bug.cgi?id=16436 Andrej Mitrovic changed: What|Removed |Added CC|

[Issue 16439] Non-typesafe variadic functions can never be @safe

https://issues.dlang.org/show_bug.cgi?id=16439 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dlang.org https://github.com/dlang/dlang.org/commit/d78d5fd8f2796e55cd0e3eb35754d886c3f3b25a fix Issue 16439 - Non-typesafe variadic functions

[Issue 16439] Non-typesafe variadic functions can never be @safe

https://issues.dlang.org/show_bug.cgi?id=16439 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 16440] wrong code with -main -c -of

https://issues.dlang.org/show_bug.cgi?id=16440 Andrej Mitrovic changed: What|Removed |Added Keywords|wrong-code

Re: On the future of DIP1000

On Sunday, 28 August 2016 at 07:43:47 UTC, Walter Bright wrote: You've had a couple of worthwhile posts, you're welcome to stay and continue in that vein. Posts with unprofessional behavior, politics, etc., will be simply deleted. D deserved someone better than a person like Andrei, but it

Re: [GSoC] Improvements for dstep

On 08/27/2016 10:23 PM, ciechowoj wrote: > Hi. > > I would like to publish a report of my work for this year GSoC. Over the > last few months, I've been making improvements and fixing bugs for dstep. > > You can check out the changes I've made by following this link: > >

Re: if-expressions

On Sunday, 28 August 2016 at 11:14:00 UTC, Cauterite wrote: Mm you're right, I had the same concern. The ':' or '?' could both be just as easily used here, but I figured since IfExpressions kind of make ternary conditionals obsolete, it'd be better to 'free-up' the '?' token for other

Re: Allows the use of part of the language keywords?

On Sunday, 28 August 2016 at 13:26:26 UTC, Chris Wright wrote: On Sun, 28 Aug 2016 08:35:06 +, ketmar wrote: i have a perfect solution to this: don't write such code! It would reflect poorly on the compiler if it failed to compile something simply because you added a few comments.

Re: Allows the use of part of the language keywords?

On Sun, 28 Aug 2016 08:35:06 +, ketmar wrote: > i have a perfect solution to this: don't write such code! It would reflect poorly on the compiler if it failed to compile something simply because you added a few comments. Especially since each C-style comment is likely its own token. A

Re: Looking for work

On Sunday, 28 August 2016 at 09:24:29 UTC, Manu wrote: Hey people, I left my job, looking for work... just thought I'd cast a net out there to see if there's any interesting job opportunities floating around in these parts? I've spent the last 6 years trying to make D a substantial part of

[Issue 16434] dmd assertion failure in declaration.d

https://issues.dlang.org/show_bug.cgi?id=16434 --- Comment #2 from John Colvin --- dmd git HEAD as of a few days ago (fe0ab0df5cfe4aa9c1ec4ea140e5521767e28df5) --

[Issue 16434] dmd assertion failure in declaration.d

https://issues.dlang.org/show_bug.cgi?id=16434 --- Comment #3 from John Colvin --- OS X, but also tested on linux --

[Issue 16434] dmd assertion failure in declaration.d

https://issues.dlang.org/show_bug.cgi?id=16434 Andrej Mitrovic changed: What|Removed |Added CC|

Re: Looking for work

On 28/08/16 12:24, Manu via Digitalmars-d wrote: Hey people, I left my job, looking for work... just thought I'd cast a net out there to see if there's any interesting job opportunities floating around in these parts? I think such an approach would work better if you: A. Said which parts are

Re: Looking for work

On Sunday, 28 August 2016 at 09:24:29 UTC, Manu wrote: Hey people, I left my job, looking for work... just thought I'd cast a net out there to see if there's any interesting job opportunities floating around in these parts? I've spent the last 6 years trying to make D a substantial part of

Re: Allows the use of part of the language keywords?

On Sunday, 28 August 2016 at 08:25:38 UTC, Basile B. wrote: to think that it can be detected with a simple lookup backward (or forward from the KW) is too simplistic. I'm not saying it'd necessarily be easy to distinguish keyword 'body' from identifier 'body' in the lexer, I'm just saying a

Re: if-expressions

On Sunday, 28 August 2016 at 10:08:09 UTC, vladdeSV wrote: Nice work! However, don't you think it's a bit odd that `if(asdf : <-- colon 5 else 6)` equals `asdf ? <-- questionmark 5 : <-- colon 6;` Mm you're right, I had the same concern. The ':' or '?' could both be just as easily used

Re: On the future of DIP1000

On 8/28/2016 3:39 AM, Dicebot wrote: There have never been a single professional or at least constructively fashioned post from that account and tolerating that harms D public image. I have learned not to argue about this but I am very unhappy that you not only allow but encourage both off-topic

[Issue 16439] Non-typesafe variadic functions can never be @safe

https://issues.dlang.org/show_bug.cgi?id=16439 --- Comment #1 from Walter Bright --- Spec change: https://github.com/dlang/dlang.org/pull/1446 --

Re: On the future of DIP1000

On Saturday, 27 August 2016 at 20:54:02 UTC, Walter Bright wrote: On 8/27/2016 9:04 AM, Dicebot wrote: Please never reply to that person unless you are his other account. Not in an announce threads at least. If the post is reasonably professional, it's ok to. Abusive posts just get deleted.

Re: mutable destructor? WAT???

Looks correct to me. This const annotation does not prevent you from deleting memory or free'ing external resources - but it does ensure no transitive mutations for data reachable from struct fields. If it allowed destroying with mutable destructor, type system hole like this would be legal:

Re: How to call a method of class D from function of C++ in DLL?

On Sunday, 28 August 2016 at 08:20:52 UTC, MGW wrote: On Saturday, 27 August 2016 at 07:13:01 UTC, Nicholas Wilson wrote: easiest method would be to mark the D class extern(C++) noting that in C++ a D class reference becomes a pointer to the C++ class. In "the D class extern(C++)" do't work

[Issue 16440] New: wrong code with -main -c -of

https://issues.dlang.org/show_bug.cgi?id=16440 Issue ID: 16440 Summary: wrong code with -main -c -of Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Keywords: wrong-code Severity:

Re: Phobos uni methods

On 8/27/16 9:40 AM, Andrew wrote: On Monday, 22 August 2016 at 10:48:14 UTC, Lodovico Giaretta wrote: By the way, the core team is very busy so if Andrew (the OP) wants to make a PR himself, it would be welcome. Is there a tool somewhere that parses the UnicodeData.txt and PropList.txt and

Re: if-expressions

On Friday, 26 August 2016 at 18:25:00 UTC, Cauterite wrote: Here's a little patch you guys might enjoy: https://github.com/dlang/dmd/compare/master...Cauterite:ifExpr0 It enables this syntax: int foo = if(asdf: 5 else 6); equivalent to int foo = asdf ? 5 : 6; Here's some other examples which

Re: mutable destructor? WAT???

On Sunday, 28 August 2016 at 09:43:02 UTC, Jack Applegame wrote: object.destroy doesn't want to destroy const structure with destructor: [...] Is there a bug in druntime? Yes and I believe this is https://issues.dlang.org/show_bug.cgi?id=4338

[Issue 8838] Slicing static arrays should be considered unsafe (@system)

https://issues.dlang.org/show_bug.cgi?id=8838 --- Comment #17 from Walter Bright --- Fixed by: https://github.com/dlang/dmd/pull/5972 --

Re: DerelictSDL2 crashes

On Sunday, 28 August 2016 at 00:53:45 UTC, Mike Parker wrote: On Saturday, 27 August 2016 at 16:08:49 UTC, unDEFER wrote: dub --help Run "dub --help" to get help for a specific command. Thank you

Re: struct visibility attributes

On Sunday, 28 August 2016 at 09:32:11 UTC, eugene wrote: Hello, everyone, i looked at https://dlang.org/spec/attribute.html#visibility_attributes but it says nothing about visibility attributes in structs. inside a module you can even access to the private fields, it's clearly written in

[Issue 16439] Non-typesafe variadic functions can never be @safe

https://issues.dlang.org/show_bug.cgi?id=16439 Walter Bright changed: What|Removed |Added Keywords||safe, spec --

[Issue 16439] New: Non-typesafe variadic functions can never be @safe

https://issues.dlang.org/show_bug.cgi?id=16439 Issue ID: 16439 Summary: Non-typesafe variadic functions can never be @safe Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: normal

mutable destructor? WAT???

object.destroy doesn't want to destroy const structure with destructor: struct T { ~this() {} } void foo_t(ref T t) { destroy(t); // works } void foo_ct(ref const T t) { destroy(t); // Error: mutable method T.~this is not callable using a const object } Mutable destructor?

Re: struct visibility attributes

Because private is to module?

Re: struct visibility attributes

LDC: ldc2-0.17.1-linux-x86_64

struct visibility attributes

Hello, everyone, i looked at https://dlang.org/spec/attribute.html#visibility_attributes but it says nothing about visibility attributes in structs. The question is: why is the code compiled by ldc and working: import std.stdio:writeln; void main() { test_struct testStruct =

Looking for work

Hey people, I left my job, looking for work... just thought I'd cast a net out there to see if there's any interesting job opportunities floating around in these parts? I've spent the last 6 years trying to make D a substantial part of my career by integrating it into my existing working

Re: Unicode function name? ∩

On Sun, 2016-08-28 at 08:03 +, Cauterite via Digitalmars-d-learn wrote: > On Sunday, 28 August 2016 at 05:21:03 UTC, Tofu Ninja wrote: > > > > Are unicode function names not supported in dmd? > > Here's a few ANSI characters you can use (and can type with  > alt-codes): > ª º · Ø ø µ ƒ > I

Re: Few questions about concurrency

On Sat, 2016-08-27 at 07:30 +, Suliman via Digitalmars-d-learn wrote: > […] > > 1. There is OS threads. Context-switching is very expensive  > because during it we should to save ALL CPU registers to RAM.  > Accessing to RAM is slowly up 200-300 times then accessing to  > registers, so

Re: Allows the use of part of the language keywords?

On Sunday, 28 August 2016 at 08:25:38 UTC, Basile B. wrote: On Sunday, 28 August 2016 at 08:07:27 UTC, Cauterite wrote: On Sunday, 28 August 2016 at 04:32:46 UTC, Basile B. wrote: You must keep track of the previous token, which is not usually done in a scanner. That sounds like a pretty

Re: Allows the use of part of the language keywords?

On Sunday, 28 August 2016 at 08:07:27 UTC, Cauterite wrote: On Sunday, 28 August 2016 at 04:32:46 UTC, Basile B. wrote: You must keep track of the previous token, which is not usually done in a scanner. That sounds like a pretty trivial feature to me. There's no way that's a legitimate

Re: How to call a method of class D from function of C++ in DLL?

On Saturday, 27 August 2016 at 07:13:01 UTC, Nicholas Wilson wrote: easiest method would be to mark the D class extern(C++) noting that in C++ a D class reference becomes a pointer to the C++ class. In "the D class extern(C++)" do't work phobos.

Re: Allows the use of part of the language keywords?

On Sunday, 28 August 2016 at 04:32:46 UTC, Basile B. wrote: You must keep track of the previous token, which is not usually done in a scanner. That sounds like a pretty trivial feature to me. There's no way that's a legitimate obstacle.

Re: Unicode function name? ∩

On Sunday, 28 August 2016 at 05:21:03 UTC, Tofu Ninja wrote: Are unicode function names not supported in dmd? Here's a few ANSI characters you can use (and can type with alt-codes): ª º · Ø ø µ ƒ I use º pretty often, it makes a nice sigil.

Re: std.functional.compose compilation error

On Thursday, 25 August 2016 at 21:01:29 UTC, Antonio Corbi wrote: On Thursday, 25 August 2016 at 14:30:00 UTC, Meta wrote: On Thursday, 25 August 2016 at 14:06:32 UTC, Antonio Corbi wrote: Hello, Trying to compile this example from Chuck Allison: ---

Re: On the future of DIP1000

On 8/27/2016 11:58 PM, Bill Hicks wrote: white men There are plenty of other forums for politics. Not this one. You've had a couple of worthwhile posts, you're welcome to stay and continue in that vein. Posts with unprofessional behavior, politics, etc., will be simply deleted.

Re: On the future of DIP1000

On Saturday, 27 August 2016 at 20:47:16 UTC, Walter Bright wrote: On 8/27/2016 8:19 AM, Bill Hicks wrote: I believe Andrei's point was that Rust had focused on one problem to the relative exclusion of others, not that memory safety was unimportant. Rust, to its credit, has changed the

Re: On the future of DIP1000

On Saturday, 27 August 2016 at 15:34:04 UTC, Anonymouse wrote: On Saturday, 27 August 2016 at 15:19:40 UTC, Bill Hicks wrote: On Saturday, 27 August 2016 at 05:57:25 UTC, Walter Bright wrote: We've never mocked Rust's safety features, although I have posted that they are too complex for D

Re: On the future of DIP1000

On Saturday, 27 August 2016 at 16:04:34 UTC, Dicebot wrote: On Saturday, 27 August 2016 at 15:34:04 UTC, Anonymouse wrote: ... Please never reply to that person unless you are his other account. Not in an announce threads at least. I ran a quick linguistic analysis and it shows that there

Re: [GSoC] std.experimental.xml is now a PR!

On Wednesday, 24 August 2016 at 09:31:44 UTC, Lodovico Giaretta wrote: Hi! I'm pleased to announce that my GSoC project, a replacement for the outdated std.xml, is now a Phobos PR! [1] It is an (almost complete) mirror of my repository [2], which is also available on DUB [3]. I would like