Displaying 4 results from an estimated 4 matches for "api_chang".
Did you mean:
api_changes
2011 Jul 13
0
[LLVMdev] [Frustration] API breakage
...hange is fresh in memory.
I regularly make small API-breaking changes in the name of cleaning
things up. Sorry! I'd be happy to update the release notes if folks
reckon this is the right thing to do. Would it just mean adding a <ul>
to the (currently empty) list in docs/ReleaseNotes.html#api_changes ?
Jay.
2011 Jul 13
4
[LLVMdev] [Frustration] API breakage
Hi all,
I know this issue has been discussed over and over again, but I'd like to
voice my opinion while 3.0 is still fairly early-ish in the pipeline.
So the issue is... API breakage. I understand and agree with the rationale
why, namely faster development. But this principle should mean that for each
breakage, the dude who makes the breakage should accompany the final commit
(or something
2011 Jul 13
1
[LLVMdev] [Frustration] API breakage
...>
> I regularly make small API-breaking changes in the name of cleaning
> things up. Sorry! I'd be happy to update the release notes if folks
> reckon this is the right thing to do. Would it just mean adding a <ul>
> to the (currently empty) list in docs/ReleaseNotes.html#api_changes ?
Sure, that makes perfect sense.
-Chris
2011 Jul 14
2
[LLVMdev] [Frustration] API breakage
...wrote:
> I regularly make small API-breaking changes in the name of cleaning
> things up. Sorry! I'd be happy to update the release notes if folks
> reckon this is the right thing to do. Would it just mean adding a<ul>
> to the (currently empty) list in docs/ReleaseNotes.html#api_changes ?
That's definitely needed. Not every LLVM user tracks development on
trunk very closely and reads every commit message. A quick note about
the nature of API-breaking changes and a hint on how to migrate existing
sources would be really appreciated.
Albert
--
Dr. Albert Gr"af
Dept...