Thanks, This doesn't however really address what I was pointing out. Maybe I was too vague, let me try to clarify.
Suppose you are working on an operating system port of something and you use sys calls. You check the syscall package, the OS docs, and you need to execute a sequence of sys calls of length two. The syscall package supports your sys calls. You follow the OS guidelines. Then, the way things are today, you are STILL not guaranteed that it will work because the runtime might be implemented in a way that uses sys calls which interfere with what you are doing. And the runtime doesn't specify what sys calls it might or might not use. So it is not really a question of whether you are using the syscall package correctly or its organisation w.r.t. operating systems. Scott On Monday, 8 October 2018 13:54:26 UTC+2, Jan Mercl wrote: > > On Mon, Oct 8, 2018 at 1:50 PM Scott Cotton <w...@iri-labs.com > <javascript:>> wrote: > > > However, I wanted to state that if the language doesn't specify this, > and the language also doesn't specify what sys-calls are used on what > platforms in what circumstances, then one can readily conclude that any Go > program that relies on sequences of sys-calls longer than length one is in > fact not guaranteed to work either. > > https://golang.org/doc/go1compat#operating_systems > > -- > > -j > -- 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.
