[Xorp-cvs] XORP cvs commit: xorp/rtrmgr

Bruce M Simpson bms@spc.org
Mon, 11 Jul 2005 09:40:48 +0100


On Sat, Jul 09, 2005 at 07:47:41PM +0000, Mark Handley wrote:
> 	Now the following works (hacking an existing XRL for test purposes):
> 	
> 	%set: xrl "$(interfaces.targetname)/ifmgr/0.1/set_mtu?tid:u32=$(interfaces.TID)&ifname:txt=blah $(#) $(<>) $(@) foo&mtu:u32=$(@)";
> 	
> 	Note the three-variable expansion in ifname. This expands the way you'd expect:
> 	
> 	[ 19518   +62 unexpanded_xrl.cc ] XRL expanded to fea/ifmgr/0.1/set_mtu?tid:u32=0&ifname:txt=blah 10200000000 : 3 foo&mtu:u32=3
> 	
> 	Now be careful you don't go and put any & into your variables, or I've
> 	no idea what will happen.

Hopefully there aren't any Win32 NDIS drivers out there which name their
adapter instances with a & in the stem string. I haven't seen any in the wild
that I can think of.

Can we support UTF-8 for 'txt' values? FriendlyNames are meant to be unicode,
but Microsoft's APIs for dealing with them are inconsistent; some calls are
ASCII only.

BMS