G
Gerard Vignes
Could a ctags tags file be generated and distributed as part of each ruby source code release?
Having a tags file as part of the source distribution would give intelligent source code browsers a way to follow the ruby code down to the c-implementation, into the web of macros, functions and other c artifacts.
A specific example would be the pry REPL (e.g., irb), which comes with a plugin to view ruby's c source files.
Tools for performance monitoring ruby applications are very important now, but it is just as important to develop a deep understanding of the implementation by examining the sources (both ruby and c). Both approaches are needed to identify inefficiency.
The ecstasy of high-level languages is being able to accomplish so much work with so little coding. The agony of high-level programming languages is having little or no idea about how the work is actually being done.
Having a tags file as part of the source distribution would give intelligent source code browsers a way to follow the ruby code down to the c-implementation, into the web of macros, functions and other c artifacts.
A specific example would be the pry REPL (e.g., irb), which comes with a plugin to view ruby's c source files.
Tools for performance monitoring ruby applications are very important now, but it is just as important to develop a deep understanding of the implementation by examining the sources (both ruby and c). Both approaches are needed to identify inefficiency.
The ecstasy of high-level languages is being able to accomplish so much work with so little coding. The agony of high-level programming languages is having little or no idea about how the work is actually being done.