This is going to be one of the most important areas of research and development moving forward in the coding world. As the amount of code multiplies and the number of languages balloon we will be increasingly crushed under the weight of our own creations. Advancements in version control have helped to keep us above water, but it's not enough. General purpose forensic coding tools are going to be needed. Leo has made great strides to fill this role and I'm excited to see how it evolves to further tackle these challenges.
On Wednesday, February 12, 2020 at 7:50:17 AM UTC-5, Edward K. Ream wrote: > > On Wednesday, February 12, 2020 at 6:01:31 AM UTC-6, Edward K. Ream wrote: > > > Leo is close to perfect for me. > > My overarching goal has always been to create a tool that helps people > understand computer programs in all their unavoidable complexity. That's > still true. > > A lot has changed since 1980 :-) Our language tools are so much better > now. That helps, but not enough. > > I'm always looking for new tools to add to Leo. The clone-find commands > were a huge step forward. I'm looking for others. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/832e2c97-961b-415a-b4ef-a523707ba431%40googlegroups.com.