From Sprezz Towers

Notes from the workshop.

Technical discoveries, field notes, unlikely bugs and the occasional opinion.

All Things Being Equals

The equals operator, or "=" to represent it symbolically. A simple programming standard; something you learned in the first 10-15 minutes of programming. Even with the simple statement x  =   1 which we all read out as x equals  1 we know that's not really completely true. It's more accurately Now ,  x should be set  to   1 or even more accurately, assign  1   to  the variable x Therefore, you could be safe in assuming that "=" isn't actually the equals operator at all, it's actually the assign operator. History buffs will recall that the original BASIC syntax was actually LET X  =   1 a construct allowed in ARev up through 3.12. But, simple assignment statements aren't all that the "=" operator is used for. In the statement if  x  =   1   then   gosub  here  else   gosub  there x is not assigned the value of 1...

Read article →

Driving Us Mad

Sometimes, just when we're starting to think that we've seen it all (with the obvious exception of a man eating his own head) we're hit with a support issue that really has us stumped. Recently we came across just such a problem. The client was finding that very intermittently at one specific site, an attach to a location would fail. This created a problem as the client wasn't using get_status to check for a failure and was just continuing on with the rest of their program leading to corrupted data. An awful lot of sleuthing followed. The problem manifested itself in an xlate returning a null value due to the table it was xlating from not being attached. So initially the blame fell on xlate - perhaps it was caching an old value in some way? FLUSHs were inserted into the code to ensure cache wasn't being used - but no joy. Long support calls ensued and the States gamely became involved in trying to find a solution. Eventually the issue was traced ...

Read article → 1 comments

I'd buy THAT for a dollar!

Here at Sprezz Towers excitement is rising about a forthcoming update to S/List that we think our users are going to love. With each release of OI we kept getting reports that S/List was getting slower - and our testing confirmed that this was the case. So we did what we do best at Sprezz - attacked the problem head on with a radical rewrite of the S/List engine. So for the past year or so we've been working on a new version of SLIST_PRODUCE (the program that does the grunt work for actually creating the report) to eliminate all calls to GET and SET_PRINTER. A few thousand of lines of code later we are finally ready to go public with the results. Now the User Interface remains the same ( for now ;) ) but the print engine is significantly faster. Those of you with long memories may remember AREV LightSpeed? Well we wouldn't go quite so far as to call it that but we have managed to wring every drop of performance from the product. Your mileage may vary but we reckon that most r...

Read article → 1 comments