> > CreationInfo= Time Date
> > Time = Hour ":" Min ":" Sec [ Timezone ]
> > Date = [Day "-" Month "-" Year] | [Day "/" Month "/" Year]
> > Hour=<unsigned integer of two or less>
> > Min=<unsigned int of two or less>
> > Sec=<unsigned int of two or less>
> > Timezone= <signed int of two or less>
> > Day = <unsigned int of two or less>
> > Month = <unsigned int of two or less> | EnumeratedMonth
> > EnumeratedMonth= {"Jan" = 1} | {"Feb" = 2} ...
> > Year = <unsigned int of four>
>
> Thats way to many types. Nearly all of those are easily defined as just
> ints.
You gain a lot of flexibility by associating them with a subtype instead
of the general "int" type. There's important information conveyed by the
fact that CreationInfo is defined at "Date Time" instead of "int/int/int
int:int:int";
Using this construct we could even do comparisons across different types
easily. A message could define a new type based on known types
dynamically with each message.
Best of all we'll have a standarization between nodes, clients,ect.
-Larry
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
