<OriansJ>markjenkinsznc: no worries as I am quite buried here due to the insanity of years of warnings finally hitting home. Eligibility is being hit with a workload several orders larger than standard; combine with the CMS audit and everything. I've been having zero time to work on the things that need to be done in mes-m2 or M2-Planet. <dddddd>OriansJ, one silly question about M1-macro.c. What EOL should we support? I'm getting mixed signals... <dddddd>purge_lineComment() checks for \r, but it seems to be the only place. <dddddd>Should we remove that exception or check for \r everywhere else? <dddddd>A param? A couple of params (input v. output)? How far do we want to go? <dddddd>Of course, the simple thing is to remove that weird \r and consider only \n (and use \n for output), but I really don't know why \r is there and how much it matters... <OriansJ>dddddd: well \r is what a bios environment would use by default for the [enter] key <OriansJ>so we can either also support \r or simply expect bios level implementations of SET or the hex0-monitor to replace \r with \n when read {Thus eliminating the need for \r in the current implementation} ***ChanServ sets mode: +o rekado_
***rekado_ is now known as rekado
<fossy>rust bootstrapping: 6 down, 6 to go... <fossy>i am glad to see that someone has already scripted this up ***efraim_ is now known as efraim
***nikita`_ is now known as nikita`