Re: Always false float comparisons

On Saturday, 14 May 2016 at 01:26:18 UTC, Walter Bright wrote: An anecdote: a colleague of mine was once doing a chained calculation. At every step, he rounded to 2 digits of precision after the decimal point, because 2 digits of precision was enough for anybody. I carried out the same

Re: Always false float comparisons

On Saturday, 14 May 2016 at 01:26:18 UTC, Walter Bright wrote: BTW, I once asked Prof Kahan about this. He flat out told me that the only reason to downgrade precision was if storage was tight or you needed it to run faster. I am not making this up. He should have been aware of

Re: Github names & avatars

On Sat, May 14, 2016 at 08:09:51AM +0300, Andrei Alexandrescu via Digitalmars-d wrote: > On 5/14/16 12:01 AM, Meta wrote: > >So many careers have been lost over some flippant tweet or Github > >comment that complete anonymity is the only sane option, whenever > >possible. > > Could you bring

Re: Github names & avatars

On 5/14/16 12:01 AM, Meta wrote: So many careers have been lost over some flippant tweet or Github comment that complete anonymity is the only sane option, whenever possible. Could you bring some evidence or list a few anecdotes over the careers lost over a tweet or github comment? Thx! --

[OT] Re: Github names & avatars

On 5/13/16 11:54 PM, Xinok wrote: On Friday, 13 May 2016 at 18:56:15 UTC, Walter Bright wrote: If some company won't hire you because you contributed code to D, I'd say you dodged a bullet working for such! I've known a couple people who had to apply for over 200-300 positions before they

Re: Command line parsing

On 5/13/16 2:27 PM, Russel Winder via Digitalmars-d wrote: On Thu, 2016-05-12 at 18:25 +, Jesse Phillips via Digitalmars-d wrote: […] unknown flags harder and displaying help challenging. So I'd like to see getopt merge with another getopt getopt is a 1970s C solution to the problem of

Re: Researcher question – what's the point of semicolons and curly braces?

On Tuesday, 3 May 2016 at 12:47:42 UTC, qznc wrote: The parser needs information about "blocks". Here is an example: if (x) foo(); bar(); Is bar() always executed or only if (x) is true? In other words, is bar() part of the block, which is only entered conditionally? There are

Re: Always false float comparisons

On 5/13/2016 5:49 PM, Timon Gehr wrote: Nonsense. That might be true for your use cases. Others might actually depend on IEE 754 semantics in non-trivial ways. Higher precision for temporaries does not imply higher accuracy for the overall computation. Of course it implies it. An anecdote: a

Re: Request assistance converting C's #ifndef to D

On 5/14/16 12:35 AM, Steven Schveighoffer wrote: On 5/13/16 12:59 AM, Andrew Edwards wrote: On 5/13/16 8:40 AM, Andrew Edwards wrote: That seems wrong. You can't assign to an enum. Besides, doesn't your declaration of MIN shadow whatever other definitions may be currently in effect? Okay,

Re: Always false float comparisons

On 14.05.2016 02:49, Timon Gehr wrote: result can actually be made less precise less accurate. I need to go to sleep.

Re: Always false float comparisons

On 14.05.2016 02:49, Timon Gehr wrote: IEE IEEE.

Re: Always false float comparisons

On 13.05.2016 23:35, Walter Bright wrote: On 5/13/2016 12:48 PM, Timon Gehr wrote: IMO the compiler should never be allowed to use a precision different from the one specified. I take it you've never been bitten by accumulated errors :-) ... If that was the case it would be because I

Re: Always false float comparisons

On 5/13/2016 2:42 PM, Ola Fosheim Grøstad wrote: On Friday, 13 May 2016 at 21:36:52 UTC, Walter Bright wrote: On 5/13/2016 1:57 PM, Ola Fosheim Grøstad wrote: It should in C++ with the right strict-settings, Consider what the C++ Standard says, not what the endless switches to tweak the

Re: To all DConf speakers: please upload slides!

On Friday, 13 May 2016 at 15:24:22 UTC, Steven Schveighoffer wrote: You only *need* the slides for when you can watch the talk. Having the slides beforehand may be confusing and unhelpful. This means there is no reason to provide the slides until the talk actually happens. I almost want to

Re: Potential issue with DMD where the template constrains are not evaluated early enough to prevent type recursion

