I appreciate you taking a look at this code but that approach will cause more problems for me than I have time to fix.
I've already used the PGMLTable subroutine 11 times in this problem so, I'm too deeply invested to change that.
Since it has worked for 11 other tables, I must be doing something different trying to make this table.
My biggest issue is that I have never written a subroutine before.
I have removed all the code that is not necessary for the Kmap to work from this version of the question.
You can see that the PGMLTable subroutine works three times
246 $PGMLLabelTable = PGMLTable(~~@fLabelTable);
247 $PGMLTable = PGMLTable(~~@table);
248 $PGMLAnsTable = PGMLTable(~~@ansTable);
But fails here
260 $PGMLAnsKMaps = PGMLTable(~~@kmapAns);
I'm trying to determine why @kmapAns has a different format than @fLabelTable, @table, @ansTable.
It has to be something in either "sub KmapMaker" (lines 62 to 93) or the creation of kmapAns (lines 250 to 258).
I've already used the PGMLTable subroutine 11 times in this problem so, I'm too deeply invested to change that.
Since it has worked for 11 other tables, I must be doing something different trying to make this table.
My biggest issue is that I have never written a subroutine before.
I have removed all the code that is not necessary for the Kmap to work from this version of the question.
You can see that the PGMLTable subroutine works three times
246 $PGMLLabelTable = PGMLTable(~~@fLabelTable);
247 $PGMLTable = PGMLTable(~~@table);
248 $PGMLAnsTable = PGMLTable(~~@ansTable);
But fails here
260 $PGMLAnsKMaps = PGMLTable(~~@kmapAns);
I'm trying to determine why @kmapAns has a different format than @fLabelTable, @table, @ansTable.
It has to be something in either "sub KmapMaker" (lines 62 to 93) or the creation of kmapAns (lines 250 to 258).