|
Bugzilla – Full Text Bug Listing |
| Summary: | Changing visibility of StartApplication and StopApplication method in Application class | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | Alex Afanasyev <alexander.afanasyev> |
| Component: | network | Assignee: | ns-bugs <ns-bugs> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | mathieu.lacage, tomh, tommaso.pecorella |
| Priority: | P5 | ||
| Version: | ns-3-dev | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | patch | ||
|
Description
Alex Afanasyev
2012-02-29 21:33:10 UTC
Created attachment 1349 [details]
patch
(In reply to comment #1) > Created attachment 1349 [details] > patch Looks OK to me; any other comments? Same here, +1 T. The problem with this patch is that it is not ok to sometimes chain up and sometimes not chain up: we must be consistent. I have no problem with chaining up in principle but we should at least make sure that our own subclasses _do_ chain up. Please, update the doc of the base class methods too. I figured out that there is no reason to do chaining, at least in this case. (Start|Stop)Application don't do anything at all in base class. |