Re: Can't compile DOS program with long file name
Juergen Luethje wrote:
> Igor Kachan wrote:
>
> >
[snip]
> > Ok, it is not *too* excellent, it is just *almost* excellent.
> > It is just not that bad, I think now.
>
> I'm glad that it is fine for you. However, that does not change the fact
> that it is everything else but excellent for me (as I wrote previously).
I'm sorry, you are right, I share your problem,
and it has 3 possible solutions:
1. Just now - just rename - just yours one.
2. Rob uses yours method about long names.
3. Rob abandones support for pure DOS.
As I'm an old lazy crazy, I vote for yours solution #1,
and it works just now, for you too (with some pain to you,
but what to do, I'm sorry, but this is the simplest way).
> > I know that German language does allow very and very long
> > combined words, it is just a champion language about long
> > words, but me myself can not say something like to
> > 'ethyloxyethylparaphenilendiaminsulphate' without 5 breakes
> > in the middle of this not too long word. 
>
> It does not matter whether or not I (or other Germans) can say so or not.
> I'm 48 years old, an not too silly. So rest assure that I know myself
> very well how to name my files properly.
Ok, you are right, I'm sorry, but please do not take all these
my 5 breakes too seriously, I just wanted to say that reading
of all these long names is my problem, I do not like long names
anyway, I like same libs for any and all platforms and try to
avoid long names in my own work.
Long names is my problem, I'm 60, lazy, and do not want
to type all these long names and then read them and search for
my typos.
It was a good idea about long file names, but now you can meet
a file with content which is shorter than own file's name.
For example, one my file has name 'language.er' consists of
a single byte and takes 4K of an empty disk space on a FAT32 disk.
I'm sorry about all these my problems, you may skip them
without reading.
> >> Since I always try to write code in include files as generic and
> >> cross-platform as possible, your suggestion means that I would have to
> >> rename all my .e library files, so that they only use old DOS 8.3 names.
> >
> > Yes, if you want these libs to work on pure DOS, you have to
> > name them as 8.3.
>
> Yes. But not if I use them in a DOS window on Windows. And it is _my_
> decision what I want to do, not yours or anyone else's.
Ok, I do understand yours decision and yours wish.
But for now it has some restriction, if you operate with ec.exe.
But me myself has the decisions and wishes *opposite* to yours ones.
What to do? I'm agreed with yours excellent for me solution #1.
Great #1 !!!
> > The Watcom compiler cares about pure DOS.
> > This Open Watcom supports 16 bit DOS too.
> >
> >> Just last week at work, I had to search for some old files (about 10
> >> years old) on CD, which all had 8.3 DOS names. It was a pain! I am very
> >> happy that we now can use more characters in order to give the files
> >> more meaningful names. I don't understand why I deliberately should want
> >> to do without it.
> >
> > What to do, it is just that old good time of PC, PC XT, PC AT etc.
>
> I just was trying to say that using these old 8.3 names is a pain for me.
> You are not able or not willing to understand that.
I do understand your pain very well, be sure, I'm sorry about
your pain, but I think this your pain is rare, not constant,
just sometimes. That was your first complaint about ec.exe.
And all pure DOS users do not have that pain at all, it is just
usual DOS life.
> >> And it should be easy for Rob to fix it. Just compiling ec.ex with DJGPP
> >> instead of Watcom probably should do the trick, see:
> >
> > <<a
> > href="http://www.listfilter.com/cgi-bin/esearch.exu?fromMonth=">http://www.listfilter.com/cgi-bin/esearch.exu?fromMonth=</a>>
> > .. see next line
> > 8&fromYear=A&toMonth=8&toYear=A&postedBy= .. see next line
> > Juergen+Luethje&keywords=%222005+Aug+17+6%3A17%22> ..
> >
> > Ok, it is the end of your single word, Juergen ...
>
> Mmm? What does "end of your single word" mean?
On web interface, all these lines look just as a single word in a single line,
yours single word in German style, very long word, nothing more.
> > I see now what you do like to see ...
>
> I have said all the time clearly what I like to see:
> A Euphoria DOS compiler that can handle files with long names when run in
> a DOS window on Windows (because on plain DOS it is not possible at all).
Ok, I do understand you very well, but imagine please
yourself with this long-name-DOS32-program on plain DOS.
ec.exe now automatically doesn't allow such a program.
And it is a good feature, I think.
With it, I'll have working programs for pure DOS and for DOS window,
and just now.
> And in the meantime I have learned that introducing long file names was
> a great mistake, because it was the end of the "old good time".
Not that great, not that mistake, but 8.3 names are not too bad,
they just remind us about that "old good time".
Regards,
Igor Kachan
kinz at peterlink.ru
|
Not Categorized, Please Help
|
|
