Hello, FPC developers' list

Please explain why clocale must be included as a separate unit to the project?
Why not include it into unix sysutils?
Can we freely use it in lazarus or we can get problems?

Best regards,
Paul Ishenin.

Paul Ishenin wrote

Hello, FPC developers' list Please explain why clocale must be included as a separate unit to the project? Why not include it into unix sysutils?

Because we don't want a FPC binary to depend on Libc by default. All LibC dependencies are optional.

If Graeme Geldenhuys finds the time, he'll code a native Object Pascal replacement for the clocale unit. That replacement could go in SysUtils.
(that is, he said he'd give it a try)

Can we freely use it in lazarus or we can get problems?

Lazarus should not be a problem, because you always use the C library anyway since you are connecting to X via the X client libs...

Michael.

In our previous episode, Paul Ishenin said:

Please explain why clocale must be included as a separate unit to the project? Why not include it into unix sysutils?

It uses the libc library. Same reason as cthreads, cwstring etc. It also allows the user to override basic locale initialization and substitute it with its own.

Can we freely use it in lazarus or we can get problems?

Similar as for the units above: Lazarus already uses library libc.

In our previous episode, Michael Van Canneyt said:

If Graeme Geldenhuys finds the time, he'll code a native Object Pascal replacement for the clocale unit. That replacement could go in SysUtils. (that is, he said he'd give it a try)

(IMHO that should be optional too, since contrary to other 0-implementations that are overridable, they will probably be large or require extra files. User should be able to skip that)

And yes, it's still on my todo list and slowly moving it's way to the top. :-)

Regards,
- Graeme -

_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/