On Jul 25 2016 2:45 PM, Gene Heskett wrote: > On Monday 25 July 2016 16:09:34 EBo wrote: > >> On Jul 25 2016 2:01 PM, andy pugh wrote: >> > On 25 July 2016 at 20:33, Gene Heskett <ghesk...@shentel.net> >> wrote: >> >>> > (debug,31 i_mjr_R=#<_i_mjr_R>) ( s/b reasonable mm's? ) >> > >> > The problem appears to be with having two comments on the same >> line. >> >> Oooo... if that is the case, the parser should be fixed. That seems >> to be a valid use case. > > Well, I am not going to jump up & down about it and stamp my feet, > but it > does seem handy to have an explanatory comment on the same line as > the > debugging comment. Putting it on the prior line, or below on the > next > line seems to be a visual disconnect for me. But I'm not steering > this > boat we're all in. :-}
as was explained in a separate branch of this discussion you can use the ';' to delineate a line. I still think it should be fixed because delineated or bracketed comments should work everywhere. Otherwise if violates the principle of least surprise. On most other language parsers the follwoing would be valid: g01 x=1 (why is x set this way) y=2 (how about y?) z=3.14159 (because it is easy as pi) EBo -- ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
