> JAT is my personal favorite, but dit does create an other 'JAL' > branche and there is little interest in the result.
In both cases JAT vs JALv2 implementations, they will generate C code. Since it is only C code, the final "result" will be totally dependent on the C compiler. So therefore, the result cannot be exactly the same as JAL in either case. I think you where talking about how some may not be interested in the final product from JAT, but I don't see how it is different then the output of JALv2 implementation. For this reason, both ways are equal except for additional features such as implementing C libraries in JAL. Another suggestion would be to try to work with kyle to put your JAT inside the JALv2 compiler and use command line parameters if you wish to use JAT. You could add a pragma to specify what C compiler you wish to use. Each C compiler can be well tested for same calculations compared to JALv2. Matt. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
