Re: [Felix-language] Os abstraction model

2012-04-29 Thread john skaller
On 30/04/2012, at 8:38 AM, Jeff Schultz wrote: > On Fri, Apr 27, 2012 at 02:50:15PM +1000, john skaller wrote: >> We should note here: Felix provides two kinds of platform independence. >> Some things are done by C++ conditional compilation or link time >> library selection. This means the genera

Re: [Felix-language] Os abstraction model

2012-04-26 Thread john skaller
Ok, so what I'm doing is this: Files: std/filestat std/posix/filestat std/win32/filestat classes: +++ std/filestat: = class FileStat_class[os, ..others] { virtual ... } include "std/posix/filestat"; include "std/win32/filestat"; // default to Host OS class class FileStat {

Re: [Felix-language] Os abstraction model

2012-04-25 Thread john skaller
On 26/04/2012, at 3:21 AM, Raoul Duke wrote: > seems like the kind of thing you can't get right from the get-go? Not enough use cases to generalise. > trying to figure out, as it sounds like you are doing, a flexible > layout for things so that it can be externalized in libraries and so > that

Re: [Felix-language] Os abstraction model

2012-04-25 Thread Raoul Duke
seems like the kind of thing you can't get right from the get-go? trying to figure out, as it sounds like you are doing, a flexible layout for things so that it can be externalized in libraries and so that people can revamp them over time to improve things, that would be a nice ground to gain? (try

[Felix-language] Os abstraction model

2012-04-24 Thread john skaller
Now we're trying to get stuff working on Windows, we need a model for portable code. Note there's a trickiness needed here: a) Cygwin can do both posix and windows functions, so it may not be "one or the other" b) We still need to write platform specific code c) All OS .. especially posix .. hav