Posted by: rowbearto
« on: December 24, 2022, 01:27:44 AM »I don't remember anymore about the compile.e file.
However very recently I copied one of my macros, lets call it rowbearto.e to a new directory. I loaded the newdir/rowbearto.e in Slickedit (load command) but it still was using the .ex file from olddir/rowbearto.ex. I was able to know this because it was still exhibiting old behavior that was changed in the newdir/rowbearto.e.
I had to explicitly remove the olddir/rowbearto.ex to force it to use newdir/rowbearto.e, then it behaved as I expected.
So I'm worried about a similar issue if I load your macro, even though I very much want this fix.
I think I'll create an 'sepatch' directory where I place these and then I can easily move that directory to make sure SE doesn't use them.
				However very recently I copied one of my macros, lets call it rowbearto.e to a new directory. I loaded the newdir/rowbearto.e in Slickedit (load command) but it still was using the .ex file from olddir/rowbearto.ex. I was able to know this because it was still exhibiting old behavior that was changed in the newdir/rowbearto.e.
I had to explicitly remove the olddir/rowbearto.ex to force it to use newdir/rowbearto.e, then it behaved as I expected.
So I'm worried about a similar issue if I load your macro, even though I very much want this fix.
I think I'll create an 'sepatch' directory where I place these and then I can easily move that directory to make sure SE doesn't use them.
 
                        