|
List Info
Thread: rev 7.00 enhancement
|
|
| rev 7.00 enhancement |

|
2007-07-03 07:34:01 |
|
I need a little more info on this. What was the dilemma?
BASIS IDE
enhancement – Resolves the source and tokenized naming dilemma by
allowing programmers to run and debug the program as ASCII, thereby facilitating
the use of the same name for both source and tokenized versions
thanks Steve Nell Mark Systems
|
| RE: rev 7.00 enhancement |

|
2007-07-03 07:45:10 |
|
| The dilemma was that when you executed or debugged a
program in the IDE it executed/debugged the tokenized version of the
program. If you are using ASCII in the IDE (which BASIS recommends) and you
changed this program in the executor or debugger the developer was changing only
the tokenized version, i.e. not the ASCII version. So now you now have the
ability to directly run/debug the ASCII version of the program. Also when
you call or have a use statement in your application, it must specify the
program name with extension (.src or .bbj, etc) and when using different
extensions for your source and tokenized program, this would cause confusion.
Now you can keep the same extension for your source and tokenized program (but
in separate directories).
Brian Hipple BASIS International
Ltd
I need a little more info on this. What was the
dilemma?
BASIS
IDE enhancement – Resolves the source and tokenized naming dilemma by
allowing programmers to run and debug the program as ASCII, thereby facilitating
the use of the same name for both source and tokenized versions
thanks Steve Nell Mark Systems
|
| Printer inactivity |
  United States |
2007-07-03 08:35:46 |
|
Greetings:
I
am probably just brain dead from the schedule I’ve had lately, but I’m
trying to recall is there was either an ALIAS parameter or MODE= modifier for
printer devices to keep them active. Is there a way to specify a
keep-alive time so that print spoolers don’t think an OPENed printer is
inactive and therefore flush the job?
This
has been a perennial problem with processes that only print something after
long record selects or sorts or those that just report the occasional error to
a printed log while doing some updates. If there was a method for BBj or
Pro5 to just send a NUL every x seconds automatically, that would prevent the
problem. I came up blank on the knowledge base, but I must be missing the
obvious.
Scully
|
[1-3]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|