There is no need to use XML. There is already a standard text representation of a VFP class:

DEFINE CLASS ClassName1 AS ParentClass [OLEPUBLIC]
  [[PROTECTED | HIDDEN PropertyName1, PropertyName2 ...]
     [Object.]PropertyName = eExpression ...]
  [ADD OBJECT [PROTECTED] ObjectName AS ClassName2 [NOINIT]
     [WITH cPropertylist]]...
  [[PROTECTED | HIDDEN] FUNCTION | PROCEDURE Name[_ACCESS | _ASSIGN]
  | THIS_ACCESS [NODEFAULT]
     cStatements
  [ENDFUNC | ENDPROC]]...
ENDDEFINE

>Hi gerry,
>
>>A library is a library, whether it's in the form of a .PRG or a .VCX.
>>
>>It's like asking a "user": "Would you like an SQL Server or an Oracle backend ?" Huh?
>>
>>Some people don't "want" to give up VCX's, etc. ... but I'm still waiting for a single concrete reason as to why they need to be kept around (other than "that's they way it's always been").
>
>Comming to think of the issue. Since, tables can be described with XML, and XML is sort of an ASCII format. Can XML fill the GAP between PRGs and VCX based classes ???
>
>Walter,