>
> Go can often completely replace C++ unless you have existing C/C++ 
> libraries that you need to use.


Well that's exactly my main issue and more.
If Go can replace C++ by offering the same performance, then developing new 
code in C++ would be a waste of time.
It would be preferable to migrate old C++ code into new Go code, while 
implementing new code already in Go.
This means, developing code in both languages could be kinda disruptive. 
I'm trying to find a reason to keep both languages in play.


On Sunday, 23 October 2016 07:05:57 UTC+1, Ian Lance Taylor wrote:
>
> On Sat, Oct 22, 2016 at 7:39 PM,  <carlo...@gmail.com <javascript:>> 
> wrote: 
> > C++ is evolving. C++14 is out and used in production. C++17 is almost 
> ready. 
> > 
> > I want to invest some time in goLang, mainly because I wanted to 
> substitute 
> > Python with a more efficient language for quick prototype 
> implementation. 
> > Also, goLang seems to be interesting for services were performance is 
> > important, but where the time to develop a service is also short. 
> > But because it seems that goLang is quite efficient (near C 
> performance), 
> > I'm just wondering... 
> > 
> > Can C++ and goLang coexist in the same service development ecosystem 
> within 
> > a company. 
> > Does it makes sense to have people developing services and applications 
> in 
> > C++ and goLang, with portability in mind? 
> > Can goLang completly substitute C++? 
>
> Yes, C++ and Go can coexist.  Go code can call into C++ using cgo 
> (requires a pure C interface) or SWIG.  C++ code can call into Go code 
> by building your Go code with -buildmode=c-archive or 
> -buildmode=c-shared. 
>
> Go can often completely replace C++ unless you have existing C/C++ 
> libraries that you need to use. 
>
> Ian 
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to