Re: [PHP4BETA] What is ext/lcg/lcg.c?

> MM is currently UNIX specific (as far as I recall, it's shared memory > based). You might be able to emulate its behavior under Win32 or a > multithreaded environment, you might not. mm works fine in multithreaded environments. Before you judge something the next time, inform yourself. > Either way, until you do, it's > platform specific (whether you use a platform specific function or a > platform specific library that may or may not be ported later on doesn't > make much of a difference; Everything can be ported or emulated, it > doesn't mean its done). > > My rule of the thumb here is simple - if something works under most unices > and Win32, it's platform independent. That is a very limited world view. As far as I recall, PHP also runs on OS/2. Therefore, your description doesn't even cover the platforms PHP runs on. Now, argumenting over the market share is another thing. > If it doesn't, it's not. Therefore, > your session code that relies on the UNIX specific MM library is platform > dependent, as it would not work under Win32 (and perhaps not on > multithreaded UNIX platforms, not sure about that though). It doesn't mean > you shouldn't use it in your session module - but it does mean it shouldn't > be encouraged and introduced as a part of PHP's infrastructure for module > development. We should encourage what PHP helps to gain momentum. My point is that the session code is completely portable. It does not rely on any platform specific calls or libraries to work. The sentence "your session code that relies on the UNIX specific MM library is platform dependent" is completely bogus. That does not say anything but "if a, then a" where a is platform dependence. But of course, the session module works just fine without mm. -- Regards, Sascha Schumann Consultant