> From: "Sandro Magi" <[EMAIL PROTECTED]>
> On 7/10/07, Rhythmic Fistman <[EMAIL PROTECTED]> wrote:
> > > > There's some support for async disk file I/O, but really
> > > > Linux can't do this so it's fairly pointless.
> >
> > Win32 felix happily uses TransmitFile. That looks like async file io
>
On 7/10/07, Rhythmic Fistman <[EMAIL PROTECTED]> wrote:
> > > There's some support for async disk file I/O, but really
> > > Linux can't do this so it's fairly pointless.
>
> Win32 felix happily uses TransmitFile. That looks like async file io
> to me, or at least async file -> socket. I don't see
On 7/10/07, skaller <[EMAIL PROTECTED]> wrote:
>
> HOF aren't necessarily slow. Try this program with
I'm not really concerned about speed. And your example is neat by the way. :-)
HOF are really needed when one needs abstraction. I'm just saying that
I suspect that the abstraction won't be neede
> From: skaller <[EMAIL PROTECTED]>
> Felix __can__ be twice as fast as C .. :)
I've never been comfortable with this statement, because seeing
as felix's output IS a C programme it's its own competitor hence
felix can be __exactly__ as fast C. It would be fairer to say that felix's
unorthodox ma
On Tue, 2007-07-10 at 10:31 +0200, Rhythmic Fistman wrote:
> > From: skaller <[EMAIL PROTECTED]>
>
> > Felix __can__ be twice as fast as C .. :)
>
> I've never been comfortable with this statement, because seeing
> as felix's output IS a C programme it's its own competitor hence
> felix can be __
> From: "Sandro Magi" <[EMAIL PROTECTED]>
> > Felix comes with a high performance platform independent
> > asynchronous I/O subsystem: works with sockets mainly,
> > but RF (the author) is playing with Unix pipes and some
> > other stuff.
>
> Excellent! :-)
I think that stuff just works on the un
> From: skaller <[EMAIL PROTECTED]>
> The Felix GC itself is split into an abstract class and
> an implementation, and the allocator likewise is a separate
> abstract class and implementation.
>
> The standard allocator implementation is malloc-free.
That is it uses malloc and malloc's counterpart
On Mon, 2007-07-09 at 16:27 -0400, Sandro Magi wrote:
> > I hope to convince you this isn't necessary.
> >
> > Many people in the games world think dynamic allocation
> > and garbage collection are evil.. in fact this is rot.
>
> Well, I don't think it's "evil"; I quite like it actually. I'm just
Off-list discussion taken back on-list.
On 7/9/07, skaller <[EMAIL PROTECTED]> wrote:
> On Mon, 2007-07-09 at 12:03 -0400, Sandro Magi wrote:
> > Ok, I think we're on the same page now. I think you'll agree that if
> > (2) allocates resources that survive its own execution, those need to
> > be bo
On Sun, 2007-07-08 at 15:07 -0400, Sandro Magi wrote:
> I'm looking into creating a VM for a language I'm building, and was
> going to base it on LLVM which is written in C++. I'd rather not have
> to deal with C++ though,
me either .. :)
> and since Felix can natively integrate with
> C++ with
I'm looking into creating a VM for a language I'm building, and was
going to base it on LLVM which is written in C++. I'd rather not have
to deal with C++ though, and since Felix can natively integrate with
C++ with much stronger typing, I'm wondering whether it would be a
good fit for this applica
11 matches
Mail list logo
