0

I am coding a boggle solver for which I need to populate a dictionary. My approach is the do a static initialization something like:

private static final Set<String> dictionayKeys = DictionaryReader.populateDictionaryWords("/../dictionary.text);

To add more details, the boggle solver would only use dictionaryKeys to verify if a word is contained then dictionaryKeys eg dictionaryKeys.contains(currWord)

Now question - I have been reading up on lazy initialization, and wondering if this example would be be an ideal canditate for lazy init, given the file IO involved ?

Guy Coder
  • 24,501
  • 8
  • 71
  • 136
JavaDeveloper
  • 5,320
  • 16
  • 79
  • 132
  • 1
    You would need to profile... How long does it take to load your data? If it takes long It would be a good candidate to a lazy loaded singleton or even to load through a concurrency library (take a look at [my previous question](http://stackoverflow.com/questions/6189099/lazy-loaded-singleton-double-checked-locking-vs-initialization-on-demand-holder) at my previous question about lazy loading initialization) – Anthony Accioly Oct 20 '13 at 19:43

1 Answers1

2

Probably not in this situation. Wouldn't you ALWAYS need to populate the dictionary at some point? I would rather wait a little bit longer when starting the program so it can populate a dictionary, then have the program seemingly hang when I am playing the game while it populates it lazily.

I think lazy initialization is better used when it is an expensive operation AND the data isn't always required. For example, hibernate might lazily load some of the fields of an entity object that aren't related to the entity's key because not every use case of the entity will need that part of the data, only the ones that explicitly ask for it.

dkatzel
  • 31,188
  • 3
  • 63
  • 67