On 09/05/2016 12:36, Dimitry Sibiryakov wrote: > 06.05.2016 20:20, Alex Peshkoff wrote: >> Why file name should be represented as a string, not PathName? It does >> not follow from what you say before. Moreover, if we need to correctly >> compare that file name with another one we must "use PathName ... to >> solve". I.e. to correctly work with file name it should be represented >> as PathName, not generic string. > Do you think that following test cases produce a right results in terms of > appending > some user-configured directory to a base Firebird directory? Can you suggest > some more > complicated test cases? > > C:\abc\ + def\ghi = C:\abc\def\ghi ...
> C:\abc\ + D:\ = D:\ This is C# Path.Combine logic. If second argument is absolute, return it. > C:\abc\ + \qwe\rty\..\uio\ = C:\qwe\uio\ This should be as the rule above. Second argument is absolute (relative to current drive, but still absolute), so if we want this logic, should be = \qwe\uio\ which you may later interpret relative to current drive. C:\abc\ should be discarded as in above rule. > C:\abc\ + ..\qwe\.\rty\\uio\. = C:\qwe\rty\uio\ > ... 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
