From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v753) In-Reply-To: <01F55221-80E2-45AE-8BD8-9F7AC1089943@mac.com> References: <20080128233615.B0DC61E8C2B@holo.morphisms.net> <775b8d190801282130y7dd93844h41db113c87e34168@mail.gmail.com> <01F55221-80E2-45AE-8BD8-9F7AC1089943@mac.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Pietro Gagliardi Subject: Re: [9fans] pico Date: Tue, 29 Jan 2008 15:35:44 -0500 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Topicbox-Message-UUID: 3c8a4838-ead3-11e9-9d60-3106f5b1d025 This only happens with black/white images, I ran a color image (boyd) through and it worked fine. I think it's with the run function... On Jan 29, 2008, at 3:33 PM, Pietro Gagliardi wrote: > In the latest update, I tried adding differentiating between color > and b/w images. However, I can't test anything because every time I > try a line like > > x new = dennis > > I get something that ends in "(double-free?)" and then the program > crashes, but something like > > x new > x new = > > do call the error() function. The lexer did not change since I > started this update, but it did change when I improved symbol > handling. > > On Jan 29, 2008, at 12:30 AM, Bruce Ellis wrote: > >> well i agree that russ did a good job but JITs are fun and often >> make things 10 times faster. >> >> brucee >> >> On Jan 29, 2008 11:30 AM, Pietro Gagliardi wrote: >>> Wow, that's very impressive! >>> >>> open: /tmp/something does not exist (2x) >>> no image lerp >>> no image doug >>> >>> But you have a preview, which I was going to add soon. >>> >>> I am sticking with my code interpreter because I know how to use one >>> (I toiled over hoc. and fossil ate my code up last December) and it >>> doesn't require hooking to a C compiler. I do like the preprocessor >>> idea though. >>> >>> >>> On Jan 28, 2008, at 6:36 PM, Russ Cox wrote: >>> >>>>> Byron Rakitzis (of posix rc fame) produced a version popi with the >>>>> JIT >>>>> compiler, though sadly his where for cpus which are common cpus >>>>> these days. >>>> >>>> Computers and compilers are fast enough now >>>> that you can get away with just feeding code >>>> into a C compiler instead of writing a full JIT. >>>> And there's no porting to do! >>>> >>>> I just put a pico on sources that does this - 738 lines, >>>> not many of which are the "JIT". >>>> >>>> 9fs sources >>>> cd /n/sources/contrib/rsc/pico >>>> mk demo >>>> >>>> Russ >>>> >>> >>> >