I
don't like the sound of using the path as an indicator of how the data is to be
interpreted. A better solution would be to pass in a third parameter
which defines the way the data is to be interpreted, i.e., the record to
use.
By the
way, depending on how much control you have over the data, I would really try to
do away with one of the records, since. after all, they describe the
same same information, just in a different order. Is this really
necessary?
-Andreas
|
- [DUG]: Load different types from one procedure? Jason Coley
- Re: [DUG]: Load different types from one procedure? Phil Middlemiss
- [DUG]: Resume Next in Delphi Traci Sumpter
- Re: [DUG]: Resume Next in Delphi Neven MacEwan
- Re: [DUG]: Resume Next in Delphi Chris Reynolds
- Re: [DUG]: Resume Next in Delphi Laurie Bisman
- Re: [DUG]: Resume Next in Delphi Dennis Chuah
- RE: [DUG]: Resume Next in Delphi Andreas Toth
- Re: [DUG]: Load different types from one procedure? Andreas Toth
- Re: [DUG]: Load different types from one procedu... Paul McKenzie
- RE: [DUG]: Load different types from one procedu... Mark Taylor
- Re: [DUG]: Load different types from one procedure? Neven MacEwan
- RE: RE: [DUG]: Load different types from one proced... Jason Coley
- Re: RE: [DUG]: Load different types from one pro... Paul McKenzie
- RE: RE: [DUG]: Load different types from one pro... Mark Taylor