On Sun, Feb 16, 2020 at 12:11 AM Andreas Otto <aotto1968z...@gmail.com> wrote: > > Ok, but that has massive consequences: > > 1. in order to bridge this, the code has to be changed to "cast" -> so the > type safety is lost > 2. or the NULL pointer test is drawn at the top, in the "caller" -> but this > is a MASSIVE change to the existing CODE basis. > 3. In "C" the call of a method is a zero time operation, "GO" seems to test > the pointer for "NULL" -> "time" is needed for this.
When you say a MASSIVE change to the existing CODE basis, as far as I can tell you mean that you can't write Go code that looks exactly like your existing C code. Go is not C, and it is not intended to be C. You should not expect to be able to translate C code to Go code line by line. Translating to Go is already a massive change. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcUZwpXCjThBJD%3DBH%2B1DOh_u6cQPm1%2BL0J47O3Bjb%2BZQfA%40mail.gmail.com.
