Need to use the file access commands for a add in I have been making, but i know I am doing something very stupid, but for the past 3 hours have come up short on what that is.
The most basic segmant of code to show this would be the following:

Code:

For some reason the handle always ends up being some random number not always negative or positive. No matter if the file tester.py exists or not.

I have no idea what I am doing wrong.

So a few things here:

• You should be checking the result of the Bfile_OpenFile_OS() system call.
  
• What is basic_printer8? Assuming it uses printf-style formatting, %i is fine, but %d would be more correct here.
  
• Nit:might as well make name be const. And let name be the correct length (in this case, 17) without specifying it.

It's confusing to me that you get random positive and negative numbers that don't seem to correlate with the existence of the tester.py file. I would expect this code to look like:


Code:

A bit more info would be aside from some extraneous warnings I disabled there are no warning thrown out by GCC.

There's no such thing as an extraneous warning. What are the warnings?

They really are just there to fill the terminal with spam.


Code:


Also when I comment out said lines no warnings are in the section of testing code I posted.

Quick question to make testing easier, if the function is working properly would it return any positive number or would it return a number in the range of 0-15?

Ok it has gotten weirder, I swear that is wasn't like this when I was previously testing, but now if the file doesn't exist it always seems to return -1.

And if it does then it either returns a non -1 negative number or will return 2^24+something. With me not being sure what prompts either result while the code is different between the 2 testing programs I made, the Bfile reference is the same among both of them and yet each of the different testing progs consistently gives that different result.

Is it expected behavior for it to return 2^24+something small, if the file does exist?

I finally figured out the issue.

Since I was just testing if the Bfile_OpenFile_OS command worked in a vacuum I never used any other Bfile commands. As such I never used the CloseFIle command. It seems that the files a program has open are never closed upon the program exiting/ opening a different program.
Resulting in it either failing or giving the next file handle. Not sure what specifically causes either result but at least the issue is fixed.

I'm very surprised to hear that file handles are not closed when a different add-in is run and then your program is re-run, but I'm glad you were able to solve your issue.