into the
> existing C import code you'll at least avoid creating bugs in those parts
> of the process.
>
> Regards,
> John Ralls
>
>
>
>
> On Feb 4, 2024, at 16:50, Brian Rater wrote:
>
> Great. Thank you for the insights. Before I got overwhelmed with work
>
:50 PM John Ralls wrote:
>
>
> > On Feb 4, 2024, at 12:11 PM, Brian Rater wrote:
> >
> > I've been looking at the import code and documentation and I'm wondering
> > what the overall plan and path is. It looks like there is a "generic"
> > imple
I've been looking at the import code and documentation and I'm wondering
what the overall plan and path is. It looks like there is a "generic"
implementation in the top level directory which has utilities that are
being converted to C++. I can see the importers making some calls into
this. What
Future?
On Thu, Mar 23, 2023 at 8:57 PM John Ralls wrote:
> We're 3 days away from releasing 5.0 and so 4 days away from shuffling the
> branches. Absent any objections I intend to rename the current "master" to
> "stable" and make it the default branch on Github. Bugfixes and
> minor-to-medium
