topic Re: Two developers, one program in Application Development and Automation Discussions

Two developers, one program

Former Member — Thu, 13 Nov 2008 16:04:59 GMT

Subject changed by moderator. Please use a meaningful subject in future

Dear guru ,

i have encountered an issue

we hav a project pressure.

me n my friend both want to write some codes in the same user exit in the same time due to the lack of time

what will be strategy to work on same source of code in same time.

and we know if u r in the editing mode my friend won't b able 2 write in it as it ll b locked by me .

but anyhow I hav 2 do both

how could I do

pls help

Edited by: Matt on Nov 13, 2008 5:35 PM

Re: Two developers, one program

ThomasZloch — Thu, 13 Nov 2008 16:17:46 GMT

you could sit on his lap and code four-handed.

Re: Two developers, one program

Former Member — Thu, 13 Nov 2008 16:37:18 GMT

he may encounter some more issues...

Re: Two developers, one program

matt — Thu, 13 Nov 2008 16:47:36 GMT

Now, chaps, keep it clean...

Saifur Rahaman - create two function modules. One that holds your logic, one that holds his. Call those function modules from the user exit.

matt

Re: Two developers, one program

ThomasZloch — Thu, 13 Nov 2008 16:52:19 GMT

OK OK, so Uwe's excellent blog here might come in handy:

Or if that gun is too big, just create two separate includes.

Thomas

Re: Two developers, one program

uwe_schieferstein — Thu, 13 Nov 2008 16:53:47 GMT

Hello Saifur

You may have a look at my recent blog

[Dangerous Liaisons in User-Exits and How to Avoid Them|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/11882] [original link is broken] [original link is broken] [original link is broken];

which exactly discusses this problem and shows a simple way to organize this.

Regards

Uwe

Re: Two developers, one program

uwe_schieferstein — Thu, 13 Nov 2008 16:54:37 GMT

Thomas, you were faster than me )

Regards

Uwe

Re: Two developers, one program

ThomasZloch — Thu, 13 Nov 2008 16:56:34 GMT

Yes, I really liked that one. I had a similar situation a few years back, with distributed development teams working on the same exits. My solution was not quite as elegant, so I will deploy your design next time.

Cheers

Thomas