Re: #ifdef cruft in Go/Rust

2021-06-20 Thread Daniel Franke via devel
Rust uses cfg attributes for most such things. https://doc.rust-lang.org/rust-by-example/attribute/cfg.html On Sun, Jun 20, 2021, 21:12 Hal Murray via devel wrote: > > How do Rust and/or Go handle the cruft that C coders use #ifdefs for? > > Does that just get pushed down to a C library? > > >

#ifdef cruft in Go/Rust

2021-06-20 Thread Hal Murray via devel
How do Rust and/or Go handle the cruft that C coders use #ifdefs for? Does that just get pushed down to a C library? -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel

Re: Objectives for the next year

2021-06-20 Thread Hal Murray via devel
Richard Laager said: > With the caveat that there is a LOT I don't know in this space, if it was my > call, I'd aim for an incremental conversion of ntpd to Rust and leave the > userspace tooling in Python. After the daemon is converted, I would > re-evaluate whether the userspace tooling shou

Re: Objectives for the next year

2021-06-20 Thread Richard Laager via devel
On 6/20/21 4:45 PM, Richard Laager via devel wrote: I get the impression that Go has a shallower learning curve (i.e. is easier to get started with), which is good, but may unfairly prejudice Go in quick Go-vs-Rust "bake off" comparisons. err... may unfairly prejudice Rust -- Richard

Re: Objectives for the next year

2021-06-20 Thread Richard Laager via devel
On 6/20/21 2:31 AM, Achim Gratz via devel wrote: Eric S. Raymond via devel writes: My choice for a language to move to would be Go. Possibly one of you can argue for a different choice, though if you agree that Go is a suitable target I would find that information interesting. Since the last r

timestamps in Go don't work yet

2021-06-20 Thread Hal Murray via devel
>From the BufferBloat list: https://github.com/golang/go/issues/46831 how to get at udp "cmsg" data for ipv4 and ipv6? The Github response says to go to: https://github.com/golang/go/wiki/Questions Which says: Unlike many projects, the Go project does not use GitHub Issues for general di

Re: PLL (was Re: Objectives for the next year)

2021-06-20 Thread Achim Gratz via devel
Hal Murray via devel writes: > e...@thyrsus.com said: >> I did. There's a blog post about it: >> https://blog.ntpsec.org/2017/02/22/testframe-the-epic-failure.html > > From there: >> One was what in discussion on the mailing list I later tagged "the code-path >> split". There are two kinds of NTP

Re: Objectives for the next year

2021-06-20 Thread Achim Gratz via devel
MLewis via devel writes: > Is it worthwhile improving the current C code to a 'hardened' programming > standard? It's always worth trying, but not as easy as it seems. The fun with standard is that there are so many to chose from. > Example > - Joint Strike Fighter standards https://www.stroust

Re: Objectives for the next year

2021-06-20 Thread Hal Murray via devel
Achim Gratz said: > Since the last round of discussion both sides of the argument have been > moving. If you believe that Rust will become a first-class implementation > language for the Linux kernel, that would tip the scales in favor of rust > considerably in my view. Thanks. I just watche

Re: Objectives for the next year

2021-06-20 Thread Achim Gratz via devel
Eric S. Raymond via devel writes: > My choice for a language to move to would be Go. Possibly one of you > can argue for a different choice, though if you agree that Go is a > suitable target I would find that information interesting. Since the last round of discussion both sides of the argument h