Platon Technologies
not logged in Login Registration
EnglishSlovak
open source software development celebrating 10 years of open source development! Thursday, March 28, 2024

File: [Platon] / libco / TODO (download)

Revision 1.3, Fri Feb 21 09:00:35 2003 UTC (21 years, 1 month ago) by yenar

Changes since 1.2: +1 -1 lines

NEWS: Added first 0.2.2 news.
TODO: Increased percent-done on plugin architecture.
configure.ac: Bumped version to 0.2.2.
debian/changelog: Added 0.2.2 entry.
libco/Makefile.am: Fixed libltdl_co link flags (added $(LIBADD_DL))
libco/co_module.c: Try more init functions for module, pass co_super to init
    function.
libco/co_module.h: Fixed co_module_load prototype.
libco/co_super.c: Use .cometa file, add module_load method (wrapper
    for co_module_load from co_module.c), plus slight formatting fixes.
libco/co_super.h: Made co_super proper CO_OBJECT.
po/sk.po: Autogenerated changes... damn.
test/*: Added module loading testcase into "make check". Fixed it slightly
    (the testcase).

MESSAGE TABLE CREATION [target: 0.2.1, done: 80%]

TABLE-DRIVEN DEFAULT MSG HANDLER [target: 0.2.2, done: 60%]
At least for now it should use simple cycle comparing received message id with
method table items one by one. When found, method shalt be executed, if not,
default action taken (i.e. "default" method invoked, which then could take
care of implicit delegation et cetera).

MORE INTELLIGENT CO_ATTR/CO_METH_INI [target: 0.2.x, done: 30%]
These should not need explicit object name, just get it from last CO_OBJECT or
CO_METH respectively. The CO_METH problem is much harder to solve and bit more
annoying.

REFLEXION [target: 0.2.3, done: 40%]
A method should be available for each object that will provide outside world
with informations from method table of object. By means of copp it should be
incorporated in message table of every prototype object.

CLONE [target: 0.2.4, done: 0%]
This should replace current constructor approach. There will be constructor,
but only as a prototype creation mechanizm, and it will be autogenerated by
copp. It will set up message-handler table for the object and so on. But more
types of cloning should be available: shallow copy, deep copy, stand-alone,
etc. This will then affect way objects are coupled - as with default, method
tables are shared - and thus adding (or removing) method at runtime will
affect all such objects. Stand-alone cloning will create new method table and
thus new object group.

PLUGIN ARCHITECTURE [target: 0.2.5, done: 40%]
Create consistent framework built on libltdl for loading modules. Each module
shalt become object in loading process and export its interface this way.

SECURITY [target: 0.3.1, done: 0%]
Fix buffer overflows and alike.

CO_MAP ASSOCIATIVE ARRAY [target 0.3.2, done: 0%]
CO_BTREE BINARY TREE IMPL [target: 0.3.5, done: 0%]
THREAD SUPPORT [target: 0.4.x, done: 0%]

Platon Group <platon@platon.org> http://platon.org/
Copyright © 2002-2006 Platon Group
Site powered by Metafox CMS
Go to Top