From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Arseniy Aharonov <aaharonov@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Multi-versioning for backward compatibility
Date: Wed, 1 Feb 2023 18:33:56 +0300 [thread overview]
Message-ID: <20230201183356.291e29d4@sovereign> (raw)
In-Reply-To: <MW4PR12MB5666792D438D8C0CDC0FA343CBD19@MW4PR12MB5666.namprd12.prod.outlook.com>
2023-02-01 14:54 (UTC+0000), Arseniy Aharonov:
> This method can't work in Windows with MSVC (at least to the best of my knowledge).
In Windows generally, not limited to MSVC.
> How does DPDK solve if in Windows for MSVC? I failed to find the answer.
It just doesn't.
Fortunately, symbol versioning is not the approach used in DPDK by default.
For example, there are currently no versioned symbols AFAICT.
The preferred approach is:
1) to keep new functions experimental (there are precise rules for how long)
2) to consider possible future extensions when defining new APIs
prev parent reply other threads:[~2023-02-01 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 14:54 Arseniy Aharonov
2023-02-01 15:33 ` Dmitry Kozlyuk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230201183356.291e29d4@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=aaharonov@nvidia.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).