That must have been a long time ago? That problem was solved well
before I left the C++ committee in '99 and gcc was normally pretty
good at tracking the emerging standard at the time...

But, yes, the template compilation model and it's impact on linking
modules that specialized the same template had been problematic
earlier on.

On Sun, Dec 29, 2013 at 2:30 PM, Cedric Greevey <cgree...@gmail.com> wrote:
> (Incidentally, it was template woes that eventually broke the camel's back
> for me with C++. I gave up on C++ when I found that one of the most
> widely-used free software C++ compilers would give duplicate definition
> errors at link time if the same template was used with the same parameters
> in two separate compilation units, and the developers had *no sane fix or
> workaround* or even an ETA on a fix...imagine if importing java.util.Map and
> using Map<String,Integer> in Foo.java and also importing java.util.Map and
> using Map<String,Integer> in Bar.java and then running something using both
> classes Foo and Bar had resulted in linkage errors instead of two classes
> coexisting at runtime that both used Map<String,Integer>s. Java 1.5 would
> have never gotten off the ground! But this C++ compiler -- and yes, it was
> then-current gcc -- would do exactly that if you #included hash_map and used
> hash_map<const char *,int,some_string_hashfn,strcmp> in two compilation
> units.)

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to