In our previous episode, Bart said: [ Charset ISO-8859-1 unsupported, converting... ] > On 3/20/09, Marco van de Voort <mar...@stack.nl> wrote: > > A plugin is the more logical route, for the ones that want to remain libc > > free, but want to risk maintainance problems. > > Like an fplocale unit, that users can include if they do not want to > use clocale?
Yes, I don't see a problem with that, if the quality is suitable. (read: the code quality is good and multiplatform). I won't accept a linux own package, see http://wiki.freepascal.org/libc_unit#But_I_only_want.... for a rationale. > > Are they guaranteed default installed on most OSes ? > Probably not... > > ... It's pretty hard to > > parse something that is not there. > If it's not there, there's nothing to parse, so the code would exit > immediately at that point. Nothing would get broken (more than it is > now): formatsettings would remain the same as before trying to > localise them (as they are now). It is not a problem for a plugin unit (though it makes it less generically appliable, and more a specialism). I was talking about the default situation, where such empty attempts are not acceptable, because it has the potential to totally break a FPC release. _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
