Another amusing quote, this time from the sbrk man page on macOS: > The brk and sbrk functions are historical curiosities left over from > earlier days before the advent of virtual memory management.
That seems to be a paraphrase of the FreeBSD man page, which says: > The brk() and sbrk() functions are legacy interfaces from before the advent of modern virtual > memory management. They are deprecated and not present on the arm64 or riscv architectures. > The mmap(2) interface should be used to allocate pages instead. Given that GAP runs on arm64, I suspect that it doesn't use sbrk in an essential way anymore. Of course fork is a different story. But there are surely lots of examples of programs that use fork which have been ported to Windows. I would guess that emacs is among them. (It has been ported to Windows - I assume it uses fork on posix systems). - Marc On Thursday, April 25, 2024 at 9:03:30 AM UTC-5 Marc Culler wrote: > On Thursday, April 25, 2024 at 8:28:48 AM UTC-5 Dima Pasechnik wrote: > > Essential components of sagelib such as GAP, Singular, don't run on > native Windows > > > I was amused to find the following statement on the GAP forum > <https://www.gap-system.org/ForumArchive2/2005/000999.html> from 2005: > > > While porting GAP to use native Win32 calls is doable, basically > src/system.c is the only place > > that needs lots of changes, it is certainly a nontrivial and > time-consuming task. (and one needs > > to be a bit of an expert in programming to do this, IMHO) > > The author was someone from the Netherlands by the name of *Dima > Pasechnik. :^)* > > - Marc > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/0fad0dee-9a92-40f3-854a-412acca934e1n%40googlegroups.com.
