Shachar Shemesh wrote:
It's not that I am for adding everything inline. That's not a good idea. Also, I think a Windows compatibility layer can be forgiven for having more dependancies than a personal finance program. This holds especially true if non-core windows functionality is only available if the external library is available at runtime (i.e. - no fribidi install - no Hebrew support in Wine. No CUPS installed - no printing available etc.). I'm not sure this holds true to something which is a core Windows function.
That would be the plan. No FAM header at compile time, no change notification support (i.e. current behavior); can't load FAM library or connect to FAM daemon at runtime, no change notification support.
Hi,
Personally, I think it would be better to use fcntl(F_NOTIFY), then fallback to FAM and finally no change notification. BSD can allways implement it natively too.
Put it this way: if we believe 90% of Wine users are using Linux, and %50 of users have FAM, then it would be logical to use F_NOTIFY instead of FAM, so that it works for most users with no effort on their half.
Mike
Ian Pilcher wrote:
That would be the plan. No FAM header at compile time, no change notification support (i.e. current behavior); can't load FAM library or connect to FAM daemon at runtime, no change notification support.