To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcxOpen lugnet.robotics.rcx in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / 198
197  |  199
Subject: 
Re: fast firmware downloader
Newsgroups: 
lugnet.robotics.rcx
Date: 
Mon, 1 Nov 1999 14:24:19 GMT
Viewed: 
1272 times
  
Dave Baum wrote:

In article <000001bf232a$bf046c80$0500000a@pro150>, "Ralph Hempel"
<rhempel@bmts.com> wrote:

What do you think Dave? There are not too many filenames that are too
long. Do you think we could chop the long ones so things work on any
platform?

Sorry, but I'm going to be stubborn on this one.  I abhor short (often
cryptic) filenames.  In the NQC source tree, almost every class is in its
own file, which is of course named after the class.  So in a sense,
truncating the filenames is more than just renaming files - it also either
requires classnames to be changed, or it breaks the class/filename
convention.  I'm not happy with either alternative.

I agree with your reasoning.  The compiler I have decided to use (Watcom C/C++
v.11
from Powersoft) will compile from the platform I am developing on (NT 4) to the
desired executing platform (DOS) and will use long file names just fine.  Other
compilers have the same ability.  I see no reason to alter the filenames when
there is no need and in doing so you lose a bit of the code's readability.

Is there seriously the need to be able to build NQC on an 8.3 system?  I'm
not talking about running the executable - but actually performing the
build.  If so, how well do those compilers handle long filenames in
#includes?  Do they just look for the truncated name?  If so, things may
work fine as is - offhand I don't think there are any collisions when
truncating to 8.3.  Anyone tried this?

Dave

--
reply to: dbaum at enteract dot com



Message has 1 Reply:
  RE: fast firmware downloader
 
(...) Great! I was using Borland C++ 3.0 because I happened to have the diskettes around. Remember when a C++ compiler fit on 5 (five) 3.5 diskettes? I have no problem with keeping the existing filename structure. It's readable, it serves the (...) (25 years ago, 1-Nov-99, to lugnet.robotics.rcx)

Message is in Reply To:
  Re: fast firmware downloader
 
(...) Sorry, but I'm going to be stubborn on this one. I abhor short (often cryptic) filenames. In the NQC source tree, almost every class is in its own file, which is of course named after the class. So in a sense, truncating the filenames is more (...) (25 years ago, 1-Nov-99, to lugnet.robotics.rcx)

5 Messages in This Thread:

Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR