Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
base system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
17 May 2009 at 02:47 UTC
Updated:
1 Jun 2009 at 14:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
pwolanin commentedAn easy and sane standard - use the unix timestamp as of when you write the code - then new modules can never break existing modules, and core never uses in values in the range of current timestamps. Hopefully since this is jsut doc it can also get backported for D6.
As a separate issue we should consider for D7 whether flags like the node build mode should be strings that are easier to make unique using a module name as a prefix.
Comment #2
pwolanin commentedComment #3
cwgordon7 commentedLiklihood should be spelled likelihood. :)
Comment #4
cwgordon7 commentedAlso the unix timestamp seems to make sense, but I wonder whether it would be any better to just randomly generate a number - or perhaps create a centralized listing somewhere where a contributed module can reserve integer constants.
Comment #5
pwolanin commentedAngie rightly points out that no one will see the doxygen there. So, how about just adding it to node_build_content() since we don't even document currently that this node property will have a major impact on the result of this function.
Comment #6
pwolanin commentedfix typo
Comment #7
webchickCan we please also add the possible build modes included in core, like hook_menu() does with 'type'?
Comment #8
pwolanin commentedok
Comment #9
dries commentedCommitted to CVS HEAD. Thanks!