Re: [Csnd-dev] [EXTERNAL] [Csnd-dev] RFC: OENTRY refactor

I remembered there was some discussion on the subject. Now I see what it is.
It answers the question I put here yesterday. 
The only change is that we are redeploying aopadr for dotard. If the renaming is a good
idea we can do that too.

If no one objects, I will move to get rid of .thread.
========================
Prof. Victor Lazzarini
Maynooth University
Ireland

> On 3 Jan 2024, at 22:42, Steven Yi <[email protected]> wrote:
> 
> *Warning*
> This email originated from outside of Maynooth University's Mail System. Do not reply, click links or open attachments unless you recognise the sender and know the content is safe.
> Hi All,
> 
> I was looking at OENTRY and think we can make a change to simplify it by:
> 
> 1. Remove .thread 
> 2. Remove .aopadr
> 3. Rename .iopadr to initFunc
> 4. Rename .kopadr to perfFunc 
> 
> There's little code to check ->thread and I think it can be refactored to check the presence of initFunc or perfFunc. I think initFunc and perfFunc might be a little easier to understand for modern devs vs. iopadr and kopadr. 
> 
> Thoughts?
> 
> Steven