[Date Prev][Date Next][Subject Prev][Subject Next][
Date Index][
Subject Index]
Re:BC vs. BX (was: XyWin sounds)
- Subject: Re:BC vs. BX (was: XyWin sounds)
- From: Jane Van Tassel 101233.342@xxxxxxxx
- Date: 21 Jan 97 03:26:46 EST
on 18 Jan., Holmgren wrote (in part)
"... The truth is, there is scarcely any need to use func BC any longer in a
program. BC is time consuming and distracting. Replace all instances of "BC
commandXC " with "BX commandQ2 " or "BX (command)".
BX=Blind_eXecute."
Far be it from me [is there an emoticon to indicate "no sarcasm intended"] to
doubt the advice of Holmgren or any of the other XyWrite gurus on this List, but
...
Several weeks ago (right after joining the List) I saw this advice while I was
writing a whole bunch of unconnected XPL programs. Some were proving a little
buggy, so to see what would happen, I wrote the next module using "BC...XC"
instead of "BX...Q2" in all the relevant places. Immediately, subroutines
tested independently started not just going haywire but locking up completely.
Restoring "BC...XC" where I had written "BX...Q2" solved the problem in that
particular case.
But when I'm writing little programs I tend to focus on getting the job done and
often don't keep detailed notes on what I'm doing; so I can't report what
characteristics, if any, distinguished the routines that didn't work with
"BX...Q2". I don't even know whether I was in Xy4 for DOS or XyWin (although I
keep the latter mainly for Win-based printing, I do lapse into just
writing/editing in XyWin when it's handier).
Can anyone tell me whether there are identifiable circumstances in which
"BX...Q2" *doesn't* work? Is this a difference between XyWin and Xy4?
Cheers,
Eric Van Tassel