Hi Alvin,
I shouldn’t look for “>” or “<“ redirection?
Yes, you only get the part of the command line, which is specific for
the application.
For console I/o does symbos do CR/LF or just LF?
It's always using 13+10 = CR/LF. Though "File_lineinput" accepts the
other variants as well.
Files are always handled in random access mode. So once you opend a file
you can read, write and seek in any way and portion you like. In general
there is no difference between "binary" or "text" or whatever files. But
if you assume it's a text file you can use the File_LineInput function
for fast and easy loading of one textline, which is terminated by CR/LF
or the other combinations (so both Windows/DOS/Linux way is supported).
SymbOS has a global sector cache with a size of 3KB, so it contains up
to 6 sectors. Only sectors, which have been partially accessed, will be
cached.
so there is no quit message or similar indicator set to tidy things up?
Of course there is, usually an application always quits in a controlled way. But there IS the possibility that it is just killed without beeing
notified - e.g. if it's hanging and the user decides to kill it with the
task manager. In most cases this isn't a problem, as the system frees
all used resources (memory areass, processes, open windows)
automatically. In your special case this would be a problem.
Ok so I don't have to worry about the exx set for other restarts?
Erm yes, the other restarts require to save the 2nd registers as well,
as they will switch #0000-#3fff from the first 64K bank into the visible
area, and this will again show a #38 restart, which is not patched. So
you will have to provide 6 functions for replacing the #08, #10, #18,
#20, #28, #30 calls.
so it’s not a simple matter of “don’t use the exx set”
You are right, but especially because of speed optimization I made this decission.
A task scheduler which would allow the usage of the the 2nd registers
would be significant slower because of two reasons:
- it can't hold its own variables and pointers inside the 2nd register
set, so it has to reload and store them from/to memory on any context switch
- it needs to push/pop nearly the double amount of registers for the
task during a context switch
That was the main reason why I decided to forbid the usage of the 2nd
register set. The interrupt handler of the native operating system of
the Amstrad CPC is using the 2nd register set as well, so normal tools
on this machine can't access them, too.
CU,
Prodatron
------------------------------------
Posted by: =?UTF-8?Q?J=c3=b6rn_Mika?= <
jmika@prodatron.net> ------------------------------------
------------------------------------
Yahoo Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/symbos8bit/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/symbos8bit/join
(Yahoo! ID required)
<*> To change settings via email:
symbos8bit-digest@yahoogroups.com
symbos8bit-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
symbos8bit-unsubscribe@yahoogroups.com
<*> Your use of Yahoo Groups is subject to:
https://info.yahoo.com/legal/us/yahoo/utos/terms/