@itix

Quote:

ASCII string is nothing but an array of bytes.

Can be handled internally in the library or device function, and so it should not be a issue, after all all functions in all devices, are nothing more then a function made available, and is handled in the same way as any other function whit in your application.

Unless strings are kept in global system lists, or distributed whit SendMsg(), or DoIO() it should not be a problem, in the future at least is how I see it.

Last edited by NutsAboutAmiga on 24-Jul-2012 at 07:00 PM.

_________________
Software developer and forum troll.
Please check out my software:
Excalibur, Basilisk 2, AmigaInputAnywhere.

@broadblues

Quote:

On AmigaOS *ALWAYS*

I thought I had seen some new resource tracking functions where the programmer had use them himself which went against brojen program recovery. However, there are some functions the system uses itself and the new Exec allocator function allow to specify tracking with release hooks.

Quote:

do think then the home owner needn't lock their doors?

No.

Quote:

The same goes for other platforms too, did you ever see a programing article / tutorial that didn't cleanup after itself, close file handles, free allocated memory etc?

For a full example no.

Quote:

There are many things that can't be forcably cleaned up at the moment. Windows being a good example.

I see this reason a lot, but think they can. If not fully removed a window can be shrunk down to size. It can be removed from the window list and cleaned off the screen. If possible its bitmap freed.

Shrinking is better than doing nothing!

Quote:

Indeed *recover* froma *bad* app. Not enable a lazy coder to get away with writing a bad app.

Note that I'm not avocating bad programming. Just a better rescure scenario. I'd agree that expecting the system to clean up if it could is sloppy.

@itix

Quote:

For example what if RT allocated resource is shared?

They should be nullified and removed off a working list with no more access allowed.

Quote:

For example a message port allocated using RT could be passed to another process (i.e. it can be simply a reply port) and that message port is suddenly freed by RT system?

A message port is small so keeping it active or in memory wouldn't hurt that much. Futher to my last statement it should be frozen and all messages replied if possible. Removed if safely done so.

Quote:

On Amiga resource tracking can cause a snowball effect.

I can see that happening but it's something that needs to be worked on either way. The way it is now is too dirty. More effort needs to be put into cleanly removing a task and freeing up its resources.

Quote:

But to handle crashed application only safe procedure to recover is full reboot.

Then AmigaOS has a lot of work to do! Other systems have had this ability for years now or at least deal with it better. . Time we caught up!

Quote:

ASCII string is nothing but an array of bytes.

Yes, byte aligned.

Althopugh FIBs contain bytes the quad byte nature gives other restirctions.


Quote:

But anyway it is not mistake to use AllocDosObject(). You know it works and it is enough.

It does. It might also be possible to specify a compiler alignement attribute. Infact could this have been put into an include file?

Or even. can a structure be allocated in the globals, then turn out to be aligned?