Knowing you mike, there must be a good reason for that statement, but I recognize I don't understand that one. What I tested and verified (which must be incomplete) is that on 3 targets(mac,win32,linux) the construction in the script "'$myvar'" is expanded as $myvar and not the content of the variable.
flk2 doesn't add any quote at all, you choosed the simple+double quote combination. My understanding is that the "$var" construct was permitting to consider the expansion of $myvar as only one parameter even if it contained separators (i.e:white spaces) as it can happen in some filenames. So I think the fltk2 solution may potentially cause problem of this order because of this absence of double quotes. But even in the case that simples quotes are not preventing expansion when contained in double quotes, my question would be why using simple quotes then ? Thanks for any clue. ----- Message d'origine ---- De : Michael Sweet <[EMAIL PROTECTED]> À : [email protected] Envoyé le : Jeudi, 28 Août 2008, 21h56mn 13s Objet : Re: [fltk.development] [fltk.commit] [Library] r6175 - branches/branch-1.3 [email protected] wrote: > Author: fabien > Date: 2008-08-28 11:12:23 -0700 (Thu, 28 Aug 2008) > New Revision: 6175 > Log: > STR #2028 fix: single quotes changed to double quotes around the variable > $compile to make it interpreted, Thanks alvin Reverting since this change is incorrect. -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