On 13.05.2016 23:21, Georgi D wrote: Hi, I have the following code which should compile in my opinion: struct Foo {} import std.range.primitives; import std.algorithm.iteration : map, joiner; auto toChars(R)(R r) if (isInputRange!R) { return r.map!(toChars).joiner(", "); } auto

[Issue 15999] Inline assembly incorrect sign extension instead of error

https://issues.dlang.org/show_bug.cgi?id=15999 safety0ff.bugz changed: What|Removed |Added Keywords||pull --- Comment

[Issue 13954] (D1 only) Compiler allows implementing float return method with a real return type

https://issues.dlang.org/show_bug.cgi?id=13954 Stewart Gordon changed: What|Removed |Added Keywords||accepts-invalid --

[Issue 15780] [REG2.069] CTFE foreach fails with tuple

https://issues.dlang.org/show_bug.cgi?id=15780 Kenji Hara changed: What|Removed |Added Summary|CTFE foreach fails with |[REG2.069] CTFE foreach

[Issue 16022] [REG2.069] dmd assertion failure due to misplaced comma operator

https://issues.dlang.org/show_bug.cgi?id=16022 Kenji Hara changed: What|Removed |Added Keywords||pull --- Comment #2 from

[Issue 16024] New: More struct/class/interface introspection helpers

https://issues.dlang.org/show_bug.cgi?id=16024 Issue ID: 16024 Summary: More struct/class/interface introspection helpers Product: D Version: D2 Hardware: x86 OS: Linux Status: NEW Severity: enhancement

[Issue 16021] Template constraint bug

https://issues.dlang.org/show_bug.cgi?id=16021 Kenji Hara changed: What|Removed |Added Status|NEW |RESOLVED

Re: Battle-plan for CTFE

On Wednesday, May 11, 2016 07:06:59 maik klein via Digitalmars-d-announce wrote: > What is the current problem with ctfe? The biggest problem is that it uses up a _lot_ of memory and is generally slow. For instance, as I understand it, every time it mutates a variable, it actually allocates a

[Issue 16013] [REG2.072a] ICE with mutually dependent structs and alias this

https://issues.dlang.org/show_bug.cgi?id=16013 Kenji Hara changed: What|Removed |Added Keywords||pull

[Issue 16023] New: Add template or trait to find the importable symbol name for a type

https://issues.dlang.org/show_bug.cgi?id=16023 Issue ID: 16023 Summary: Add template or trait to find the importable symbol name for a type Product: D Version: D2 Hardware: x86 OS: Linux Status:

[Issue 16012] [REG2.070] forward reference with alias this

https://issues.dlang.org/show_bug.cgi?id=16012 Kenji Hara changed: What|Removed |Added Keywords||pull

[Issue 16011] [REG2.068] recursive RefCounted used to work

https://issues.dlang.org/show_bug.cgi?id=16011 Kenji Hara changed: What|Removed |Added Keywords||pull

Re: Defining member fuctions of a class or struct out side of the class/struct body?

On 05/13/2016 11:41 AM, Jamal wrote: Warning D newb here. Is it possible to define a member function outside of the class/struct like in C++; class x { body void foo(int* i); }; void x::foo(int* i){ *i++; } Or is it just D-like to define everything inside the class/struct body?

Re: Defining member fuctions of a class or struct out side of the class/struct body?

On 5/13/16 2:41 PM, Jamal wrote: Warning D newb here. Is it possible to define a member function outside of the class/struct like in C++; Not within the same file. You can have an "interface file", extension .di, which hides the bodies of functions. But inside the implementation file, you

[Issue 16022] [REG2.069] dmd assertion failure due to misplaced comma operator

https://issues.dlang.org/show_bug.cgi?id=16022 ag0ae...@gmail.com changed: What|Removed |Added Keywords||ice CC|

Defining member fuctions of a class or struct out side of the class/struct body?

Warning D newb here. Is it possible to define a member function outside of the class/struct like in C++; class x { body void foo(int* i); }; void x::foo(int* i){ *i++; } Or is it just D-like to define everything inside the class/struct body?

[Issue 16022] New: dmd assertion failure due to misplaced comma operator

https://issues.dlang.org/show_bug.cgi?id=16022 Issue ID: 16022 Summary: dmd assertion failure due to misplaced comma operator Product: D Version: D2 Hardware: x86 OS: Mac OS X Status: NEW Severity: major

Re: To all DConf speakers: please upload slides!

