Forums

by Dave Mellow >> Wed, 1 Nov 2006 18:18:48 GMT

Hi all

I've never used patch versioning in the way that it is probably intended, but do often use the "Browse Patches" facility to visually re-check the list of changes made over a length of time, say the last day or two. I'd always thought that some method changes seemed to be absent from the list, and realised the other day why. I changed the signature of a method and upon compilation I was of course presented with a list of methods now in error (calls to the method I'd just changed)... I then clicked on each of those, fixing and re-compiling them one at a time. Later I noticed that they were the methods not listed when I browsed the summary of patches. In other words, methods changed and compiled via one of the "methods in error" windows don't seem to get added to the patch summary.

Just wondering if other users had noticed this behavior and whether there is a logical reason for this that escapes me right now (as I mentioned I've never really fully investigated or used the patch versioning feature, and I'm just curious if there is an obvious reason that the methods I've described were excluded)? By the way, the system I'm talking is back at Jade 6.0.20.

Regards
Dave

by cnwjhp1 >> Wed, 1 Nov 2006 20:23:48 GMT

There is an option on the Patch form to Include Compiled Methods. Did you set that?

by Dave Mellow >> Wed, 1 Nov 2006 22:08:40 GMT

Thanks for that suggestion.

Curiosity is getting to me, and just I went into two systems, the 6.0.20 one I normally work on (incidentally, this is an old - circa 1998 - and big system that has gone through lots of version upgrades etc.) and a basically empty 6.1.08 I had downloaded.

Changing and recompiling methods in the new system seems to always produce predictable patch summary results (irrespective of which window etc. I do it from)... further testing in the older system does seem to indicate different behaviour... for example (and I had thought in the past I had seen this) if the window in which I compiled the method is still open, that method doesn't initially show up on the patch summary. The moment I close it the method pops up (through some notification event I'd imagine) in the patch summary window. In the 6.1 system the method shows up irrespective.

So, OK there is different behavior... the later version seems to me predictable in its results and I would assume some of the "quirky" behaviour I've always thought I'd observed will most likely be fixed when we upgrade. Incidentally, a colleague mentioned that she thought she'd sometimes noticed similar things happening with deltas.

Thanks for your suggestion though, and I think I need to do a bit more reading of doco concerning patch versioning in general.

Regards
Dave