On Tuesday, December 11, 2012 5:32:25 AM UTC, rjf wrote:
>
> I recommend reading up on the Axiom computer algebra system
> about structuring code around mathematical categories.
>
Or you could read up on the sage devel mailing list a couple of years back.
The Sage categories are modeled after Mu
I recommend reading up on the Axiom computer algebra system
about structuring code around mathematical categories.
Been there, done that.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googleg
Thank you for the extensive explanation. It clarifies things I obviously
didn't understand...
sage.categories.pushout is the most relevant part for what I was trying to
ask.
Paul
On Wednesday, November 28, 2012 2:31:06 PM UTC+1, Simon King wrote:
>
> Hi Paul,
>
> On 2012-11-28, Paul-Olivier Deh
On Wed, Nov 28, 2012 at 2:59 AM, Paul-Olivier Dehaye
wrote:
>>
>> > change "To coerce from the category down to the parent" --> "To coerce
>> > from
>> > the abstraction layer to the parent". In this abstraction layer (which
>> > is
>> > close to the categories now available, but not quite the sam
Hi Paul,
On 2012-11-28, Paul-Olivier Dehaye wrote:
>> > change "To coerce from the category down to the parent" --> "To coerce
>> from
>> > the abstraction layer to the parent". In this abstraction layer (which
>> is
>> > close to the categories now available, but not quite the same),
I stil
>
>
> > change "To coerce from the category down to the parent" --> "To coerce
> from
> > the abstraction layer to the parent". In this abstraction layer (which
> is
> > close to the categories now available, but not quite the same), we would
> > have a list of methods for the parent class an
On 2012-11-27, Robert Bradshaw wrote:
>> A while ago, I have created a public worksheet on "how to implement
>> basic algebraic structures in Sage", using category framework and coercion.
>> I think at some point it was supposed to become part of the
>> documentation, but I think we lost momentum.
On Mon, Nov 26, 2012 at 2:43 PM, Paul-Olivier Dehaye
wrote:
> My impression is that Sage's directory structure tries to address different
>>
>> concerns (meaning here: different mathematical topics). Do you think
>> that the present directory structure does not succeed to keep different
>> concern
On Mon, Nov 26, 2012 at 6:34 AM, Simon King wrote:
> Dear Paul-Olivier,
>
> On 2012-11-26, Paul-Olivier Dehaye wrote:
>> My understanding of aspect-oriented programming in general: encourages the
>> developer to realize that there are several concerns that will be present
>> in a large project, a
My impression is that Sage's directory structure tries to address different
> concerns (meaning here: different mathematical topics). Do you think
> that the present directory structure does not succeed to keep different
> concerns apart?
>
Here are a few folders in the main folder:
- datab
Dear Paul-Olivier,
On 2012-11-26, Paul-Olivier Dehaye wrote:
> My understanding of aspect-oriented programming in general: encourages the
> developer to realize that there are several concerns that will be present
> in a large project, and to organize the project in such a way to minimize,
> a
My understanding of aspect-oriented programming in general: encourages the
developer to realize that there are several concerns that will be present
in a large project, and to organize the project in such a way to minimize,
at any location in the code, the number of concerns whose concrete
impl
12 matches
Mail list logo
