TID: Mystic BBS 1.12 A46   
   MSGID: 3:770/100 1a579cfe   
   REPLY: 1:153/7715.0 005b8de0   
   TZUTC: 1300   
   On 18 Jan 2021 at 08:34a, Dallas Hinton pondered and said...   
       
    DH> Hi, Dan -- on Jan 19 2021 at 03:11, you wrote:   
    DH>    
    DH> DC> A couple of things, but the biggest one I can think of is fragility   
    DH> DC> in the face of system crashes.  In particular, who's responsible for   
    DH> DC> cleaning this file up?  Should `binkd` delete it as part of gracefully   
    DH>    
    DH> FWIW, I have a batch file that runs on startup and deletes all semaphore   
    DH> flags. They're all in the same directory so it's easy.   
      
   Yeah, that's _a_ design, but doesn't really address the   
   question.  The program author still has to make some kind   
   of design decision about what to do if the file exists   
   when the program starts up (suppose someone starts it   
   directly, without running the script that deletes the files   
   ahead of time?).   
      
   More generally, the issue in this discussion is that the   
   request for a feature has been wrapped up in details about   
   the implementation of that feature.  From my observation,   
   that's the central source of friction.   
      
   --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)   
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)   
   SEEN-BY: 1/123 57/0 90/1 103/705 105/81 120/340 123/131 124/5016 129/305   
   SEEN-BY: 153/250 154/10 203/0 220/50 70 221/0 226/17 30 227/114 229/100   
   SEEN-BY: 229/101 200 424 426 550 664 1016 1017 240/5832 249/109 110   
   SEEN-BY: 249/206 307 317 267/800 280/464 5003 5555 288/100 292/854   
   SEEN-BY: 292/8125 310/31 317/3 322/757 340/1000 342/200 396/45 423/120   
   SEEN-BY: 460/58 633/280 712/848 770/0 1 100 340 772/0 1 210 220 230   
   SEEN-BY: 2452/250   
   PATH: 770/100 1 280/464 229/101 426