Re: Appending to file.patterns.bash
"'Neil Hodgson' via scite-interest" <[email protected]> Tue, 26 Sep 2023 11:17:20 +1000
| Newsgroups | gmane.editors.scite.general |
|---|---|
| Message-ID | <[email protected]> |
ed.adasiewicz: > I find the restriction confusing since what I was trying to do was nothing more than using "variable=value" with value containing the value of another variable - as stated in the docs. It's not *another* variable, it's the *same* variable. This is similar to 'recursively expanded' variables used in 'make' for as opposed to 'simply expanded' variables. https://www.gnu.org/software/make/manual/html_node/Recursive-Assignment.html https://www.gnu.org/software/make/manual/html_node/Simple-Assignment.html For an example of why this is done, consider a Java compilation in global properties: command.compile.*.java=javac $(FileNameExt) If $(FileNameExt) was simply expanded when global properties was read then it wouldn't be able to build a Java file opened later. With recursively expanded variables, $(FileNameExt) is expanded just before the command is executed which allows it to see the current value of the file path and build the right file. Neil -- You received this message because you are subscribed to the Google Groups "scite-interest" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/scite-interest/0F14AB07-3B05-42E0-9B30-1215BBCD93E8%40me.com.