Opened on 03/07/2018 at 01:41:35 PM
Last modified on 03/29/2018 at 11:42:44 AM
#6452 new change
Use INI parser natively from emscripten branch of adblockpluscore
| Reported by: | sergz | Assignee: | |
|---|---|---|---|
| Priority: | P2 | Milestone: | |
| Module: | Libadblockplus | Keywords: | |
| Cc: | rjeschke, hfiguiere, oleksandr | Blocked By: | #6180, #6477 |
| Blocking: | #6520 | Platform: | Unknown / Cross platform |
| Ready: | no | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description
Background
In order to use emscripten C++ code natively in libadblockplus we firstly want to try something relatively small and what is not widely used. INI parser seems the best candidate for it.
What to change
It will be researched, both projects libadblockplus and adblockpluscore[emscripten] have to be changed.
Attachments (0)
Change History (4)
comment:1 Changed on 03/13/2018 at 06:33:26 PM by sergz
- Blocked By 6180 added
comment:2 Changed on 03/23/2018 at 10:37:21 AM by sergz
- Blocked By 6477 added
comment:3 Changed on 03/23/2018 at 05:33:09 PM by sergz
- Blocking 6520 added
comment:4 Changed on 03/29/2018 at 11:42:44 AM by sergz
- Cc hfiguiere oleksandr added
- Owner sergz deleted
Note: See
TracTickets for help on using
tickets.
One can find the progress in that regard in gitlab sandbox group (unfortunately it's private, at least so far).
The branch in libadblockplus is called issue-6452, it uses adblockpluscore repo residing also in that gitlab group, denepdencies file is updated accordingly (though not tested), JIC the branches are issue-6452 and issue-6452-emscripten in adblockpluscore repo.
Because of ad-hoc changes of priorities, I'm revoking my self so far. IMO the next steps would be to work on #6520 in order to see whether we can get the benefit in the memory usage.