RE: ArraysãBY: Reaper Man to U. CraZy Diamond on Thu Jun 24 1999 11:07 pmãã > > Angus made a workaround that actually worked but it was only a workaroundã > > still frustratingly limited. :(ã > ã > work around???ã > now this is quite interesting?ã > I'd be happy to see this work around and its "short-coming" after all if I cã > emmulate and array then that is good enough for me.ããI'll look around and see if I can't dig it up for ya... I wouldn't have deletedãit on purpose.ããAngus? Remember this?ãããã---ã þ Synchronet þ °±² The Serial Port ²±° ¯807ù547ù2134ã

RE: ArraysãBY: Angus Netfoot to U. CraZy Diamond on Fri Jun 25 1999 09:48 amãã > > Angus made a workaround that actually worked but it was only a workaroundã > > still frustratingly limited. :(ã > >ã > ã > Yes, and if I recall it made for a significant performance bottleneck. Itã > involved generating Baja BIN files on-the-fly and then EXEC_BINing them toã > access the data element. Worked, but was naturally slow due to the multipleã > disk-accesses involved.ããRight. AIIRC it also required an excessive amount of coding. I remember doingãa few experiments with it and although it worked for the most part it wasn't asãeffective as one would hope for.ãPretty clever, tho. If I can find it d'you mind if I repost it here?ããã---ã þ Synchronet þ °±² The Serial Port ²±° ¯807ù547ù2134ã

RE: ArraysãBY: U. CraZy Diamond to Angus Netfoot on Sun Jun 27 1999 07:33 amãã > > Yes, and if I recall it made for a significant performance bottleneck. Iã > > involved generating Baja BIN files on-the-fly and then EXEC_BINing them tã > > access the data element. Worked, but was naturally slow due to the multiã > > disk-accesses involved.ã > ã > Right. AIIRC it also required an excessive amount of coding. I remember doã > a few experiments with it and although it worked for the most part it wasn'tã > effective as one would hope for.ã > Pretty clever, tho. If I can find it d'you mind if I repost it here?ããGo right ahead. I would have done so except all my experimental code-fragsãwent west when the BBS box blew up.ããIf you can't find it I can probably re-generate some examples.ããã---ã þ Synchronet þ telnet://talamasca-bbs.com http://www.talamasca-bbs.comã

RE: ArraysãBY: U. CraZy Diamond to Reaper Man on Sun Jun 27 1999 07:24:00ãã > > work around???ã > > now this is quite interesting?ã > > I'd be happy to see this work around and its "short-coming" after all if ã > > emmulate and array then that is good enough for me.ã > ã > I'll look around and see if I can't dig it up for ya... I wouldn't have deleã > it on purpose.ã > ã > Angus? Remember this?ããalmost enough to make me sit down and seriously learn how to do com i/o inãqbasic <shudder>ãã---ã þ Synchronet þ Flamin' Torch BBS - The Board on Fireã

RE: ArraysãBY: U. CraZy Diamond to Angus Netfoot on Sun Jun 27 1999 07:33:00ãã > Right. AIIRC it also required an excessive amount of coding. I remember doã > a few experiments with it and although it worked for the most part it wasn'tã > effective as one would hope for.ã > Pretty clever, tho. If I can find it d'you mind if I repost it here?ããhere is another prob, what are the limitations to disk i/oãcan I read from anywhere in a file and write to anywhere?ãã---ã þ Synchronet þ Flamin' Torch BBS - The Board on Fireã

RE: ArraysãBY: Reaper Man to U. CraZy Diamond on Mon Jul 05 1999 05:57 pmãã > here is another prob, what are the limitations to disk i/oã > can I read from anywhere in a file and write to anywhere?ããOf course. But you will have to know the field lengths and positions of yourãtarget file and use FLOCK & FUNLOCK to lock the portions you areãreading/writing to/from as well as FSET_POS to move around to these fileãpositions.ãThen use FREAD and FWRITE for file I/O.ãie: To read and write to a 25 char field from a file at file position 256-281ãyou would open the file in the usual manner, thenããFSET_POS <file handle> 256 SEEK_SET # Move to beginning of recordãFREAD <file handle> <var> 25 # Read what's there into <var>(str or int)ãFSET_POS <file handle> -25 SEEK_CUR # Move back to file positionãFLOCK <file handle> 25 # Lock that fieldãFWRITE <file handle> <source> 25 # Write (overwrite) at the current file ã # position from <source>(str or int)ãFSET_POS <file handle> -25 SEEK_CUR # (sigh) move back to file positionãFUNLOCK <file handle> 25 # Unlock that recordããThat's basically it in a nutshell and you will have to fill in the blanks andãadd other code required for proper flow and error checking but should point outãsome of the pitfalls you might discover whilst trying this. :)ããHope it helps.ãã _UCD_ãã---ã þ Synchronet þ °±² The Serial Port ²±° ¯807ù547ù2134ã

RE: ArraysãBY: U. CraZy Diamond to Reaper Man on Sat Jul 10 1999 11:09:00ãã > That's basically it in a nutshell and you will have to fill in the blanks anã > add other code required for proper flow and error checking but should point ã > some of the pitfalls you might discover whilst trying this. :)ããi see what you have there and it is most impressive...ãIt never occured to me to lock the file when I writeãAlso I kinda taylored the code for use in a program where data is readãin sets of 3 and written in 1 piece but I am going to save these postsãso that Ican make my head go boom after the quake2 game is over..ããã---ã þ Synchronet þ Flamin' Torch BBS - The Board on Fireã