Re: Voting reminder: OLE
| From: | Bertrand Mansion | Date: | Fri, 18 Apr 2003 07:02:26 +0000 |
| Subject: | Re: Voting reminder: OLE | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-15227@lists.php.net to get a copy of this message | ||
<jcastagnetto@yahoo.com> wrote :
>
> --- Xavier Noguer <xnoguer@rezebra.com> wrote:
>> El Jue 17 Abr 2003 14:30, Jesus M. Castagnetto escribi?:
>>> --- Xavier Noguer <xnoguer@rezebra.com> wrote:
>>>> El Jue 17 Abr 2003 02:30, LIMBOURG Arnaud escribio:
>>>>> +1
>>>>>
>>>>> Wha will be the category ? Structures ?
>>>>
>>>> Yes. I'm proposing it for Structures.
>>>>
>>>>
>>>> Xavier
>>>
>>> +1 for the pacakage (although I do not use Windows)
>>> -1 for Structures as a category
>>>
>>> Using that name can be confusing, because usually when you see classes/libs
>>> classified under a "Structures" category, one tend to think about data
>>> structures, e.g.: lists, linked lists, sets, bags, maps, stacks, heaps,
>>> etc.
>>
>> 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.
>
> 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?
>
> Anyone else w/ ideas, opinions, clarifications?
Maybe Protocol, Linking, Interface, Network. Network already exists, I think
it's the best category for this stuff. -1 for Structure.
Bertrand Mansion
Mamasam