From mboxrd@z Thu Jan  1 00:00:00 1970
From: dexen deVries <dexen.devries@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Date: Mon, 25 Jul 2011 17:00:19 +0200
User-Agent: KMail/1.13.6 (Linux/3.0.0-l35+; KDE/4.5.5; x86_64; ; )
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201107251700.19492.dexen.devries@gmail.com>
Subject: [9fans] [p9p] problem with mk: variable being truncated
Topicbox-Message-UUID: 05ed3d9a-ead7-11e9-9d60-3106f5b1d025

hi,

this regards plan 9 port.

with a very simple mkfile, $prereq and $newprereq get truncated at slightly=
=20
below 16*1024 characters.

essence of the mkfile:

allfiles=3D`{find -name '*.c'}
foo:VQ: $allfiles
	echo $newprereq
#	(alternatively: echo $prereq)



it seems to me formatted output library (fmt) is to blame, perhaps around t=
he=20
twisted code of counting formatted characters. poking in mk internals, down=
 in=20
dorecipe() i've stumbled upon a debug print():

print("lt=3D%s ln=3D%s lp=3D%s\n",wtos(head.next, ' '),wtos(ln.next, '=20
'),wtos(lp.next, ' '));

which (when un-commented) also prints truncated dump of the variable.

one clue i got so far is that adding a small print() after it fixes the out=
put=20
*from the debug print*:
print("\n");

any help or hints please?


regards,
=2D-=20
dexen deVries

[[[=E2=86=93][=E2=86=92]]]

=46or example, if the first thing in the file is:
   <?kzy irefvba=3D"1.0" rapbqvat=3D"ebg13"?>
an XML parser will recognize that the document is stored in the traditional=
=20
ROT13 encoding.

(( Joe English, http://www.flightlab.com/~joe/sgml/faq-not.txt ))