Wrapping a code that we cannot ship makes little sense. I say: if we are
going to rewrite it, we better do it as part of the sage library from the
beginning. If the license is not clarified soon, that is the path that i
would follow.
El lunes, 5 de mayo de 2014 14:49:42 UTC+2, Amit Jamadagni es
But the worry is that the maintainer has not given his thoughts on the
subject of license. I know re-writing is altogether at a different level
(keeping in mind the extensive results that Braid program provides), but
considering the advantages like total control (rather than wrapping, with
compiler
Well, we still have the license issue. Without the explicit permission of
the author we cannot distribute a derivative work under the GPL.
El lunes, 5 de mayo de 2014 14:32:36 UTC+2, Amit Jamadagni escribió:
>
> Yes, with some pointers I guess I can pull it off. But re-writing would
> make it se
Yes, with some pointers I guess I can pull it off. But re-writing would
make it set once for all. That is what I think.
On Mon, May 5, 2014 at 5:58 PM, mmarco wrote:
> Amit, how do you feel about that patching? Do you feel capable of doing it?
>
> El sábado, 3 de mayo de 2014 22:29:23 UTC+2, Am
Amit, how do you feel about that patching? Do you feel capable of doing it?
El sábado, 3 de mayo de 2014 22:29:23 UTC+2, Amit Jamadagni escribió:
>
> Hello all,
> We (me under the mentorship of Miguel) have been working on
> the implementation of Knot theory in Sage as a part of GSoC
Hi Marco,
On 2014-05-04, mmarco wrote:
> That sounds a lot like rewriting it.
Why?
> El domingo, 4 de mayo de 2014 17:21:21 UTC+2, Volker Braun escribi=C3=B3:
>>
>> I've actually looked at the code. If we really want to use it we'd really=
>> need to turn it into a shared library, strip out deb
That sounds a lot like rewriting it.
El domingo, 4 de mayo de 2014 17:21:21 UTC+2, Volker Braun escribió:
>
> I've actually looked at the code. If we really want to use it we'd really
> need to turn it into a shared library, strip out debugging code, and
> probably replace the custom bigint libr
I've actually looked at the code. If we really want to use it we'd really
need to turn it into a shared library, strip out debugging code, and
probably replace the custom bigint library with gmp/mpir.
On Saturday, May 3, 2014 10:29:23 PM UTC+2, Amit Jamadagni wrote:
>
> Hello all,
>
>
> Hoping to hear from the community.Thanks.
>
Personally, I would start by stress-testing the code on a variety of inputs
to determine it's robustness. If it crashes a lot, there's not much point
wrapping it. On the other hand, if it turns out to be bullet-proof, I
would recommend against
leif wrote:
Amit Jamadagni wrote:
[...]
We got introduced to the Braid progamme
(http://www.layer8.co.uk/maths/braids/index.htm) project as we were
looking out for Vogel's algorithm implementation. Coming to the details
of Braid project it has been written in C++ and has some extensive
results p
Amit Jamadagni wrote:
[...]
We got introduced to the Braid progamme
(http://www.layer8.co.uk/maths/braids/index.htm) project as we were
looking out for Vogel's algorithm implementation. Coming to the details
of Braid project it has been written in C++ and has some extensive
results pertaining to
11 matches
Mail list logo