On 05/13/2016 08:24 AM, Steven Schveighoffer wrote: > But then the slides provided online don't match the slides you are > showing. That is not good. Thanks to you, I've fixed my silly binary-tree mistake in one of my slides. My slides on dconf.org don't match the ones in the video. :) Ali

Re: Github names & avatars

On 5/13/2016 10:19 AM, Adam D. Ruppe wrote: It is nice to have a consistent pseudonym for matching up forum posts with irc with github etc., but let's not make this a requirement. It's a suggestion, not a requirement. I respect that some people have good reasons for anonymity.

Re: Request assistance converting C's #ifndef to D

On Thursday, 12 May 2016 at 22:51:17 UTC, Andrew Edwards wrote: The following preprocessor directives are frequently encountered in C code, providing a default constant value where the user of the code has not specified one: #ifndef MIN #define MIN 99 #endif

[Issue 13954] (D1 only) Compiler allows implementing float return method with a real return type

https://issues.dlang.org/show_bug.cgi?id=13954 Walter Bright changed: What|Removed |Added CC|

[Issue 13954] (D1 only) Compiler allows implementing float return method with a real return type

https://issues.dlang.org/show_bug.cgi?id=13954 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to dmd-1.x at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/8728fdd029d1f6765dd634fef2a7ed25b6539f4d Fix Issue 13954 - Disallow non-covariant overrides

Re: Github names & avatars

On Friday, 13 May 2016 at 17:02:20 UTC, Walter Bright wrote: In today's surveillance state, the government already knows your name and what you look like, so being anonymous on github is a bit pointless, as if anyone cares that you are interested in D. I can understand if you're a celebrity or

Re: Github names & avatars

On 5/13/16 1:02 PM, Walter Bright wrote: I'll ask again that the active Github users use their own name, and add to that if you could have a selfie as your github image. Sorry, this isn't going to happen :) @schveiguy is much better than @StevenSchveighoffer. Some of us are not so

Github names & avatars

I'll ask again that the active Github users use their own name, and add to that if you could have a selfie as your github image. It avoids when people who post as "Fred" on the newsgroup submit PRs as "HorseWrangler" and get annoyed when I don't realize they are the same person, and then I

Re: Reproducible builds of D compilers

On Saturday, 7 May 2016 at 17:56:07 UTC, Johan Engelen wrote: On Saturday, 7 May 2016 at 16:22:34 UTC, Vladimir Panteleev wrote: https://blog.thecybershadow.net/2015/05/05/is-d-slim-yet/ Thanks for repeating the link to that blog article. I was reminded of it at DConf. Would be great if

Re: Version block "conditions" with logical operators

On 5/13/2016 1:57 AM, Joakim wrote: I'm trying, but Daniel seems against it, care to chip in? https://github.com/dlang/dmd/pull/5772 Specifically, do you want the changes in that PR? If so, do you prefer the use of TARGET_POSIX as a runtime variable or listing each TARGET_OS separately? I

Re: Battle-plan for CTFE

On Friday, 13 May 2016 at 13:59:57 UTC, Don Clugston wrote: I think I need to explain the history of CTFE. Originally, we had constant-folding. Then constant-folding was extended to do things like slicing a string at compile time. Constant folding leaks memory like the Exxon Valdez leaks oil,

Re: imports && -run [Bug?]

On Friday, 13 May 2016 at 06:33:40 UTC, Jacob Carlborg wrote: Even better is to use "rdmd" which will automatically track and compile dependencies. but i should warn about annoing bug with local import http://forum.dlang.org/post/mailman.1984.1373610213.13711.digitalmar...@puremagic.com

Re: Request assistance converting C's #ifndef to D

On Thursday, 12 May 2016 at 22:51:17 UTC, Andrew Edwards wrote: The following preprocessor directives are frequently encountered in C code, providing a default constant value where the user of the code has not specified one: #ifndef MIN #define MIN 99 #endif

Re: The Case Against Autodecode

On 5/12/16 4:15 PM, Walter Bright wrote: 10. Autodecoded arrays cannot be RandomAccessRanges, losing a key benefit of being arrays in the first place. I'll repeat what I said in the other thread. The problem isn't auto-decoding. The problem is hijacking the char[] and wchar[] (and variants)

Re: Battle-plan for CTFE

