Thanks, Ken- you're right, of course. Transcript seems not to penalise
sloppiness, so it's easy not to notice that one has left out parentheses.
Wouldn't it be better if the IDE tightened up on this sort of thing? It's
worrying that code can work in the IDE but quietly fail in a standalone.
> I s
The server upgrade cut me off for a while, which is just as well. In the
interval, I have realised that my post claiming that I had found an
inconsistency in Transcript between IDE and standalones was... well,
actually, I was totally and embarrassingly WRONG.
So please accept my apologies for wast
(apologies it this is duplicate post - access problems after the server
upgrade?)
Thanks, Ken- you're right, of course. Transcript seems not to penalise
sloppiness, so it's easy not to notice that one has left out parentheses.
Wouldn't it be better if the IDE tightened up on this sort of thing?
On 6/27/05 5:03 AM, "John Ridge" <[EMAIL PROTECTED]> wrote:
> I should emphasise that it's a standalone problem - it fails when compiled
> for Mac OS 9 as well as Windows. Are there known issues like this with the
> syntax of Transcript when compiled into a standalone? If so, I'd appreciate
> a p
I've just hit something that seems to me very weird. I'd appreciate any
thoughts.
The (tiny) problem is to calculate the interest due on a sum of common-law
compensation - our client X paid certain sums over a period; the court has
now agreed that they should not have been required to pay. OK, th
