On 06/05/2016 14:04, Alex Peshkoff wrote: > On 05/06/2016 07:56 PM, Adriano dos Santos Fernandes wrote: >> On 06/05/2016 13:50, Alex Peshkoff wrote: >>> On 05/06/2016 07:39 PM, Dimitry Sibiryakov wrote: >>>> 06.05.2016 18:19, Adriano dos Santos Fernandes wrote: >>>>> Also constructor PathName(const PathName&, const string&) would be good. >>>> Why? It has the same ambiguity: whether to put dir separator in >>>> between or not. >>>> >>> If we talk about ctors - no ambiguity. 2 ctors: >>> >>> PathName(const PathName&, const string&) // no dirsep between >> Disagree. Should separate as that is the common operation, concatenate a >> name with a parent path. >> >> >>> PathName(const PathName&, const PathName&) // dirsep between >>> >> Should not exist IMO. Potentially wrong operation. >> > But PathName is not necessarily _full_ path. File name in CWD (i.e. > something like "filename.ext") is also represented with PathName. > Yes, PathName may represent a relative path, but generally (always?) you know that a path read from somewhere will or not going to be appended with a parent path.
And assuming it's going, you know that this PathName is not a existent (or going to be created) file. So these names is better represented as strings, they are not about real files. Then you combine (concat) this string in another PathName to use. It's much better than have fake PathNames. Adriano ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
