Re: Re: Coding question
By: Nelgin to MRO on Sun Nov 11 2018 06:15 pm
> MRO wrote:
> M> Re: Coding question
> M> By: Plt to All on Sat Nov 10 2018 11:33 pm
> >> Re: Coding question
> >> By: Plt to All on Sat Nov 10 2018 23:06:57
> >> > I was looking at some code and I am trying to figure out what does the
> >> > 770
> >> I found the answer to my question.
> M> unbaja creates random designations for stuff that is lost when it
> M> decompiles.
> M> atleast i think that's why.
> M> so if i had a variable that was named BUTT, when decompiled it would give
> M> it another designation
> M> ---
> M> Γûá Synchronet Γûá ::: BBSES.info - free BBS services :::
> Probably more to do with the mode the file is created with. 770 = rwx to both
> owner and group and no permissions to other.
well it's an undocumented feature then.
*FOPEN <int_var> <#> <"str" or str_var> FILE_IO.INC
args: handle access path_and_filename
*------------------------------------------
This function opens or creates a disk file (path_and_filename) for read and/or
write access. This function is the Baja equivalent of the standard C fopen()
function. No file I/O operations can be performed on a file until it has been
opened with this function. The 'handle' argument must be a defined integer
variable name. The 'access' argument is the requested open access. The access
flags (defined in FILE_IO.INC) are:
Access Flag Description
~~~~~~~~~~~ ~~~~~~~~~~~
O_RDONLY Read Only
O_WRONLY Write Only
O_RDWR Read and write
O_CREAT Create (create if doesn't exist)
O_APPEND Append (writes to end of file)
O_TRUNC Truncate (truncates file to 0 bytes automatically)
O_EXCL Exclusive (only open/create if file doesn't exist)
O_DENYNONE Deny None (shareable, for use with record locking)
---
■ Synchronet ■ ::: BBSES.info - free BBS services :::
|
