D 2.069.0 released, compiler automatically ported from C++ to D

Post by thepumpkin1979 » Wed, Nov 04, 2015, 4:53 PM UTC

WalterBright wrote: post #54

thepumpkin1979 wrote: post #36

Not sure what I do wrong every time I try D again, I wanted to see the new backtraces worked but I still get: /bin/bash: line 1: 82501 Segmentation fault: 11 ./main while I try to call a method on a null variable, which is not that friendly to newcomers. Sample code: import std.stdio; void main() { Greetings g = null; g.hola(); }

That code won't compile because Greetings is undefined. Hence, you may be running some other program which seg faults.

  $ cat main.d
  import std.stdio;

  class Greetings {
	void hello() {
		writeln("hello");
	}
  }

  void main()
  {
	Greetings g = null;
	g.hello();
  }
  $ dmd -g main.d && ./main
  Segmentation fault: 11
  $ uname -a
  Darwin Johan-Ride-Mac.local 15.0.0 Darwin Kernel Version 15.0.0: Sat Sep 19 15:53:46 PDT 2015; root:xnu-3247.10.11~1/RELEASE_X86_64 x86_64
  $ dmd --version
  DMD64 D Compiler v2.069.0
  Copyright (c) 1999-2015 by Digital Mars written by Walter Bright

Post by thepumpkin1979 » Wed, Nov 04, 2015, 4:53 PM UTC

Zardoz84 wrote: post #57

thepumpkin1979 wrote: post #36

Not sure what I do wrong every time I try D again, I wanted to see the new backtraces worked but I still get: /bin/bash: line 1: 82501 Segmentation fault: 11 ./main while I try to call a method on a null variable, which is not that friendly to newcomers. Sample code: import std.stdio; void main() { Greetings g = null; g.hola(); }

1) Where is Greetings defined ? 2) Spanish ?

Post by [deleted] » Wed, Nov 04, 2015, 4:57 PM UTC

knocte wrote: post #50

pornel wrote: post #19

Earlier quoted context omitted.

C translates almost 1:1 to Rust, but when converting C++ to Rust you'll run into impedance mismatch between OO hierarchies and traits, and generics being narrower in functionality than templates. In Rust you still can do "clever" things with generics to make them feel like C++, but the rest of the language is still closer to C: errors returned rather than thrown, no inheritance (but the "flat" OO and enums map well t…

> errors returned rather than thrown WHATT??? did they do the same mistake as Go?

Post by pcwalton » Wed, Nov 04, 2015, 5:01 PM UTC

kbenson wrote: post #64

steveklabnik wrote: post #30

Earlier quoted context omitted.

Since 1.0 last May, we have a strong commitment to backwards compatibility as well. Stability should not be an issue any longer.

GP is actually the second post in a week I've seen where someone mentions tracking rust changes, but rust has been 1.0 for a while now. Have there actually any backwards incompatible changes since 1.0, or are people really complaining about a problem that's been fixed for close to six months and even then was specific to beta versions?

Post by WalterBright » Wed, Nov 04, 2015, 5:05 PM UTC

yokohummer7 wrote: post #56

WalterBright wrote: post #52

Earlier quoted context omitted.

> It still has implicit numeric cast, Implicit numeric casts that lose bits are not allowed anymore. > exception unsafety ??

> Implicit numeric casts that lose bits are not allowed anymore. That's good to hear, but I want implicit conversion to be forbidden unconditionally (even int * float -> float). I've been bitten by even widening conversions, so I just want to let them go away. It might be great if such an option could be applied to module level. > ?? Sorry if my understandings or my words were wrong, but I got the impression that D a…