## Pegasus Telecon, 2 August 2001

## Attendees

- Mike Brasher
- Karl Schopmeyer
- Orano
- Bob Blari
- Carl Chan
- Bryan
- Roger Kumpf
- Mike Day
- Barbara Packard.
- Ellen Stokes
- Denise Eckstein

## Agenda

Review of the last week.

the Subscription Document - One hour telecon.

The programming style guide

The Build structure..

## NOTES

### Immediate Activities

What

Next Week.

Bob Blair -

ACTION: Note to BB the toMOF sutff.

HP - repository Changes.

Mike Day - Threading completed.

### Subscription Document discussion

Subscription TELECON tomorrow same time.

Ellen Stokes -

### The Build breaking Problems

Actions: HP will try to do an NT build.

Question: Could we share between subgroups without getting the whole group involved. Multiple branches, etc.

SUGGESTION: Keep things out of the build but commit them. This could be done with conditional make or local makefiles.

### The Build Structure

Chip made a proposal to look at breaking up the libraries. In particular he is concerned because the common lib is very large and in his case, he only uses pieces of it. We agreed that we will need to reorganize the libraries at some point but that we should try to get through the next major milestones and code drops with the existing structure. We do need to clarify what basis we will use for reorganizing

ACTION: Chip noted that he gets lots of calls about the executables, etc. since we have all executables gathered into a common library We agreed that the executables should be moved. Move the test functions executables to a bin/test directory

Chip noted that he is going to create the provider manager Class. The provider manager - Unload and load providers on its own.

ACTION: Chip Monday Provider Manager discussion.

QUESTION: we noted that the exceptions.h file is probably disorganized today. We are looking for suggestions to clean this up. In generally we probably need to move exceptions much closer to the source.

ACTION: This should be part of the guidelines.

Mike day suggested using the throw clause in your class definitions. Note that this may not work for all compilers so we will have to do a macro out.

ACTION: We need to document and define the characteristics of exceptions. This should become part of the Guidelines.

Agreed that we should have separate exceptions, not groups with IDs.

ACTION: We need to start a working discussion for the changes required to exceptions.

Internationalization: No we have not really put any thought into this yet.

NOTE: The system class is not international today. Thus, internationalized names, etc. would be narrowed down to UTF8. There is another set of higher level functions (FileSystem.h) that should be used. These functions use String which is internationalized.

ACTION: We want to encourage the use of the _name as a way to define private functions.

ACTION: Clean up the FileSystem stuff.

### The Style Guide

MD asked about style guide that we use. ELEMTLL is probably the style we should use.