westonpace commented on issue #10:
URL: https://github.com/apache/arrow-cookbook/issues/10#issuecomment-894855192
I think that could be a workable solution. I do think you will end up with
a lot of cookbooks and then if you find a grammar issue for example you have to
fix it in several places. That being said, you could always have a limit on
how many versions of Arrow we support. For example, only keep the cookbooks
for 2 years of Arrow versions or something. I don't plan on going quite that
far with the C++ cookbook anytime soon although maybe someone else will want
to. Do you think the different cookbooks need to align on how they approach
this? I was hoping for C++ to be able to do something like this...
```
BEGIN_RECIPE("Xyz", 3.0.0) {
DoThingOldFashionedWay();
}
BEGIN_RECIPE("Xyz") {
DoThingNewWay();
}
```
This would then use the older method for versions <= 3.0.0 and the newer
method for all other version. However, I could compile this into multiple
cookbooks as easily as a single cookbook with dropdown selectors.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
