Hi Uz, > Hm, we're discussing since several years the lack of opendir() and > friends > > on CBM. Wouldn't it be the "right" solution to finally include those > and > > re-designate cbm_opendir() to CBM-specific functionality as its name > > implies? > > These are actually two only marginally connected problems. While it is for > sure worthwhile to have opendir() for the CBMs, there are still good > reasons > to have cbm_opendir handle pattern matching for files. The standard POSIX > opendir() function doesn't allow for a file name pattern by definition. > Sorry for obviously being such mistakable: Exactly _because_ opendir() can't provide the functionality asked for here it makes sense to provide that functionality with cbm_opendir() - and not with cbm_opendir2(). Or to put it in other words: I'd consider three different functions for dir handling as overkill / undesirable. And with opendir() wanted for sure there's only room for one additional function. So there's no reason to not name that second function cbm_opendir() - totally independent from it's signature. Regards, Oliver ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Mon May 28 16:37:59 2012
This archive was generated by hypermail 2.1.8 : 2012-05-28 16:38:03 CEST