A study of predictive value of a variety of syntax-based program complexity measures is described. Experimentation with variants of new chunk-oriented measured showed that one should judiciosly select measurable software attributes as proper indicators of what one wishes to predict, rather than hoping for a single, all pirpose complexity measure. This study has shown that it is possible for particular complexity measures or other factos to serve as good predictors of some properties of program but not for others. For example, a good predictor of construction time will not necessarily correlate well with the number of error occurences. Halstead's effort measure (E) was found to be a better predictor than the other two nonchunk measures we evaluated: McCabe's V(G) and lines of code, but at least one chunk measure predicted better than E in every case.