Re: [AOLSERVER] Win mmap()

2004-08-17 Thread Jamie Rasmussen
This one brings the question: why not go and abstract other #ifdef's arround the code? Perhaps adding a compat or win/unix or such directory with platform-specific stuff a'la Tcl? I'm not sure how bit that effort is, but is worth examining since it will ease the server maintenance greatly. AOL is

Re: [AOLSERVER] Win mmap()

2004-08-17 Thread Nathan Folkman
[EMAIL PROTECTED] wrote: This one brings the question: why not go and abstract other #ifdef's arround the code? Perhaps adding a compat or win/unix or such directory with platform-specific stuff a'la Tcl? I'm not sure how bit that effort is, but is worth examining since it will ease the server

Re: [AOLSERVER] Win mmap()

2004-08-17 Thread Nathan Folkman
[EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: This one brings the question: why not go and abstract other #ifdef's arround the code? Perhaps adding a compat or win/unix or such directory with platform-specific stuff a'la Tcl? I'm not sure how bit that effort is, but is worth examining since it

Re: [AOLSERVER] Win mmap()

2004-08-17 Thread Zoran Vasiljevic
On Tuesday 17 August 2004 20:17, you wrote: To maximize portability, AOLserver could probably use the Tcl API even more than it does now, and in a few cases modules aren't taking advantage of the portability abstractions we already have, for example, in the latest nsopenssl sources, struct