G'Day Roy,
 
-=> Quoting Roy Mcneill to Frank Adam <=-

 FA> When Prog1 gets it's slice back it goes and returns ptr which is no
 FA> longer the same animal,

 RM> ptr is the same, it's just the block of memory that it points to
 RM> that may have changed. And since your code has already freed that
That is what i meant.

 RM> Nothing actually wrong with returning ptr after it's been freed,
 RM> it's just pointless. Unless it's used to return an error if
 RM> something in the function failed (a bit obfuscated for my taste,
 RM> unless fully commented...)
As i've said in an earlier mssg, it did return the correct string
properly, even after it was freed, at one stage i executed a few more
functions just to see, how long it'll take until it gets corrupted, got 
tired of waiting, the string was still in there. 
Of course it's not advisable, and it was basically just a test.
                                                              
  L8r Frank (fadam{at}ozemail.com.au).
  
___ Blue Wave/DOS v2.21

--- Maximus 3.01