On Saturday, September 29, 2018 at 3:46:41 PM UTC+2, Robert Engels wrote: > > Your description makes no sense. Why are you creating another C thread, > you should just lock the OS thread the Go routine is on. Otherwise if you > create another C thread, in the cgo call you need to block that thread or > somehow communicate back into Go some other way - otherwise what is the > point? >
As I mentioned on the top floor, I am migrating a very old pure C project to Go, and eventually become a pure Go project. the original project was linked by different components, and I am replacing them one by one... I know it doesn't make sense (apparently, before creating a non-Go thread, there are some internal preprocessing they are irrelevant to Pango) but to archive what you describe (in one goroutine) will consume loads of time for reading, understanding, and implementation, time is limited. -- 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.
