Dear Ian Lance Taylor,
thankyou very much for your hint!
Kind regards, Christian
Am Mittwoch, 2. Oktober 2019 04:36:4D8 UTC+2 schrieb Christian Maurer:
>
> Dear community,
>
> what is wrong with the following simple code, which yields "undefined
> reference for F" ?
>
>
> file f.go:
>
> package
Dear Ian Lance Taylor,
thankyou very much for your hint!
Kind regards, Christian
--
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...@googleg
Dear community,
what is wrong with the following simple code, which yields "undefined
reference for F" ?
file f.go:
package main
// #include "f.h"
// void f (int a) { F(a) }
import "C"
func F(a int) { println(a) }
func main() { C.f(7) }
file f.h:
extern void F (int a);
//export F
Thanks
Dear Community and dear Go-developers,
Meanwhile it is clear why things do not work:
The Go-Scheduler is unable to allow to switch to another goroutine in
busy-waiting-loops -
the only possibility to get around that problem is either to put
"switch-steps" into the source
- either "time.Sleep(1)"
Dear Go-community,
I noticed a very strange effect by translating the
mutual exclusion algorithm of E. W. Dijkstra to Go.
Reference:
Cooperating Sequential Processes. Technical Report EWD-123,
Technological University Eindhoven (1965)
http://www.cs.utexas.edu/users/EWD/ewd01xx/EWD123.PDF)
I
