Re: Voting reminder: OLE

--------- Original Message -------- From: Jesus M. Castagnetto > > --- Xavier Noguer <xnoguer@rezebra.com> wrote: > > > > OLE's internal structure tries to resemble a filesystem, with files and > > directories. In that sense it is a data structure. > > Yep. I looked at your code again, and indeed is a fs-like. But it is not a > general data structure in the sense of: > > http://www.nist.gov/dads/HTML/datastructur.html > > It is a structure in the sense of a specific C struct or similar. Any other > possible names? > > Also, my examples were a little mixed. In some langs lists/bags, sets, > maps/hashes, etc. are collections or data containers, and linked lists, stacks, > trees, graphs, are general (or abstract) data structures. As Arnaud pointed out, there seems to be some work on a DTA extension for php. That could mean that the Structures category will never become too much populated. See below for why do I think this is relevant. > Just take this as my understanding on the issue/concept. I am not a > professional programmer, just a scientist that mangles code. > > > > I am not sure if I would put OLE as a structure (if that were true, then > > > CORBA would be one too), but as a interprocess protocol or something along > > > those lines. > > > > I'm not trying to implement COM. The OLE format is just that, a format for > > containing files. The package implements an API for reading an OLE > > container's contents or writing them, nothing more. > > Perhaps a "Container" category then? Indeed, that would be a more appropriate name. But perhaps too specific? I just don't want to end up with a hundred categories in pear. I think having categories with just 1 or 2 packages should be avoided whenever possible.