can I pass NULL for RsslError* when calling rssl functions
If I do not care RsslError, especially when there is not much you can do if function likes rsslReleaseBuffer fails (perhaps it never fail if used correctly).
Best Answer
-
No unfortunately passing nullptr or NULL will result in a fault when an error occurs and the API attempts to assign a value.
With the Elektron-SDK suite of APIs it is highly recommended to test the return values and at least log the result as it significantly aids in diagnosing faults in production environments. For RsslReleseBuffer the API is used to return an object to a memory pool and thus a failure could mean shortly the pool is exhausted and no new data can be processed.
0
Answers
-
Is RsslError::text always populated in case of error? Obviously RsslError::text is more readable than RsslError::rsslErrorId.
1 -
Here's one I made earlier,
if (RSSL_RET_SUCCESS != rsslReleaseBuffer (buf, &rssl_err)) {
LOG(WARNING) << "rsslReleaseBuffer: { "
"\"rsslErrorId\": " << rssl_err.rsslErrorId << ""
", \"sysError\": " << rssl_err.sysError << ""
", \"text\": \"" << rssl_err.text << "\""
" }";
}Other functions sometimes return codes which need helpers to decode,
if (RSSL_RET_SUCCESS != rsslEncodeMsgComplete (, RSSL_TRUE /* commit */)) {
LOG(ERROR) << "rsslEncodeMsgComplete: { "
"\"returnCode\": " << static_cast<signed> (rc) << ""
", \"enumeration\": \"" << rsslRetCodeToString (rc) << "\""
", \"text\": \"" << rsslRetCodeInfo (rc) << "\""
" }";
}Feel free to take examples from my code, I also created a minimal ostream helpers for some additional types.
0 -
Yes, but it may not be informative, you are recommended to log all available data such as the return code, error code, error id, and error text as appropriate. Beware the value-add libraries have added their own error data types and return codes.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