On 13.05.2016 15:59, Don Clugston wrote: All that's needed is a very simple bytecode interpreter. Here is the one I have hacked together: https://github.com/tgehr/d-compiler/blob/master/interpret.d This file does both constant folding and byte-code interpretation for most of the language. I

Re: Request assistance converting C's #ifndef to D

On 5/13/16 12:59 AM, Andrew Edwards wrote: On 5/13/16 8:40 AM, Andrew Edwards wrote: That seems wrong. You can't assign to an enum. Besides, doesn't your declaration of MIN shadow whatever other definitions may be currently in effect? Okay, got it. It seams I just hadn't hit that bug yet

Re: To all DConf speakers: please upload slides!

On 5/12/16 6:21 PM, Daniel Kozak via Digitalmars-d-announce wrote: Dne 12.5.2016 v 22:55 Steven Schveighoffer via Digitalmars-d-announce napsal(a): On 5/12/16 4:13 PM, Seb wrote: On Wednesday, 11 May 2016 at 09:17:54 UTC, Dicebot wrote: To do the editing of HD videos we need presentation

Re: To all DConf speakers: please upload slides!

On 5/12/16 8:31 PM, Vladimir Panteleev wrote: On Thursday, 12 May 2016 at 23:14:05 UTC, Leandro Lucarella wrote: Steven Schveighoffer, el 12 de May a las 16:55 me escribiste: On 5/12/16 4:13 PM, Seb wrote: >On Wednesday, 11 May 2016 at 09:17:54 UTC, Dicebot wrote: >>To do the editing of HD

Re: The Case Against Autodecode

On Friday, 13 May 2016 at 14:06:28 UTC, Vladimir Panteleev wrote: On Friday, 13 May 2016 at 13:41:30 UTC, Chris wrote: PS Why does do I get a "StopForumSpam error" every time I post today? Has anyone else experienced the same problem: "StopForumSpam error: Socket error: Lookup error:

Re: The Case Against Autodecode

On Friday, 13 May 2016 at 13:41:30 UTC, Chris wrote: PS Why does do I get a "StopForumSpam error" every time I post today? Has anyone else experienced the same problem: "StopForumSpam error: Socket error: Lookup error: getaddrinfo error: Name or service not known. Please solve a CAPTCHA to

Re: Always false float comparisons

On 13 May 2016 at 07:12, Manu via Digitalmars-d wrote: > On 13 May 2016 at 11:03, Walter Bright via Digitalmars-d > wrote: >> On 5/12/2016 4:32 PM, Marco Leise wrote: >>> >>> - Unless CTFE uses soft-float implementation, depending on >>>

Re: Battle-plan for CTFE

On Monday, 9 May 2016 at 16:57:39 UTC, Stefan Koch wrote: Hi Guys, I have been looking into the DMD now to see what I can do about CTFE. Unfortunately It is a pretty big mess to untangle. Code responsible for CTFE is in at least 3 files. [dinterpret.d, ctfeexpr.d, constfold.d] I was shocked

Re: Adventures in D Programming

On Thursday, 12 May 2016 at 21:08:58 UTC, Matthias Klumpp wrote: To elaborate a bit more on the version incompatibilities thing: E.g. me as a new user reads about std.concurrency.Generator, wants to use it, and it turns out that the standard library doesn't contain it yet (in GDC). Same for

Re: The Case Against Autodecode

On Friday, 13 May 2016 at 13:17:44 UTC, Walter Bright wrote: On 5/13/2016 2:12 AM, Chris wrote: If autodecode is killed, could we have a test version asap? I'd be willing to test my programs with autodecode turned off and see what happens. Others should do likewise and we could come up with a

Re: The Case Against Autodecode

On 5/13/2016 3:43 AM, Marc Schütz wrote: On Thursday, 12 May 2016 at 20:15:45 UTC, Walter Bright wrote: 7. Autodecode cannot be used with unicode path/filenames, because it is legal (at least on Linux) to have invalid UTF-8 as filenames. It turns out in the wild that pure Unicode is not

Re: The Case Against Autodecode

On 5/12/2016 11:50 PM, Bill Hicks wrote: And I get called a troll and other names when I list half a dozen things wrong with D, my posts get removed/censored, etc, all because I try to inform people not to waste time with D because it's a broken and failed language. Posts that engage in

Re: The Case Against Autodecode

