Or option4, just let asc2g/g2asc be v4’s graveyard as-is? It would be nice if libgcv could read v4 asc from a historical perspective, but not a big deal to me. All for fixing any bugs of course.
Cheers! Sean > On Jul 13, 2020, at 7:21 PM, Clifford Yapp <cliffy...@gmail.com> wrote: > > I hit that because I was trying to use lcov to build up a .g file that would > hit most of the g2asc v4 code paths to get set for testing the libgcv > translation of the asc logic (or at least more than moss.g). > > Even without the rhc I can't round trip the file, unfortunately... Not sure > whether to try to fix the g2asc/asc2g tools, try to make the libgcv version > work instead, or just ignore it and get the libgcv version working as well as > the tools currently do... > > On Mon, Jul 13, 2020 at 11:49 AM Christopher Sean Morrison via brlcad-devel > <brlcad-devel@lists.sourceforge.net > <mailto:brlcad-devel@lists.sourceforge.net>> wrote: > > Some (many) primitives intentionally cannot be downgraded. That said, > dbupgrade should have handled it gracefully and probably did not. > > Any primitives added in the last 10 years or so should not have or get v4 > support added. Rhc’s are older, though, so this is probably still a bug. > > Cheers! > Sean > > _______________________________________________ > BRL-CAD Developer mailing list > brlcad-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/brlcad-devel
_______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
