[BUG] Where is croutine.c in the main branch?

[jwestmoreland]

Hello All,

Looked in the docs - at least what I could find in the rev history - has croutine.c been removed?

Just wondering - maybe I missed something.

It's there in the v10.5.1 branch/tag.

Thanks!
John W.

[rawalexe]

Hello John W.,
We have depreciated croutine.c you can find the place holder here. Please use v10.5.1 if you still need them.

Please let me know if have any other queries.

Best Regards,
Anubhav Rawal

[jwestmoreland]

Anubhav,

Has the functionality in croutine.c been incorporated someplace else?

Thanks,
John W.

[rawalexe]

Greetings John,
We noticed that the c file hadn't been touched in a long time and we never had a questions or pull requests on it. After a careful considerations we felt that it was safe to remove the file as most folks were using larger processors and weren't in need of the file. However if you still need them, you can find them from the v10.5.1 release . As the file has been stable for a long time you can still use the past version of the file.

Hopefully this helps. Please let us know if you have more questions.

Best Regards,
Anubhav Rawal

[jwestmoreland]

Anubhav,

OK - so, no one's using a stack challenged processor these days, OK.

Or - some others may notice when 10.5.1+ is released.

Hopefully Richard sees this comment and chimes in.

Thanks,
John W.

[RichardBarry]

Hi John - noted - I will discuss with the team Monday.

[jwestmoreland]

Hello Richard,

Interested to hear what's decided.

I have a few things in the pipeline here - on one especially that's 'ram challenged' - pretty sure we will end up using co-routines.

Thanks!
John

[RichardBarry]

Hi John - we decided to add the file back into the git repo, and then update co-routine related website pages noting co-routines are no longer under development. I hope that is agreeable for you.

[jwestmoreland]

Hello Richard,

That's fine.

Thanks!
John

[AniruddhaKanhere]

Since the above PR has been merged, we will close this issue. Please feel free to reopen this thread if you feel that your issue wasn't resolved correctly.