On 5/13/2016 2:12 AM, Chris wrote: If autodecode is killed, could we have a test version asap? I'd be willing to test my programs with autodecode turned off and see what happens. Others should do likewise and we could come up with a transition strategy based on what happened. You can avoid

Re: The Case Against Autodecode

On Friday, 13 May 2016 at 10:38:09 UTC, Jonathan M Davis wrote: IIRC, Andrei talked in TDPL about how Java's choice to go with UTF-16 was worse than the choice to go with UTF-8, because it was correct in many more cases UTF-16 was a migration from UCS-2, and UCS-2 was superior at the time.

Re: Killing the comma operator

On Thursday, 12 May 2016 at 02:51:33 UTC, Lionello Lunesu wrote: I'm trying to think of a case where changing a single value into a tuple with 2 (or more) values would silently change the behavior, but I can't think of any. Seems to me it would always cause an error, iff the result of the

[Issue 15662] Cannot move struct with defined opAssign due to @disabled post-blit

https://issues.dlang.org/show_bug.cgi?id=15662 --- Comment #12 from Martin Nowak --- (In reply to Martin Nowak from comment #11) > static if (!hasElaborateAssign!T && isAssignable!T) > chunk = T.init; That needs to be `value = T.init;`. Direct assignment is an

Re: Adventures in D Programming

On Thursday, 12 May 2016 at 22:01:04 UTC, David Nadlinger wrote: Are there any bug reports for this, by the way? Thanks! I believe, it was the atomicOp bug. You can see the link to discussion there.

Re: The Case Against Autodecode

On Friday, 13 May 2016 at 00:47:04 UTC, Jack Stouffer wrote: If you're serious about removing auto-decoding, which I think you and others have shown has merits, you have to the THE SIMPLEST migration path ever, or you will kill D. I'm talking a simple press of a button. char[] is always

Re: imports && -run [Bug?]

On 2016-05-13 08:27, Andrew Edwards wrote: I fail to see why the compiler would be less capable at this task than rdmd. Since it is already build to accept multiple input files and knows more about what's going on during compilation than rdmd will ever know, in does not make sense that it

Re: DMD flag -gs and -gx

On Friday, 13 May 2016 at 10:19:04 UTC, Nordlöw wrote: -gsalways emit stack frame IIRC, not emitting a stack frame is an optimization which confuses debuggers. So I think this can be used to make optimized builds a bit easier to debug. -gxadd stack stomp code

Re: Command line parsing

On Thu, 2016-05-12 at 18:25 +, Jesse Phillips via Digitalmars-d wrote: […] > unknown flags harder and displaying help challenging. So I'd like  > to see getopt merge with another getopt getopt is a 1970s C solution to the problem of command line parsing. Most programming languages have moved

Re: How to split a string/array with multiple separators?

Wow, thanks Steve :)

Re: The Case Against Autodecode

On Friday, 13 May 2016 at 10:38:09 UTC, Jonathan M Davis wrote: Ideally, algorithms would be Unicode aware as appropriate, but the default would be to operate on code units with wrappers to handle decoding by code point or grapheme. Then it's easy to write fast code while still allowing for

[Issue 15959] core.sys.windows modules should be modified for x64

https://issues.dlang.org/show_bug.cgi?id=15959 --- Comment #5 from j...@red.email.ne.jp --- https://github.com/dlang/druntime/pull/1574 --

Re: The Case Against Autodecode

On Thursday, 12 May 2016 at 23:16:23 UTC, H. S. Teoh wrote: Therefore, autodecoding actually only produces intuitively correct results when your string has a 1-to-1 correspondence between grapheme and code point. In general, this is only true for a small subset of languages, mainly a few

Re: The Case Against Autodecode

On Friday, 13 May 2016 at 10:38:09 UTC, Jonathan M Davis wrote: Based on what I've seen in previous conversations on auto-decoding over the past few years (be it in the newsgroup, on github, or at dconf), most of the core devs think that auto-decoding was a major blunder that we continue to

Re: The Case Against Autodecode

On Thursday, 12 May 2016 at 20:15:45 UTC, Walter Bright wrote: 7. Autodecode cannot be used with unicode path/filenames, because it is legal (at least on Linux) to have invalid UTF-8 as filenames. It turns out in the wild that pure Unicode is not universal - there's lots of dirty Unicode that

Re: synchronized with multiple arguments

