User talk:Genuinelucifer: Difference between revisions

User talk:Genuinelucifer (edit)

28 bytes added , 26 May 2016

m

14

edits

@@ Line 31: / Line 31: @@
 d) The above works on at least one OS (probably GNU/Linux).
-a) PyTave converts various Python objects into appropriate Octave objects: extend this in some way to improve the way @sym objects are returned from Python.  That is, bypass the current generating of xml strings.  This could be done in some
+a) PyTave converts various Python objects into appropriate Octave objects. PyTave needs to be extended to return proper @pyobj when it cannot convert the object. Also, symbolic must be able to convert such objects to @sym objects by calling proper python functions via PyTave (if they are indeed @sym).  That is, bypass the current generating of xml strings.
-non-optimal way initially, such as hardcoding specifics of @sym objects into PyTave.
 b) Improve the BIST test set coverage of both PyTave and Symbolic for any new features added.
@@ Line 42: / Line 41: @@
 ) Improve on 2a) with some TBD mechanism: perhaps a pure m-file callback feature in the PyTave export code.
 ) The above works on both GNU/Linux and MS Windows.
 === Time-line ===