The documentation in the manual says to get full name of a file, you
should send fullName message actual image has no such message, it has full I'm assuming the documentation is wrong even though, fullName seems a more logical message name than full. Which is in error? Paolo. should I do a patch to fix whichever is in error? _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
Sean Allen wrote:
> The documentation in the manual says to get full name of a file, you > should send > > fullName message > > actual image has no such message, it has > > full > > I'm assuming the documentation is wrong even though, fullName seems a > more logical message > name than full. > > Which is in error? Sending #full (that's the name of the message that is spelled "full", like #at:put: is the name of the message that is spelled "at: ... put: ...") is correct. I avoided the term "name" because it is used for some messages that return a String. Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
On Jan 8, 2009, at 1:13 AM, Paolo Bonzini wrote: > Sean Allen wrote: >> The documentation in the manual says to get full name of a file, you >> should send >> >> fullName message >> >> actual image has no such message, it has >> >> full >> >> I'm assuming the documentation is wrong even though, fullName seems a >> more logical message >> name than full. >> >> Which is in error? > > Sending #full (that's the name of the message that is spelled "full", > like #at:put: is the name of the message that is spelled "at: ... put: > ...") is correct. I avoided the term "name" because it is used for > some > messages that return a String. k well the manual has fullName listed. http://www.gnu.org/software/smalltalk/manual-base/html_node/File_002dfile-name-management.html#File_002dfile-name-management so that is an incorrect manual entry. _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
> k well the manual has fullName listed. > > http://www.gnu.org/software/smalltalk/manual-base/html_node/File_002dfile-name-management.html#File_002dfile-name-management > > so that is an incorrect manual entry. Ah, I see. #fullName was present up to 3.0; in 3.1 it is the same as #name and can be replaced with it. #full returns a new File instance. I added back #fullName and updated the manual. Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
> I updated the manual. Done. In the new manual (for 3.1) FilePath is a superclass of File, so you'll see most of the methods you want under http://www.gnu.org/software/smalltalk/manual-base/html_node/FilePath.html#FilePath Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
On Jan 8, 2009, at 7:57 AM, Paolo Bonzini wrote: > >> I updated the manual. > > Done. In the new manual (for 3.1) FilePath is a superclass of File, > so > you'll see most of the methods you want under > > http://www.gnu.org/software/smalltalk/manual-base/html_node/FilePath.html#FilePath so all these are part of FilePath not File? http://www.gnu.org/software/smalltalk/manual-base/html_node/File_002dtesting.html#File_002dtesting _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
Sean Allen wrote:
> > On Jan 8, 2009, at 7:57 AM, Paolo Bonzini wrote: > >> >>> I updated the manual. >> >> Done. In the new manual (for 3.1) FilePath is a superclass of File, so >> you'll see most of the methods you want under >> >> http://www.gnu.org/software/smalltalk/manual-base/html_node/FilePath.html#FilePath >> > > so all these are part of FilePath not File? > > http://www.gnu.org/software/smalltalk/manual-base/html_node/File_002dtesting.html#File_002dtesting The manual includes all methods defined in a class. An object responds to methods in a class and its superclasses. You're more likely to find interesting methods in FilePath than in File. http://www.gnu.org/software/smalltalk/manual-base/html_node/FilePath_002dtesting.html includes more messages than the URL you found, because for example FilePath can implement isRelative as ^self isAbsolute not I'll add a list of inherited methods in each category to the manual, as time permits. Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
On Jan 8, 2009, at 8:05 AM, Paolo Bonzini wrote: > Sean Allen wrote: >> >> On Jan 8, 2009, at 7:57 AM, Paolo Bonzini wrote: >> >>> >>>> I updated the manual. >>> >>> Done. In the new manual (for 3.1) FilePath is a superclass of >>> File, so >>> you'll see most of the methods you want under >>> >>> http://www.gnu.org/software/smalltalk/manual-base/html_node/FilePath.html#FilePath >>> >> >> so all these are part of FilePath not File? >> >> http://www.gnu.org/software/smalltalk/manual-base/html_node/File_002dtesting.html#File_002dtesting > > The manual includes all methods defined in a class. An object > responds > to methods in a class and its superclasses. > > You're more likely to find interesting methods in FilePath than in > File. > > http://www.gnu.org/software/smalltalk/manual-base/html_node/FilePath_002dtesting.html > includes more messages than the URL you found, because for example > FilePath can implement isRelative as > > ^self isAbsolute not > > I'll add a list of inherited methods in each category to the manual, > as > time permits. > Ok, so the manual should have all inherited methods ( I assumed the opposite ) but that isnt done across the board. Am I correct on that? Just want to make sure. As long as that is the case, I'll stop pointing them out. _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
> Ok, so the manual should have all inherited methods ( I assumed the > opposite ) but that isnt done across the board. The manual has only *redefined* methods (the manual is automatically generated, so at least it is consistent :-)). To see all inherited methods, the only way is to look up the superclass. It's very good anyway that you pointed out this -- I see how it can be confusing, and there's an easy fix. Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
On Jan 8, 2009, at 8:11 AM, Paolo Bonzini wrote: > >> Ok, so the manual should have all inherited methods ( I assumed the >> opposite ) but that isnt done across the board. > > The manual has only *redefined* methods (the manual is automatically > generated, so at least it is consistent :-)). To see all inherited > methods, the only way is to look up the superclass. It's very good > anyway that you pointed out this -- I see how it can be confusing, and > there's an easy fix. AH... I get it. So whats the easy fix going to be so, when it happens, I don't get confused all over again? _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
>> The manual has only *redefined* methods (the manual is automatically >> generated, so at least it is consistent :-)). To see all inherited >> methods, the only way is to look up the superclass. It's very good >> anyway that you pointed out this -- I see how it can be confusing, and >> there's an easy fix. > > AH... I get it. So whats the easy fix going to be so, when it happens, > I don't get confused all over again? Modify the manual generation so that it adds a link to each superclass, and a short list of methods from the superclasses. The comments won't be duplicated though for brevity. Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
> > Modify the manual generation so that it adds a link to each superclass, > and a short list of methods from the superclasses. The comments won't > be duplicated though for brevity. > A link to the superclass would be very helpful. It is something I've wished for often... at the moment one has to keep scrolling to the top of the page to get the list of classes when looking up methods in a superclass. Stephen _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
Free forum by Nabble | Edit this page |