News for hackers. Stuff that matters.
Re:Why C++ Is Not "Back" by pjmlp on Tuesday December 04, 2012 @08:54AM (#4870877)
> Go is compiled to native code in all major implementations

So is C#, bytecodes are only used as a storage format.

With Microsoft tooling you can JIT at load time, NGEN at installation time, convert to MDIL when uploading to Windows 8 App Store, or convert to pure binary with Bartok in Singularity.

With Mono tooling you can JIT at load time or generate binaries with mono -aot.

With Cosmos OS , it gets compiled to native code.

> This is not true. The level of control you get is extremely limited due to the fact that very few types are values in C#.

Please provide an example where Go compilers offer more control than C# ones.

Re:Why C++ Is Not "Back" by 4ad on Wednesday December 05, 2012 @07:11PM (#4879465)

  type T struct {
  	X, Y P
  	J *Q
  	Z [42]struct {
  		A R
  		W [100]S
  	}
  }
Please note that P, Q, R and S are arbitrary types, not just a subset of value types, and an instance of T is contiguous in memory.
Re:Why C++ Is Not "Back" by pjmlp on Thursday December 06, 2012 @03:26AM (#4880860)
Ah ok, now I understand your point and you're right.

I was actually under the impression that any value type could be used in fixed buffers.

You can however workaround that by using fixed byte buffers with serialization, but it is not so programmer friendly.