Hi all, I was filling in the "Module (chicken process)" wiki page for the new manual, and noticed something peculiar:
current-process-id and parent-process-id are in (chicken process-context), but process-group-id and its related setter, and create-session are in (chicken process). This seems... wrong. I think it makes most sense to put them all in process-context, but it might be slightly inconvenient that these are in a different module from process-fork and friends. But given that most/all of them are clearly related to the current process context, I think (chicken process-context) is the best place for them. I noticed that the procedure signature for create-pipe, process-execute, process and process* on Windows are different than on Unix. There is an additional optional argument for each of those, while on Unix we'll get an error if we pass this extra argument. I think it makes sense to have the signature the same everywhere, just having the extra args ignored on Unix. That makes it easier to write portable programs without cond-expand, and it makes for sane types.db entries (right now it has only the Unix versions). What do you all think? Cheers, Peter
signature.asc
Description: Digital signature
_______________________________________________ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers
