From 125feb6da0060d8a693cac6c6b3199980b26231a Mon Sep 17 00:00:00 2001 From: jkniiv Date: Sat, 9 Jul 2022 11:31:11 +0000 Subject: [PATCH] I should use the correct term --- ...ows__58___prepare_for_Win32_not_export_c__95___entities.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/todo/windows__58___prepare_for_Win32_not_export_c__95___entities.mdwn b/doc/todo/windows__58___prepare_for_Win32_not_export_c__95___entities.mdwn index fcf313c0cb..73b2b454b3 100644 --- a/doc/todo/windows__58___prepare_for_Win32_not_export_c__95___entities.mdwn +++ b/doc/todo/windows__58___prepare_for_Win32_not_export_c__95___entities.mdwn @@ -47,7 +47,7 @@ But according to Joey that is undesirable for a lockfile implementation (.\Utili ``` -So what to do when the authors of module Win32 pull the rug from under you? Should we perhaps weave +So what to do when the authors of package Win32 pull the rug from under you? Should we perhaps weave our own tiny c_CreateFile API with FFI, or, could we do without it and use one of the implementations using Windows LockFileEx, for instance the one by my compatriot: