Small problem

Afrow UK · 12th April 2005, 14:59

I found a small problem (think it's an error by design) but ${__LINE__} is reset when used in an !include file.

It's a problem when used in labels because we get ${__LINE__} being the same twice in the same script (could be line 11 in main script, and then 11 again in the included script).

Perhaps a solution would be to get ${__LINE__} to be added on from where it left off (at the !include call)?

-Stu

kichik · 12th April 2005, 16:54

${__LINE__} was not designed for that purpose. If you want a globally unique verifier you can throw in ${__FILE__} and even ${__TIMESTAMP__}.

Afrow UK · 13th April 2005, 18:36

Good idea. ${__FILE__} would do the trick for !includes.

-Stu

12th April 2005, 14:59	#1
Afrow UK Moderator Join Date: Nov 2002 Location: Surrey, England Posts: 8,434	Small problem I found a small problem (think it's an error by design) but ${__LINE__} is reset when used in an !include file. It's a problem when used in labels because we get ${__LINE__} being the same twice in the same script (could be line 11 in main script, and then 11 again in the included script). Perhaps a solution would be to get ${__LINE__} to be added on from where it left off (at the !include call)? -Stu

12th April 2005, 16:54	#2
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	${__LINE__} was not designed for that purpose. If you want a globally unique verifier you can throw in ${__FILE__} and even ${__TIMESTAMP__}. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

13th April 2005, 18:36	#3
Afrow UK Moderator Join Date: Nov 2002 Location: Surrey, England Posts: 8,434	Good idea. ${__FILE__} would do the trick for !includes. -Stu