Re: GSoC 2017- Application (Symbolic Package)

[Abhinav Tripathi]

Hi, just to answer a few of your questions :

On Mar 27, 2017 1:39 PM, "NVS Abhilash" <address@hidden> wrote:
>
> Hi,
>
> Thank you again for your valuable feedback.
>
>
> I have tried to add some bug numbers to the application. Please verify are
> they the correct ones which are needed to be resolved first.
>
> I was not able to find exact bug report in core Octave for this: "indexing
> constants with a classdef object". Can you help me with that?
>

I think there's no bug report for that. You can open a new bug report.

> Also is it completely not feasible to use this PR
> [https://github.com/cbm755/octsympy/pull/590#issuecomment-283458422].

I think that PR is completely okay in itself, which  means if you start from scratch you will eventually end up doing something similar and have the same blockers as this PR. It would be better if we resolve the 3 issues in core which are blocking this PR from getting merged. That would save duplicate effort too.

> Because then it means I have to work on the existing implementation of @sym
> and when that PR gets ready to be merged will there be more conflicts not
> only merge conflicts but implementation wise?
>
> I think it will depend on how much of the upstream issues are resolved in
> the GSoC. But is there some other problems that I am missing?
>

Please fetch the PRs code and run the tests. There might be a couple of failing tests which may be resolved. Also you might optimize the existing code.
Other than that I think you can base your work on that PR.

Regards,
Abhinav

> Thanks,
> NVS
>
>
>
> -----
> NVS Abhilash
> --
> View this message in context: http://octave.1599824.n4.nabble.com/GSoC-2017-Application-Symbolic-Package-tp4682483p4682626.html
> Sent from the Octave - Maintainers mailing list archive at Nabble.com.
>