Jump to content

FS PROCESSNAME: Difference between revisions

From EDM2
Created page with "Allow an FSD to modify filename to its own specification after the OS/2 canonicalization process has completed. ==Syntax== FS_PROCESSNAME(pNameBuf) ==Parameters== ;pNameB..."
 
Ak120 (talk | contribs)
mNo edit summary
 
Line 1: Line 1:
Allow an FSD to modify filename to its own specification after the OS/2 canonicalization process has completed.  
Allow an FSD to modify filename to its own specification after the OS/2 canonicalization process has completed.


==Syntax==
==Syntax==
  FS_PROCESSNAME(pNameBuf)
  FS_PROCESSNAME(pNameBuf)
==Parameters==
==Parameters==
;pNameBuf: is a pointer to the ASCIIZ pathname.  
;pNameBuf: is a pointer to the ASCIIZ pathname.
 
:The FSD should modify the pathname in place. The buffer is guaranteed to be the length of the maximum path. The FSD does not need to verify this pointer.
:The FSD should modify the pathname in place. The buffer is guaranteed to be the length of the maximum path. The FSD does not need to verify this pointer.  


==Calling Sequence ==
==Calling Sequence==
<PRE>
<PRE>
int far pascal FS_PROCESSNAME(pNameBuf)
int far pascal FS_PROCESSNAME(pNameBuf)


char far * pNameBuf;
char far * pNameBuf;
</PRE>


</PRE>
==Remarks==
==Remarks==
The resulting name must be within the maximum path length returned by DosQSysInfo.  
The resulting name must be within the maximum path length returned by DosQSysInfo.


This routine allows the FSD to enforce a different naming convention than OS/ 2. For example, an FSD could remove blanks embedded in component names or return an error if it found such blanks. It is called after the OS/2 canonicalization process has succeeded. It is not called for FSH_CANONICALIZE.  
This routine allows the FSD to enforce a different naming convention than OS/2. For example, an FSD could remove blanks embedded in component names or return an error if it found such blanks. It is called after the OS/2 canonicalization process has succeeded. It is not called for FSH_CANONICALIZE.


This routine is called for all APIs that use pathnames.  
This routine is called for all APIs that use pathnames.


This routine must return no error if the function is not supported.
This routine must return no error if the function is not supported.


[[Category:IFS Interfaces]]
[[Category:IFS Interfaces]]
{{DISPLAYTITLE:FS_PROCESSNAME}}
{{DISPLAYTITLE:FS_PROCESSNAME}}

Latest revision as of 06:03, 10 February 2020

Allow an FSD to modify filename to its own specification after the OS/2 canonicalization process has completed.

Syntax

FS_PROCESSNAME(pNameBuf)

Parameters

pNameBuf
is a pointer to the ASCIIZ pathname.
The FSD should modify the pathname in place. The buffer is guaranteed to be the length of the maximum path. The FSD does not need to verify this pointer.

Calling Sequence

int far pascal FS_PROCESSNAME(pNameBuf)

char far * pNameBuf;

Remarks

The resulting name must be within the maximum path length returned by DosQSysInfo.

This routine allows the FSD to enforce a different naming convention than OS/2. For example, an FSD could remove blanks embedded in component names or return an error if it found such blanks. It is called after the OS/2 canonicalization process has succeeded. It is not called for FSH_CANONICALIZE.

This routine is called for all APIs that use pathnames.

This routine must return no error if the function is not supported.