11–20 of 187 posts
Almost like the way D programming language handle it http://dlang.org/module.html
http://dl.rust-lang.org/doc/tutorial.html#modules-and-crates
Browsed golang.org for a bit and didn't find any info on how Go handles modules/packages. All I know is that it has something to do with the folder hierarchy of your project (links appreciated).
long overdue indeed, reminds me a lot of google go?
Almost like the way D programming language handle it http://dlang.org/module.html
For completeness, here's how Rust handles modules: http://dl.rust-lang.org/doc/tutorial.html#modules-and-crates Browsed golang.org for a bit and didn't find any info on how Go handles modules/packages. All I know is that it has something to do with the folder hierarchy of your project (links appreciated).
Everyone wants modules but nobody can agree on how they should behave. This is why they weren't included in C(++)11.
"Apple's Module proposal..." Is Apple really who deserves credit here? Is there something I missed about Apple's management driving this, and not Gregor or the C++ standards committee?
Earlier quoted context omitted.
For completeness, here's how Rust handles modules: http://dl.rust-lang.org/doc/tutorial.html#modules-and-crates Browsed golang.org for a bit and didn't find any info on how Go handles modules/packages. All I know is that it has something to do with the folder hierarchy of your project (links appreciated).
in Go, you declare a package for your file. Exported symbols start with an upper case letter.
Since these are not in C++11, we'll have to wait 10 years...
Everyone wants modules but nobody can agree on how they should behave. This is why they weren't included in C(++)11.
Speaking as someone who doesn't follow the development of those specs, can you elaborate? What behaviors are contentious?
http://channel9.msdn.com/Events/GoingNative/GoingNative-2012...