Number: 144

Date: 17-Mar-84  0':27':20

Submitter: Sannella.PA

Source: Stansbury.pa

Subject: Lisp chokes on Mis-parsed filenames':  bytecomp.user.cm

Lisp Version: 14-Mar-84 10':16':58

Description: '
Date': 15 Mar 84 16':21 PST'
Sender': Sannella.pa'
Subject': Lisp': Mis-parsed filenames (unpackfilename or filenamfield)'
To': LispSupport.pa'
From': Stansbury.pa'
Lisp-System-Date': 14-Mar-84 10':16':58'
Machine-Type': Dolphin'
'
There is a file {phylex':}<lispmemos>bytecomp.user.cm which lisp is choking on.  '
'
dir {phylex':}<lispmemos>* creationdate'
'
lists it as bytecomp.user;cm and then tries the getfileinfo with that name, causing a file not found error.'
'
Can''t we get filenames like this to parse as (filename bytecomp.user.cm version nil) rather than (filename bytecomp.user version cm)?'
'
-- Tayloe.'


Workaround: 

Test Case: 

Edit-By: Masinter.PA

Edit-Date: 17-Aug-84 22':37':52

Attn: Release

Assigned To: Masinter

In/By: 

Disposition: 17 Aug 84, lmm': I fixed UNPACKFILENAME to parse A.B.C as NAME A.B extension C but A.B.3 as NAME A EXTENSION B VERSION 3.'
'
Not absolutely the best, but I think it is more reasonable. This was a problem with *ALL* file devices, not just NS services, thus "Generic File" rather than "NS Filing"

System: Operating System

Subsystem: Generic File Operations

Machine: 

Disk: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Difficulty: Moderate

Frequency: Everytime

Impact: Moderate

Priority: Perhaps

Status: Fixed

Problem Type: Bug

Source Files: