agemogolk/clay — comment on commit 3d4539e5978305cc6f670101077addb4a5b3ff6d
File:  line 0
By agemogolk:

My strategy there was pretty simple - look at the llvm D language
compiler (ldc) and do it the same way. I've been using the complex types
extensively in the linalg library and my laplace inversion codes and
have had no problem. Haven't tried it on other hardware yet though. I do
have a macbook knocking around so i'll make it work on that when time
permits. Probably try to get Clay running on some bigger hardware at
the Uni I work at to run some of my modelling stuff and see what breaks
. . .

I do wonder, what does Clay have in-store for the future? Apart from
yourself and a couple of others I don't see much development activity.
As a language it suits my needs (and preferences) very well, would be
nice to see it stay afloat. I have an interest in parallel/concurrency
and am currently tinkering with a basic coroutines library (blatantly
ripped off some early development C code knocking around the net).

On 04/11/11 03:05, Joe Groff wrote:
> The compiler changes look good. The compiler's not the easiest code to work with. But I wonder if there are ABI issues with the complex types—I know on x86-64 at least, `_Complex` behaves a bit differently from a struct of two floats.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/agemogolk/clay/commit/3d4539e5978305cc6f670101077addb4a5b3ff6d#commitcomment-694643