Hi Ingo: In reply to your statement: >When your 'op was named 'open, did you change the line > fp: open/new/write %objone.txt >to > fp: system/words/open/new/write %objone.txt > ------------- >?? > >otherwise it has called itself, again and again ... I didn't - and that's why I got a stack overflow, because of unending recursion. Thanks! I'm glad you caught that! Tim At 01:20 PM 4/12/00 +0200, you wrote: >Hi Tim, > >I haven't closely looked at your code, but a >short notice on ... > >Those were the words of [EMAIL PROTECTED]: >> I have probably answered my own question: >> I'm still a newbie, but am pleased to return >> results -> >> ; == consider the following code: the two objects work >> ; independently. They use the same named methods >> ; op, prn, and close >> ; When I named those methods open, print,and close, >> ; I got stack overflows, which suggests to me >> ; that rebol doesn't like me overridding their >> ; own system functions. ><...> >> object-one: make object! >> [ >> op: func [] [fp: open/new/write %objone.txt] >> prn: func [value] >> [append fp value] >> cls: func[] [close fp] >> ] > >-- _ . _ >ingo@)|_ /| _| _ <We ARE all ONE www._|_o _ _ ._ _ >www./_|_) |o(_|(/_ We ARE all FREE> ingo@| |(_|o(_)| (_| >http://www.2b1.de/Rebol/ ._| ._| > >
