Re: OBJECTS.FS Question

I finally made it work.  I attach the source code. There is no need to
modify objects.fs although I'd love to see it included in the
"official" release by Anton. Just include this after objects.fs.

Note that if you wish to omit the "persistant" word after each
interface, you need to redefine
end-interface as
: end-interface  end-interface persistant ;

As I said before, this cannot be done generally in classes. If you
always stick to the same class declaration style, then you could
probably do a similar thing either in end-class or end-methods

-Rafael

\
==============================================================================================
\ Persistant classes for objects.fs
\ Rafael Gonzalez Fuentetaja, May, 7th, 2008.
\ Public Domain, no warranty.

: heap>dict				  \ addr1 u1 -- addr2
\ +G Transfer a chunk of memory from the heap to the dictionary
memory,
\ +* releasing the old heap memory.
   over >r
   here dup >r over allot		\ -- addr1 n addr2 ; R: -- addr1 addr2
   swap move
   r> r> free throw
;

: persist-interface-map		  \ old-ifce-map -- new-ifce-map
\ +G Persist a single interface map into the dictionary memory.
   dup
   @[EMAIL PROTECTED]
 interface-map 2@[EMAIL PROTECTED]
 nip		\ get the interface map size
   heap>dict				\ and reallocate
;

: persist-interface-maps		  \ --
\ +G Persist all interface maps for classes that implement interfaces.
\ Loop not executed if no interfaces are implemented.
   current-interface @[EMAIL PROTECTED]
 dup interface-map-offset @[EMAIL PROTECTED]
 swap interface-map
2@[EMAIL PROTECTED]
 drop
   swap bounds ?do
      i @[EMAIL PROTECTED]
 ?dup if persist-interface-map
      i !   \ patch the interfaces list with the new address.
   then
   1 cells +loop
;

: persistant
\ *G Copy the last defined interface map from the heap
\ ** back to the dictionary so that it can be safely saved in turnkey
\ ** applications, freeing the unusued heap memory.
   current-interface @[EMAIL PROTECTED]
 interface-map 2@[EMAIL PROTECTED]
 dup >R
   heap>dict
   R> current-interface @[EMAIL PROTECTED]
 interface-map 2!
   persist-interface-maps
;

object persistant \ make the root class persistant

0 [if] \ example code

interface
   selector sel1
   selector sel2
end-interface i-test1 persistant

interface
   selector sel3
   selector sel4
end-interface i-test2 persistant

object class
   i-test2 implementation

   Cell% inst-var m-count

   selector foo

end-class per1

per1 methods
public

  m:
     m-count off
  ;m  overrides construct

  m:
     ." count is " m-count ? cr
     1 m-count +!
  ;m  overrides print

  m:
     ." I'm foo selector" cr
  ;m overrides foo

  :m bar
     ." I'm bar method"
  ;m

  m:
     ." I'm selector sel4" cr
  ;m overrides sel4

end-methods persistant

per1 dict-new constant p1

p1 print
p1 print

save persis.elf cr
bye


[then]




On 3 mayo, 18:37, Doug Hoffman <no.spam> wrote:
> ragof...@[EMAIL PROTECTED]
 wrote:
> > Further test have shown that this do not work for classes implementing
> > interfaces. I'm working on that to find out why.
>
> That is unfortunate.  Let's hope there is a way to do so.  IMHO
> Objects.fs *require* interfaces so the programmer is not burdened with
> the constraints of which messages can be passed to which objects, i.e.,
> having to design the class hierarchy in a specific way.
>