delorie.com/archives/browse.cgi | search |
Hello John. Quoting John Doty <jpd AT noqsi DOT com>: > Thus, the infrastructure locks in the language in an important > subset of cases. It is important that the infrastructure be > accessible from a widely familiar language that’s easy to learn. In > my world, people fluent in Guile are rare. People fluent in Lua are > nonexistent (I don’t do games). But Python is ubiquitous. Yes. How about going multiple pathes, while not breaking the old one? And I am aware of the fact, that all the EDA guys are fluently in Tcl and Perl; and someone around Cadence might be fluent in Scheme. I would like to build some functions, to interprete Tcl in a Guile environment and also to interprete Guile/Scheme in a Tcl one. So if someones comes from Tcl easily can use the gEDA tools with their Guile interface. Another one from Scheme can also use other tools like ngspice with Tcl interface quit easy. Both directions become more seamless, right? And do not forget the "competitor" KiCAD also was at FOSDEM. As I understood all (dinner) talks, they are like the edacore proposal also. Let's cooperate! If we like to pimp up the interchange file formats for smooth intergration to/from other environments, and not further using the current ASCII format, something like YAML can be handy. Just the same principles w/ attributes, but a litte bit more eloquent/better code readability while using-the-editor- for-changing-something-quick. Currently I eye-balling every time on the format description to fix the right value on the right position.. Regards, Hagen Sankowski -- "They who can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." Benjamin Franklin (1775)
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |