And I'm not alone. I mean besides the extra-dimensional entities that
channel code through me, there are other code mediums who find the
@author documentation far too limiting.
Could the GAG library be extended to support code channelers instead
of those of us who pair-program with entities from beyond the veil?
Addressing the many possible entities who like to produce well-
documented (if often incomprehensible to human mind) code, I suggest
the following
enum EntityType {
EX_HUMAN,
LIZARD_PERSON,
INTERN,
SPIRIT,
OLD_ONE,
FUTURE_SELF,
ALTERNATE_REALITY_SELF,
ARMY_OF_NANOBOTS,
}
and to help out future (and dimensionally sideways) maintainers it'd
be good to know
enum OpinionOfHumanity {
BENEVOLENT,
COMMITTED_TO_EVENTUAL_DESTRUCTION_OF,
INDIFFERENT,
CAN_BE_PLACATED_WITH_CAFFEINE,
}
Sincerely,
@author mike.samuel
@channeling("C. Babbage", EntityType.EX_HUMAN)
On Apr 1, 10:37 am, ☻Mike Samuel <msam...@google.com> wrote:
> Go ahead.
>
>
>
> On Thu, Apr 1, 2010 at 09:35, Leo Deegan <leodee...@google.com> wrote:
> > Oh really good stuff, mind if I add this to the gallery? I'll make you the
> > @author (and/or @channeling if you like).
>