| | [ Return to Bugs & Features | Roadmap 1.1 | SVN ⇄ GIT ]
STR #277
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 2 - Low, e.g. a documentation error or undocumented side-effect |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Documentation |
|---|
| Summary: | Error in Fl_Text_Buffer documentation |
|---|
| Version: | 1.1.4 |
|---|
| Created By: | ciudadsatan.hotmail |
|---|
| Assigned To: | mike |
|---|
| Fix Version: | 1.1.5rc1 |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
No files
Trouble Report Comments:
| |
| #1 | ciudadsatan.hotmail
03:52 Feb 05, 2004 |
| Fl_Text_Buffer documentation isn't clear regarding if the pointer returned by certain functions should be free'd, delete'd or just leave them alone.
Functions are:
highlight_text()
line_text()
secondary_selection_text()
selection_text()
text_in_rectangle(int,int,int,int)
text_range(int,int)
text();
I thought the pointers returned weren't supposed to be free'd nor delete'd, mainly because their type is "const char*". Now, looking at the headers, they return "char*". This should be fixed in the docs, too.
| |
| |
| #2 | mike
17:45 Feb 29, 2004 |
| Fixed in CVS - the anonymous CVS repository will be updated at midnight PST. | |
[ Return to Bugs & Features ]
|
| |
