How to put brackets "(" into batch script comment lines "::"
Dennis Halver
:: some comment ( sometext ) more text
then the brackets (especially the closing bracket) is interpreted as command or end of comment.
How do I force the command interpreter to really treat EVERYTHING in the comment line as comment?
Do I really have to "mask" the brackets?
Dennis
Richard Bonner
> When I put into a batch command script a comment line like
> :: some comment ( sometext ) more text
> then the brackets (especially the closing bracket) is interpreted as
> command or end of comment.
> How do I force the command interpreter to really treat EVERYTHING in the
> comment line as comment?
> Dennis
*** DOS users can ignore this. Using double colons in a DOS batch
file will permit any characters within a comment. I don't know why
Microsoft made that to differ in NT systems.
--------
For more on DOS characters:
http://www.chebucto.ca/~ak621/DOS/DOS-Char.html
Richard Bonner
http://www.chebucto.ca/~ak621/DOS/
Paul Bartlett
> Dennis Halver (ha...@persrec.com) wrote:
>> When I put into a batch command script a comment line like
>
>> :: some comment ( sometext ) more text
>
>> then the brackets (especially the closing bracket) is interpreted as
>> command or end of comment.
> [trim]
> *** DOS users can ignore this. Using double colons in a DOS batch
> file will permit any characters within a comment. I don't know why
> Microsoft made that to differ in NT systems.
I presume that Microsoft is on a vendetta to kill any forms of DOS come
hell or high water so that most of the world will be trapped into using
their expensive and buggy Windoozy operating so-called "systems"
whether people want to use them or not. Years ago I was professionally
involved with what were then almost the only computers around, namely,
"big iron" mainframe systems. Although they were not the only player,
IBM ruled the roost. "Standards? What do you mean, standards? We
are IBM. That is all we need to say." Eventually they got somewhat of
their comeuppance. Perhaps if the Linux community can hang in there
long enough, Microsoft may get their comeuppance also. Sadly, as much
as I like DOS, I am not optimistic for its long term future, unless it
may be that someone can some up with a genuinely workable 32-bit DOS
with native LFN support.
--
Paul Bartlett
Richard Bonner
> On Sat, 27 Jun 2009, Richard Bonner wrote:
> > Dennis Halver (ha...@persrec.com) wrote:
> >> When I put into a batch command script a comment line like
> >
> >> :: some comment ( sometext ) more text
> >
> >> then the brackets (especially the closing bracket) is interpreted as
> >> command or end of comment.
> > [trim]
> > *** DOS users can ignore this. Using double colons in a DOS batch
> > file will permit any characters within a comment. I don't know why
> > Microsoft made that to differ in NT systems.
> I presume that Microsoft is on a vendetta to kill any forms of DOS come
> hell or high water so that most of the world will be trapped into using
> their expensive and buggy Windoozy operating so-called "systems"
> whether people want to use them or not.
*** Microsoft is famous for breaking competing operating systems and
software. Lately, they are trying to break the alphabet and control
codes. )-:
> Years ago I was professionally
> involved with what were then almost the only computers around, namely,
> "big iron" mainframe systems. Although they were not the only player,
> IBM ruled the roost. "Standards? What do you mean, standards? We
> are IBM. That is all we need to say." Eventually they got somewhat of
> their comeuppance. Perhaps if the Linux community can hang in there
> long enough, Microsoft may get their comeuppance also.
*** It won't be a complete comeuppance because at some point, in order
to survive, they will return to being more compatible with those systems,
as they once were with systems of the past. Recently a buddy of mine
installed a new system at a paper plant. They went with Linux even though
Microsoft relaxed some of its rules so as to compete. In the end, Linux
was chosen in part because the likelihood that Linux will be broken some
time down the road is less than with Microsoft. This was even though the
MS system was price competitive.
> Sadly, as much
> as I like DOS, I am not optimistic for its long term future, unless it
> may be that someone can some up with a genuinely workable 32-bit DOS
> with native LFN support.
> --
> Paul Bartlett
*** Peope are trying but the resources just aren't there. It would need
some big company or big bucks behind it.
Richard Bonner
http://www.chebucto.ca/~ak621/DOS/