Replies: 2 comments 1 reply
|
Technically it's not a split at all - it's a downstream fork, regularly synced with upstream. It's 100% compatible with FPC: it's FPC with features on top. The only catch is that if you use those features, they simply don't exist in stock FPC. Bugfixes already flow back: when I hit an FPC bug, I send the patch upstream, and a few have been merged. The language features are the other side of it. They're in the fork precisely because upstream said no, so merging them back is upstream's call, not mine. The code is open, and if they ever want any of those features, they're free to merge them. I'm not counting on it, though - that's the reason the fork exists in the first place. |
|
That’s what I suspected regarding why the features aren't making it into the upstream. It’s a real shame. Still, it’s good that you’re trying to keep that option open. Maybe the time will come eventually :) Is this a hobby project for you, or are there bigger plans behind it? |
Uh oh!
There was an error while loading. Please reload this page.
To what extent is the fork an irreversible split from FPC? Is there any chance of a merge back into FPC?
All reactions