Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
102 user(s) are online (80 user(s) are browsing Forums)

Members: 1
Guests: 101

rjd324, more...

Support us!
Donate

Headlines
Recent files - OS4Depot - Your one stop for AmigaOS4 files

 
Jump to the bottom of the page Bottom    View previous topic Previous Topic    View next topic Next Topic

  Register To Post  

« 1 (2)
ChrisH
Re: Get WB params without using main() ?
Posted on: 2011/6/30 11:09    #21
Home away from home
Home away from home


See User information
@whose
I agree with Hans that your proposed method would be an extremely bad idea, since it would rely on undocumented OS features that could change at any time. So you & Hans do not need to worry

Author of the PortablE programming language.
Go to top
jaokim
Re: Get WB params without using main() ?
Posted on: 2011/7/4 18:55    #22
Just popping in
Just popping in


See User information
How about patching IDOS->System with a function that records each application's arguments? So when you need it it's already stored in an array.
Go to top
centaurz
Re: Get WB params without using main() ?
Posted on: 2011/7/4 23:29    #23
Just popping in
Just popping in


See User information
@jaokim

You won't catch a lot of WB programs by patching System().
Go to top
ChrisH
Re: Get WB params without using main() ?
Posted on: 2011/7/5 13:19    #24
Home away from home
Home away from home


See User information
@all
Don't worry, I already solved my problem by using a totally different approach

Author of the PortablE programming language.
Go to top
whose
Re: Get WB params without using main() ?
Posted on: 2011/7/5 18:28    #25
Just popping in
Just popping in


See User information
Would you share your totally different approach with us?

Go to top

  Register To Post
« 1 (2)

 
Jump to the top of the page Top    View previous topic Previous Topic    View next topic Next Topic




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2024 The XOOPS Project