A few things to add to the roadmap proposal.
I suggest we start making Glob2 explicitly network-safe by applying the
proposal I put forward during the networking discussion to all newly
written code, and to old code where appropriate. That is, code must be
put in the "Glob2" namespace, and code which is explicitly not portable
be put in the "Glob2::nonportable" namespace. Code in these namespaces
are not allowed to use plain ints/floats/etc., and instead have to use
Sint32 etc. Code in the non-portable namespace can use "Sint", "SintL"
etc., which are explicitly not portable. Detecting breaches of this
policy should be as simple as running a `grep`.
Also, solving the inn bug should be a requirement for the next release,
and we should make some effort to get improvements to path-finding in,
unless they would involve structural changes, or otherwise delay the
release too much. That's not to say that structural changes wouldn't
be allowed in, only that they might need to wait until the next release
if they start causing problems.
- Andrew
_______________________________________________
glob2-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/glob2-devel
