There's an additional issue in GIC. At the bottom of the "comments" section
there needs to be a "continue" statement. Otherwise
the code will drop through to the next "switch" test and then the
commented-out files will be passed back along with the regular
files. I don't know why it requires "continue" when it should technically
require "break", but that's the only way that seemed to
work. I also don't know how this escaped the original author's notice,
unless they never used comments.
To be more clear, it needs "continue" either just before or just after the
line:
#$ini[$section][$name] = $value
In my own copy I've used your GIC from tidbits but adding "continue". So if I'm
the next one to update
both sets of changes will be there. I've also listed your changes and my
changes in the comments at the
top to ease confusion.
1.4 - 2019/07/18 - Various changes to section tests (TT)
1.5 - 2019/07/22 - Needs 'continue' at bottom of section
test (MAS)
Thanks!
On Saturday, July 20, 2019 at 2:12:56 AM UTC-7, @TiddlyTweeter wrote:
>
> Ciao Mark S. & interested avians
>
> ISSUES
>
> 19/07/20 -- There are issues with *.\lib\Get-IniContent *related to
> whitespace handling. In the "test" version of Polly I discovered that IF a
> "[parrots]" setting line has trailing spaces it will fail to parrot. I'll
> change the module's regular expressions for next version so this is,
> hopefully, no longer an issue. The draft code changes are at:
> https://tidbits.wiki/polly/polly.html#Get-IniContent.ps1%20-versioned under
> "Info > Versions > item 2"
>
>
> TT
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/82d51883-d5cc-479e-ad43-c422119114ef%40googlegroups.com.
