On 07/05/2016 02:12 AM, Tristan Gingold wrote: > On 03/07/16 20:47, Adam Jensen wrote: >> On 07/03/2016 11:20 AM, Jonas Baggett wrote: >>> Hello, >>> >>> I had some more thoughs on the signal selection for the waveform, and I >>> made an example of a wave signal file (is there a better english therm >>> for that ?) that reflects them : >>> >> >> Have you considered embedding a Tcl interpreter? > > Can you clarify why an interpreter would help to select signals ? > The file format is so simple that 'parsing' it manually would be very > simple too. >
A custom syntax/parser for a signal-trace configuration file seems like a perfectly valid way to implement a very useful function. If that is the only goal, then libconfig is probably overkill and jimTcl is certainly excessive. I've been imagining that one day GHDL might have richly structured HDF5 signal-trace capabilities, and that simulations might be configured with elaborate IPC/RPC (for interaction with Octave, R, SciPy, etc.), and a few other slightly more unusual deployments. It seems like much of this might benefit from a [scriptable] embedded shell with access to both the simulation-model and the OS. But these suggestions [from me] are all just "what if..." and "would it be nifty if..." type remarks. I'm not implementing anything and the decisions are ultimately going to be made by the people who actually build things. Viva la open-source! ;) _______________________________________________ Ghdl-discuss mailing list Ghdl-discuss@gna.org https://mail.gna.org/listinfo/ghdl-discuss
