[sage-devel] Computing Automorphism Groups of Error-Correcting Codes Software

2007-03-14 Thread Pere Urbón-Bayes
Dear Dr. Jeffrey Leon, my name is Pere Urbón-Bayes [0] and I'm an Spanish Software Engineer. Since I was with a research group at the Autonomous University of Barcelona [1] doing some developments on error correcting codes theory I'm so interested on it. Now I'm contributing with a free software

[sage-devel] Re: A menu for the notebook

2007-03-14 Thread boothby
I like the simplicity of it... I ran something like this by William once before, and he objected citing Tish's dislike of dropdown menus. What do other people think of this? On Fri, 9 Mar 2007, Timothy Clemans wrote: > > I have created a menu for the notebook that would be helpful. I really

[sage-devel] Re: SageX and C++ and pass-by-reference

2007-03-14 Thread Martin Albrecht
> My question, what's the most sensible way to call my C++ > function 'do_something_with_a_reference' that takes a reference parameter? > I came up with a clever hack -- put the following in your .pxd file: cdef > extern from "NTL/ZZ.h": > ZZ ZZ_deref "*"(ZZ *z) > and then your function becom

[sage-devel] SageX and C++ and pass-by-reference

2007-03-14 Thread Joel B. Mohler
This question is probably mostly for Martin. I observe that SageX doesn't know what to do with something like the following declaration: cdef do_something( ZZ &x ): do_something_with_a_reference( x, 1 ) This is presumably because the "&" is a C++ syntactic sugar and pyrex only does C.

[sage-devel] Re: Strange inconsistency

2007-03-14 Thread Michel
Thanks you very much. I had looked on http://sage.math.washington.edu/sage/hg/sage-main/file/1f3dd6372b47/sage/rings/integer_mod_ring.py and your patch wasn't there yet. So I assumed the problem was still open. Regards, Michel On Mar 14, 9:00 am, David Harvey <[EMAIL PROTECTED]> wrote: > Hi

[sage-devel] Re: Strange inconsistency

2007-03-14 Thread David Harvey
Hi Michel, you are correct, actually I already fixed it but I forgot to reply to the list. The fix will be in the next release of sage. Your solution is fine; we actually ended up with something slightly different for efficiency reasons, you can grab the patch if you like from http://sage.mat