Re: 1.4.2 Release Candidate Available

> i think that abre was talking about the static method taking a
> ConcreateElement as a parameter in ConcreteElement. (hopefully he'll
> correct me if i'm wrong.)

Hmm, now I have another question--what's the intended difference between the
static and non-static versions? Why would one call the static version
directly instead of the non-static version?

>
> <snip>
>
> i'm not sure (maybe stephen can answer that) but i'd say that it seems
> like a reasonable way to specify an encoding so that elements can write
> themselves

The reason I'm curious is that I can't imagine that anyone would ever invoke
setCodeSet on each element individually--it would just be too tedious. In
practice, you'd just set the global default value in ecs.properties, which
each element would then pick up. But then if every element is using the same
value, it seems a little inefficient (and perhaps confusing) to have each
element store its own copy of that value.

- Rob