From: Toby Ho <air...@gm...> - 2005-12-19 04:47:15
|
I really think what you're suggesting is out of the scope of my project. But I do have a suggestion how you might do it though. For one thing, the yaml file you've created can be loaded in as a java.util.Map Map map =3D (Map)YmlDecoder.loadFromFile(filename); and at this point you can do whatever you'd like with it. Work directly with the map if you'd like, or store it off somewhere so that you'll have the values when you need them later. toby On 12/18/05, Sven Verdoolaege <ski...@ko...> wrote: > On Sun, Dec 18, 2005 at 01:24:36PM -0500, Toby Ho wrote: > > Skimo - I'll just ignore or give a warning when the field is missing, > > no problem. > > That would be perfect for my use (assuming I can suppress the warnings), > but you might also want to consider the bigger picture. > > It's nice to be able to read in a data structure made by some > other program, make some changes to it and write the data out > again, without loosing (as much as possible) any information > created by the other program that your program may not know > about. > > I.e., if a map has some entries that don't map to your java > classes' fields, you typically want them to reappear in the > output when you emit your data structure again. > > skimo > |