On Fri, 03 Nov 2006 13:22:03 -0800, <[EMAIL PROTECTED]> wrote:
>
> pyrage
> sagerex
> sageX
> SAGeXtremelyFastExtensionLanguageScript
> hypersage
I actualy like "sageX" a lot. The "X" suggests speed.
But it also suggests "eXtension" code. And it is easy
to say and remember.
William
--~--~---
I think if you are really making a fork of pyrex, that non-SAGE users
might want to use (I think they most defenitely will as it has so many
improvements), you should name it something that
i) lets people know that it is useful outside of SAGE
ii) provides some indication of it origin
On 11/3/
pyrecs? pyreks?psyrex?(where the s is for SAGE).Of course this would mean that we would call pyrexc pyrecsc or pyreksc which is sort of incomprehensible. This also has the disadvantage of being a homonym with pyrex. I'm trying to think of a glassware-related pun that would be appropriate...
On 11/3
pyrage
sagerex
sageX
SAGeXtremelyFastExtensionLanguageScript
hypersage
On Fri, 3 Nov 2006, David Harvey wrote:
>
>
> On Nov 3, 2006, at 2:51 PM, William Stein wrote:
>
>> On Fri, 03 Nov 2006 11:42:29 -0800, alex clemesha <[EMAIL PROTECTED]>
>> wrote:
>>
>>> I vote for Spyrex too, not syrex ... t
On Nov 3, 2006, at 2:51 PM, William Stein wrote:
> On Fri, 03 Nov 2006 11:42:29 -0800, alex clemesha <[EMAIL PROTECTED]>
> wrote:
>
>> I vote for Spyrex too, not syrex ... that sounds like some medical
>> device :)
>
> Robert Bradshaw pointed out that Spyrex sounds like *spyware*! Also,
> when
Hmm ... SExtSo you're /really/ going to make a fork of Pyrex?
what about:PyrexS ( pronounced Pyrex - 'S', kinda like My-S-Q-L )or if you want less association with Pyrex, 'SAGext' is fine.-Alex
--~--~-~--~~~---~--~~
To post to this group, send email to sage-
On Fri, 03 Nov 2006 11:42:29 -0800, alex clemesha <[EMAIL PROTECTED]>
wrote:
> I vote for Spyrex too, not syrex ... that sounds like some medical
> device :)
Robert Bradshaw pointed out that Spyrex sounds like *spyware*! Also,
when I say "syrex", I might spit on somebody. Maybe an entirel
On Fri, 03 Nov 2006 11:36:42 -0800, David Harvey
<[EMAIL PROTECTED]> wrote:
>
>
> On Nov 3, 2006, at 1:57 PM, William Stein wrote:
>
>> FYI -- I just made complete nicely documted Pyrex declarations for the
>> entire Python/C
>> API for SAGE (so nobody else do this). They'll be in the
>> deve
I vote for Spyrex too, not syrex ... that sounds like some medical device :)-AlexOn 11/3/06, David Harvey <
[EMAIL PROTECTED]> wrote:On Nov 3, 2006, at 1:57 PM, William Stein wrote:
> FYI -- I just made complete nicely documted Pyrex declarations for the> entire Python/C> API for SAGE (so nobody el
On Nov 3, 2006, at 1:57 PM, William Stein wrote:
> FYI -- I just made complete nicely documted Pyrex declarations for the
> entire Python/C
> API for SAGE (so nobody else do this). They'll be in the
> devel/sage/sage/ext subdirectory
> in the next release, and will make it easy to use any Pyth
On Nov 3, 2006, at 1:57 PM, William Stein wrote:
> Also, since I'm making so many changes to Pyrex, to avoid confusion (or
> making the
> Pyrex author angry) I'm going to call the SAGE branch of Pyrex by the
> name
> "Syrex",
> which means "SAGE Pyrex".
Surely you meant to say Spyrex.
Also, S
11 matches
Mail list logo
