On Dec 7, 2008, at 8:46 AM, John E. Malmberg wrote:
> John E. Malmberg wrote:
>> The mp_do_pathify_dirspec needed enhancements to more accurately
>> parse VMS file specifications, and also to handle UNIX file
>> specifications the same way that mp_do_tovmspath() does.
>> It was simpler to replace than to try to modify the existing routine.
>> In addition this is the start of fixing issues where routines can
>> be called with a null thread context, by removing the thread
>> context where it is not needed.
>> More patches will be following this.
>
> An additional note, this patch may cause some tests in vmsfspec.t to
> fail. That is because the old behavior of pathfiy_dirspec() was
> inconsistent with vmsify().
>
Specifically:
not ok 92 - pathify('/__down_/__the_/__garden_/__path_.'): '/__down_/
__the_/__garden_/__path__/'
# Failed at [.lib]vmsfspec.t line 24
# got '/__down_/__the_/__garden_/__path__/'
# expected ''
...
not ok 94 - pathify('/__down_/__the_/__garden_.__path_'): '/__down_/
__the_/__garden____path_/'
# Failed at [.lib]vmsfspec.t line 24
# got '/__down_/__the_/__garden____path_/'
# expected ''
...
not ok 106 - pathify('__path_.notdir'): '__path__notdir/'
# Failed at [.lib]vmsfspec.t line 24
# got '__path__notdir/'
# expected ''
> I am working on a new version of vmssfspec.t that handles both the
> traditional mode of perl and with the decc$efs_charset / decc
> $filename_unix_report modes activated.
>
How does this plan address the failures above?
________________________________________
Craig A. Berry
mailto:craigberry@mac.com
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
Thread Previous
|
Thread Next