On 5/10/07, Peter Karman [EMAIL PROTECTED] wrote:
What I would like to do now is at the same time I create code, also create
stub
POD for each of the columns, fks and relationship methods that are magically
available in each class. Just stubs: the method name, column/fk/relationship
definition, etc.
Any suggestions? Anyone tried this already? Anyone think it's a really bad
idea?
Anyone want to collaborate on a project?
Call it perl_class_pod() and have it called in the appropriate place
in make_modules() and I think you'll have something :) My advice is
to link to the relevant existing MakeMethds::* docs in the generated
POD where appropriate. All the information you need to do this should
be available by examining foreign_keys(), relationships(), and the
relevant method maps and objects (though you may need to use some
internal APIs. Use the source :)
-John
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object