× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Jim Essinger wrote:

I had tried single quotes in the script, but not double quotes. I don't
know why I didn't think of that. It works well, forcing the jar command in
the script to accept the white space in the path name.

I _think_ "weak" and "strong" are to indicate the amount and/or kind of 'protection' that is given to the quoted value. "Strong" quotes provide full protection -- whatever you type between the quotes will be protected from all the stuff that can happen from parameter substitution and other possible effects. "Weak" quotes pretty much act merely as delimiters -- the stuff between the quotes is still subject to change though the effects are held within the limits.

If you put a variable name within "weak" quotes, the value of the variable may/will replace the variable name. If you put it between "strong" quotes, then all you're going to get is just that name as the value.

Weak or strong? Am I simply marking an area? or do I want protection? It might not be correct, but it works for me.

Tom Liotta


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.