On Friday, 13 May 2016 at 09:17:06 UTC, Andrei Alexandrescu wrote: A reader reminded me (thanks!) that in TDPL synchronized with multiple argument does the right thing - locks objects in increasing order of address. So now to everyone's unpleasant surprise, the sample code in TDPL compiles

Re: The Case Against Autodecode

On Thursday, May 12, 2016 13:15:45 Walter Bright via Digitalmars-d wrote: > On 5/12/2016 9:29 AM, Andrei Alexandrescu wrote: > > I am as unclear about the problems of autodecoding as I am about the > > necessity to remove curl. Whenever I ask I hear some arguments that work > > well emotionally

DMD flag -gs and -gx

What role does the DMD flags -gs and -gx play? The documentation says -gsalways emit stack frame -gxadd stack stomp code which I don't know what it means.

Re: The Case Against Autodecode

On Friday, 13 May 2016 at 06:50:49 UTC, Bill Hicks wrote: not to waste time with D because it's a broken and failed language. D is a better broken thing among all the broken things in this broken world, so it's to be expected to be preferred to spend time on.

Re: The backlash against scripting languages has begun

On Friday, 13 May 2016 at 07:31:26 UTC, Joakim wrote: He mentions Swift, Rust, and Go as his hopes at the end, too bad he doesn't include D: https://medium.com/@deathdisco/today-i-accept-that-rails-is-yesterday-s-software-b5af35c9af39 He'd probably be happy with D, particularly given Walter's

Re: To all DConf speakers: please upload slides!

On Thu, May 12, 2016 at 10:55 PM, Steven Schveighoffer via Digitalmars-d-announce wrote: > On 5/12/16 4:13 PM, Seb wrote: > >> On Wednesday, 11 May 2016 at 09:17:54 UTC, Dicebot wrote: >> >>> To do the editing of HD videos we need presentation slides which

Re: The Case Against Autodecode

On Friday, 13 May 2016 at 06:50:49 UTC, Bill Hicks wrote: Wow, that's eleven things wrong with just one tiny element of D, with the potential to cause problems, whether fixed or not. And I get called a troll and other names when I list half a dozen things wrong with D, my posts get

synchronized with multiple arguments

A reader reminded me (thanks!) that in TDPL synchronized with multiple argument does the right thing - locks objects in increasing order of address. So now to everyone's unpleasant surprise, the sample code in TDPL compiles and runs, it just has difficult to detect problems. So regardless

Re: The Case Against Autodecode

On Friday, 13 May 2016 at 01:00:54 UTC, Walter Bright wrote: On 5/12/2016 5:47 PM, Jack Stouffer wrote: D is much less popular now than was Python at the time, and Python 2 problems were more straight forward than the auto-decoding problem. You'll need a very clear migration path, years long

Re: Version block "conditions" with logical operators

On Thursday, 12 May 2016 at 01:58:33 UTC, Walter Bright wrote: On 5/11/2016 6:52 PM, Joakim wrote: That example is misleading, as that was translated from C++ and the host half of it was removed a couple months ago: https://github.com/dlang/dmd/pull/5549/files I'll submit a PR for the rest:

Re: Command line parsing

On 5/12/16 8:21 PM, Nick Sabalausky wrote: You may want to ask Sonke about his specific reasons and experiences with that design. Yes please! -- Andrei

Re: Casting Pointers?

On Thursday, 12 May 2016 at 22:23:38 UTC, Marco Leise wrote: The pointer cast solution is specifically supported at CTFE, because /unions/ don't work there. :p Well that's a problem ^^ I remember a discussion quite a while ago where Walter stated D should have strict aliasing rules, let me

Re: To all DConf speakers: please upload slides!

On Wednesday, 11 May 2016 at 17:31:32 UTC, dilkROM wrote: And also, if anyone can identify all lightning speakers, that would be terrific. We do need their slides and their names / desired nicknames / contact info as well. :) I didn't use slides, but only a few code examples, collected in a

Re: Always false float comparisons

On Friday, 13 May 2016 at 05:12:14 UTC, Manu wrote: No. Do not. I've worked on systems where the compiler and the runtime don't share floating point precisions before, and it was a nightmare. Use reproducible cross platform IEEE754-2008 and use exact rational numbers. All other

Re: The Case Against Autodecode

On Friday, 13 May 2016 at 00:47:04 UTC, Jack Stouffer wrote: D is much less popular now than was Python at the time, and Python 2 problems were more straight forward than the auto-decoding problem. You'll need a very clear migration path, years long deprecations, and automatic tools in order

