passing arguments to a CreateNewProc process....etc.

[Noster]

Hi,

1 - It is a C-style function pointer, NOT a BPTR.
2 - NO, the function prototype is: void(*)(void). But you could send a kind of startup-message to the messageport you get as result of the successfull CreateNewProc(). This message will be send to the new process's pr_MsgPort.
3 - I would program a timeout-timer and start the child process from your main program and I would create a public messageport for communication between the child process and your main program. The child would send a message to this public port when it has started successfully. Your main program has to Wait() for the signals of this public messageport and the timerequest after the child has been created. If the timerequest returns before the child has notified the success/result via the public messageport the child has failed.

Noster

[Noster]

[Noster]

Hi,

@Dietmar

> It's easier to pass AllocVec()'ed data in task->tc_UserData. NP_UserData should do the trick but I install it manually, with handshaking via signals.
> Tasks FreeVec()s the data when done with it.

This is hacking and might not work in future releases of the AmigaOS (or if you wish to release a MorphOS or AROS version of your program)..

Noster

[Noster]

Hi,

@Jose

Depending on the kind of data you want to pass you may pass them as string using NP_Arguments.
Poking tc_UserData is not much better code than using global variables in my opinion. Using messages protects from race conditions resp. you don't have to use Forbid()/Permit() (which should be avoided when ever possible).

Noster

[Noster]

Hi,

@Piru

> Anyway, the tag rules indeed. You get rid of that nasty sync/poking crap. Nice idea.

How is NP_UserData defined?

Noster