>
>Don't worry! I'm not trying to blow things into a major debate either <g>. I'm just trying to understand your concept of consistency. I was curious if others felt the same way. Its not a big deal.

OK, just as long this isn't going to turn ugly ;-) The threads from Steve & John are enough for me <g>.

>
>But what specifically is wrong with the case of the code you posted? The IF/ENDIF is capital but the lparameters, sys() and returns aren't? Is it the Camel Case Letters?
>

I picked that at random. Other code sometimes capitalizes IF/ENDIF, sometimes not, sometimes capitalizes the methods, sometimes not. That's what I mean. Also, this is in addition to the fact that some methods have headers, some don't. I think one job as a framework developer is to make the code you write as clear and consistant as possible, and I think these things contribute to this. As silly as it might sound, how the code "looks" is important to me and I think can positively or negatively effect how easy it is to understand.

>I've had to work with code from many developers, so I guess my skin is pretty thick (and not just because I eat well)!

I've worked on some ugly legacy code too, but I don't like it <g>. Trust me, we have a lot of code here that I have to support, from a lot of different developers who seemed to each have their own ideas of how to code. While I can do it, I'm not always happy about it (and I'll avoid it as much as possible). Because of this, I want to use code that's easy on the eyes when I'm working with a framework.