From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] pico
Date: Tue, 29 Jan 2008 15:35:44 -0500 [thread overview]
Message-ID: <DA9E4326-C4FC-40B5-B4AF-D8E3F7468C2F@mac.com> (raw)
In-Reply-To: <01F55221-80E2-45AE-8BD8-9F7AC1089943@mac.com>
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 <pietro10@mac.com> 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
>>>>
>>>
>>>
>
next prev parent reply other threads:[~2008-01-29 20:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 22:05 [9fans] How to read/write pixels from Memimage Pietro Gagliardi
2008-01-26 14:05 ` Russ Cox
2008-01-26 14:09 ` Pietro Gagliardi
2008-01-26 14:55 ` Russ Cox
2008-01-26 23:22 ` Pietro Gagliardi
2008-01-27 18:05 ` Skip Tavakkolian
2008-01-27 18:55 ` Pietro Gagliardi
2008-01-27 19:29 ` [9fans] pico Steve Simon
2008-01-28 23:36 ` Russ Cox
2008-01-29 0:30 ` Pietro Gagliardi
2008-01-29 5:30 ` Bruce Ellis
2008-01-29 20:33 ` Pietro Gagliardi
2008-01-29 20:35 ` Pietro Gagliardi [this message]
2008-01-29 22:46 ` Russ Cox
2008-01-30 1:13 ` Pietro Gagliardi
2008-01-30 6:53 ` Bruce Ellis
2008-01-30 23:42 ` Pietro Gagliardi
2008-01-30 23:55 ` Pietro Gagliardi
2008-01-31 7:41 ` Bruce Ellis
2008-02-05 3:01 ` Pietro Gagliardi
2008-01-27 19:14 ` [9fans] How to read/write pixels from Memimage Pietro Gagliardi
2008-01-27 23:44 ` Pietro Gagliardi
2008-01-28 0:18 ` Pietro Gagliardi
2008-01-28 1:08 ` Pietro Gagliardi
2008-01-28 1:22 ` erik quanstrom
2008-01-28 3:23 ` Pietro Gagliardi
2008-01-28 9:24 ` mattmobile
2008-01-28 16:20 ` ron minnich
-- strict thread matches above, loose matches on Subject: below --
2002-07-17 23:06 [9fans] pico Fariborz (Skip) Tavakkolian
2002-07-17 21:57 ` Sam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DA9E4326-C4FC-40B5-B4AF-D8E3F7468C2F@mac.com \
--to=pietro10@mac.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).