The backlash against scripting languages has begun

He mentions Swift, Rust, and Go as his hopes at the end, too bad he doesn't include D: https://medium.com/@deathdisco/today-i-accept-that-rails-is-yesterday-s-software-b5af35c9af39 He'd probably be happy with D, particularly given Walter's stance on the monkey-patching that guy now rues:

Re: The Case Against Autodecode

On Friday, 13 May 2016 at 06:50:49 UTC, Bill Hicks wrote: On Thursday, 12 May 2016 at 20:15:45 UTC, Walter Bright wrote: (...) Wow, that's eleven things wrong with just one tiny element of D, with the potential to cause problems, whether fixed or not. And I get called a troll and other names

Re: The Case Against Autodecode

On Friday, 13 May 2016 at 06:50:49 UTC, Bill Hicks wrote: *rant* Actually, chap, it's the attitude that's the turn-off in your post there. Listing problems in order to improve them, and listing problems to convince people something is a waste of time are incompatible mindsets around here.

Re: The end of curl (in phobos)

Am Sun, 8 May 2016 11:33:07 +0300 schrieb Andrei Alexandrescu : > On 5/8/16 11:05 AM, Jonathan M Davis via Digitalmars-d wrote: > > On Sunday, May 08, 2016 02:44:48 Adam D. Ruppe via Digitalmars-d > > wrote: > >> On Saturday, 7 May 2016 at 20:50:53 UTC, Jonas

Re: The Case Against Autodecode

On Thursday, 12 May 2016 at 20:15:45 UTC, Walter Bright wrote: Here are some that are not matters of opinion. 1. Ranges of characters do not autodecode, but arrays of characters do. This is a glaring inconsistency. 2. Every time one wants an algorithm to work with both strings and ranges,

Re: Request assistance converting C's #ifndef to D

On 5/13/16 3:23 PM, tsbockman wrote: On Friday, 13 May 2016 at 06:05:14 UTC, Andrew Edwards wrote: Additionally, what's the best way to handle nested #ifdef's? Those that appear inside structs, functions and the like... I know that global #ifdef's are turned to version blocks but versions

Re: Command line parsing

On 2016-05-02 14:52, Andrei Alexandrescu wrote: I found this in https://peter.bourgon.org/go-best-practices-2016/: "I said it in 2014 but I think it’s important enough to say again: define and parse your flags in func main. Only func main has the right to decide the flags that will be available

Re: Command line parsing

On 2016-05-12 19:21, Nick Sabalausky wrote: Vibe.d uses a system (built on top of getopt, IIRC) that allows different modules to define and handle their own flags. It seems to be useful for framework-style libraries where there are certain common flags automatically provided and handled by the

Re: imports && -run [Bug?]

On 2016-05-13 08:10, tsbockman wrote: According to the DMD compiler manual, the -run switch only accepts a single source file: -run srcfile args... After the first source file, any further arguments passed to DMD will be interpreted as arguments to be passed to the program being run. To

Re: imports && -run [Bug?]

On 5/13/16 3:10 PM, tsbockman wrote: On Friday, 13 May 2016 at 01:16:36 UTC, Andrew Edwards wrote: command: dmd -run mod inc output: Undefined symbols for architecture x86_64: "_D3inc5printFZv", referenced from: __Dmain in mod.o ld: symbol(s) not found for architecture x86_64 clang:

Re: Request assistance converting C's #ifndef to D

On Friday, 13 May 2016 at 06:05:14 UTC, Andrew Edwards wrote: Additionally, what's the best way to handle nested #ifdef's? Those that appear inside structs, functions and the like... I know that global #ifdef's are turned to version blocks but versions blocks cannot be used inside classes,

Re: imports && -run [Bug?]

On Friday, 13 May 2016 at 01:16:36 UTC, Andrew Edwards wrote: command: dmd -run mod inc output: Undefined symbols for architecture x86_64: "_D3inc5printFZv", referenced from: __Dmain in mod.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit

Re: Request assistance converting C's #ifndef to D

On 5/13/16 7:51 AM, Andrew Edwards wrote: The following preprocessor directives are frequently encountered in C code, providing a default constant value where the user of the code has not specified one: #ifndef MIN #define MIN 99 #endif #ifndef MAX #define MAX

  1   2   >