[Date Prev][Date Next][Subject Prev][Subject Next][Date Index][Subject Index]

Re: hardcode.pgm anomaly



If Harry's solution doesn't work for you and HARDCODE.PGM did, try the 
following. Open HARDCODE.PGM and CVA the string "fix" to some sort of 
nonsense string, say "}]*={[". Any gibberish unlikely to occur in your 
files. Don't change the string "fix" when it occurs after LaBel or 
GoLabel. Save it as HARDCOD2.PGM or HARDCODE.PM and try that. It seemed 
OK at my end (I don't use the program); at least it stopped deleting the 
word "fix" from your source file.

HARDCODE.PGM uses "fix" as a marker (I've not looked closely at why it does that, though why it'd use a real word is beyond me), and ultimately cleans all "fix" strings from the file (ci /fix//, twice, for good measure).

Paul Lagasse

Harry Binswanger wrote:
Isn't hardcode.pgm something developed by XyQuest and send out by them, with purchase? If so, it's known to be a bad-behaving program.

If all you want to do is change DC tags into their numbers, a simple-minded program to do that is:

XPLeNCODE v2.0
b-gin [UNTITLED]
{<}SV568,{<}LB{>}{>}{<}SV569,LB{>}{<}XS568,569,595,570,596{>}
[BC_]Pgm assumes there's no resetting of counters--ok? (-/n){
<}SX01,{<}RC{>}{>};*;[cr|lf]{<}IF{<}RC{>}=="n"{>}{<}GL_{>}{<}
EI{>};*;[cr|lf][BC_]enter number of counter, 1 - 9 (or x){<}S
X01,{<}RC{>}{>};*;[cr|lf]{<}IF{<}IS01{>}=="x"{>}{<}GL_{>}{<}E
I{>};*;[cr|lf]{<}SX02,{<}PV01{>}{>};*;[cr|lf]{<}IF{<}PV02{>}>
9!{<}PV02{>}<1{>}{<}GL_{>}{<}EI{>};*;[cr|lf]{<}SX03,{<}PV01{>
}{>}[TF_][XP_]{<}SX04,1{>};*;[cr|lf]{<}LBA{>};*; LOOP [cr|lf]
[BX_]se /{<}PV595{>}c{<}PV02{>}{<}PV596{>}/[Q2_];*;[cr|lf]{<}
IF{<}ER{>}{>}[TF_]{<}GL_{>}{<}EI{>};*;[cr|lf][BD_][BD_][BD_][
BD_]{<}PV04{>}{<}SX04,{<}PV04{>}+1{>}{<}GLA{>}{<}LB_{>}{<}SV5
0,555-598{>}[JM_]2.clearsgts[Q2_]{<}EX{>}[cr|lf]
-nd
XPLeNCODE


Robert, Carl, anybody,

I have discovered an anomaly using hardcode.pgm. All instances of the string "fix" (case insensitive) in the source file are deleted from the target file. I attach samples. I'm guessing there is a mechanical pun involving a command call in the hardcode.pgm. Help?