[bug #62150] [afmtodit] should not write full file names to "name" directive of font descriptions

[Dave]

Follow-up Comment #5, bug #62150 (project groff):

Hmm, it now occurs to me: is this script guaranteed to be run on a file system
that uses "/" as the directory separator?  If it needs to be more general,
perl has a basename() function in its standard File::Basename module
<http://perldoc.perl.org/File::Basename> that is aware of the OS's
conventions.

[comment #4 comment #4:]
> A fellow student in my high school programming class
> (Pascal-based) discovered for himself the arbitrariness
> of variable names, recognizing that the machine did not
> care what we called them.  So on one occasion he named
> something, I think it was a loop index, "BANANA".

A coding session for one of my advanced college programming classes stretched
into the wee hours, and my project partner and I were a little slap-happy.  At
one point when he was at the keyboard, we realized we needed a new variable
for some flag.  He asked me what we should name it, and I offered "Fred."  He
dutifully typed this in, and it remained in the code we eventually submitted. 
Moral: Do not listen to me when it comes to naming variables.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62150>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/