On Friday, November 25, 2011 5:30:40 PM UTC, doyen...@gmail.com wrote:
>
> I was not trying to make any claims. My link was only for those that
> are not aware of
> JNA and usually make the claim that JNI is the only way.
I'm sorry if I offended you.
If you would have posted the above explanatio
On Nov 25, 2011 10:18 AM, "rjf" wrote:
>
> We could always continue this discussion on sage-flame.
Please do. This thread should be about Mathematica and the extent to
which their claim to have a compiler for arbitrary Mathematica programs is
actually true.
William
> I think that persons who
On Nov 25, 2011 9:30 AM, "Alfredo Portes" wrote:
>
> I was not trying to make any claims. My link was only for those that
> are not aware of
> JNA and usually make the claim that JNI is the only way.
>
> But I appreciate your message as it reminds me of how welcoming this list
is.
> No WTFs needed
I was not trying to make any claims. My link was only for those that
are not aware of
JNA and usually make the claim that JNI is the only way.
But I appreciate your message as it reminds me of how welcoming this list is.
No WTFs needed, ignore me, and like Ted Kosan I am out of here.
On Fri, Nov
Thanks for your well-thought out contribution. I'm sure you are aware that
JNA, although it sucks slightly less than JNI, doesn't support C++. So its
back to writing C stubs to use instances from one object-oriented language
in another object-oriented language. WTF!
On Friday, November 25, 2011
Sage-devel was so nice for the last few months with out Richard Fateman
FUD...
On Nov 25, 2011 8:13 AM, "rjf" wrote:
>
> re: writing stubs to access C (etc) libraries from Lisp.
>
> There are several lisp programs which will take your *.h files and
> attempt to
> automatically write all the stubs
On Thu, Nov 24, 2011 at 9:25 PM, rjf wrote:
>
> William seems to prefer to tout the Sage-Cython link.
That's because we use Cython, and it's easy to use in Sage, and
provides a fully-functional language-native interface between Cython
and Sage. Not a single part of that is true about the Maxima
On Fri, Nov 25, 2011 at 7:29 AM, Volker Braun wrote:
> I think thats the actual advantage of Cython. Every interpreter can dload a
> library somehow. But try to mix a shared library, some custom C++ code, and
> the interpreter of your choice. In any commercial Ma* or Java JNI you'll
> invariably
On Friday, November 25, 2011 10:33:24 AM UTC, Robert Bradshaw wrote:
> Note that another selling point of Cython is not just writing new
> (fast) code, but interfacing with existing low-level libraries in a
> clean way.
>
I think thats the actual advantage of Cython. Every interpreter can dload
On Wed, Nov 23, 2011 at 2:16 PM, rjf wrote:
>
> Maxima compiles code to binary, and has done so, oh for a couple of
> decades.
>
> Since Maxima is part of Sage, one might hope that William would be
> aware of this feature.
In the spirit of being mutually informative, here's how it's done in Sage
On Nov 24, 2011 4:56 AM, "Simon King" wrote:
>
> On 23 Nov., 23:16, rjf wrote:
> > Maxima compiles code to binary, and has done so, oh for a couple of
> > decades.
>
> Is Maxima considered to be in the class "Ma*"? I thought the
> definition of "Ma*" is: Name starts with "Ma" and code is closed
>
11 matches
Mail list logo
