I just ran this branch on my Sherline / Probotix setup, and I think one of my recent commits broke something so that a G-code program fails to run. I'll investigate further over the weekend.
Also, I'd like to clarify that my goal is to merge this branch to master as soon as it's demonstrated to be stable (provided the changes are in line with the community's goals). I'm guessing it will take 1-4 weeks to fully test. For anyone who's familiar with trajectory planner structure, I'm curious why some of the state of the trajectory planner is stored in static variables, rather than the TP_STRUCT itself. I'd like to collect all the state data for the trajectory planner in one state structure, since that pointer gets passed around to all the functions anyway. -Rob On Thu, Oct 31, 2013 at 8:37 PM, Robert Ellenberg <[email protected]> wrote: > Hi All, > > As part of the trajectory lookahead overhaul, I've done a bunch of > refactoring in the trajectory planner and in the posemath library. Rather > than introduce all of the changes as one big patch, I rebased out a bunch > of under-the-hood changes as a standalone patch. These tweaks shouldn't > change any behavior or features, so it will be easy to test by comparison > to the current master. Hopefully it will make my future changes easier to > integrate. > > Here's a summary of the changes: > > - Refactored large sections of trajectory planner code into static > functions > - Added doxygen-style docstrings to major trajectory planner functions > - Converted inputs to C functions in posemath to use constant pointers > to constant data > - Added const specifier to output pointers > > Here's the branch on my github mirror: > > > https://github.com/robEllenberg/linuxcnc-mirror/tree/feature/pm-pass-const-pointer > > Please let me know if you have any feedback on these changes. I'm open to > suggestions at this point, since my lookahead stuff is in active > development. > > Thanks! > Rob > > ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
