> The idea is simple: indentation as block style.
Religious matter. Do as you wish, but expect flames.
> Another feature I hope to supply is bit arrays.
ok
> Bentley also will have nested functions, a Pascal-like for statement
> (with variable steps instead of 1/-1), and a loop statement for
On Fri, 02 May 2008 08:49:24 BST John Stalker <[EMAIL PROTECTED]> wrote:
> > To ensure programmers will use good style, Bentley will lack goto. To
> > break out of nested loops, you can use the breakout statement.
>
> This worries me. When I need to implement a finite state autonomon I
> usual
* Bakul Shah ([EMAIL PROTECTED]) wrote:
> Clearly he has a lot of enthusiasm but I don't understand why
> he is squandering it on implementing boring old language
> ideas.
Old ideas have the benefit of already being there.
On May 2, 2008, at 6:14 AM, Anant Narayanan wrote:
Hi,
Is there a tool available which can convert plan 9 a.out executables
to plan 9 assembly code? I'd like to know how the C compiler stores
arguments for a system call on the stack for x86.
8c -S does not help, since all it displays is:
Hi,
Is there a tool available which can convert plan 9 a.out executables
to plan 9 assembly code? I'd like to know how the C compiler stores
arguments for a system call on the stack for x86.
8c -S does not help, since all it displays is: `call print', instead
of what instructions are actu
i normally give the -a option to 8l(1)
> Hi,
>
> Is there a tool available which can convert plan 9 a.out executables
> to plan 9 assembly code? I'd like to know how the C compiler stores
> arguments for a system call on the stack for x86.
>
> 8c -S does not help, since all it displays is: `call print', instead
> of what instruc
> i normally give the -a option to 8l(1)
or use db(1) or acid(1)
> That sounds somewhat similar to Dan Bernstein's qhasm
> (http://cr.yp.to/qhasm.html) which is a semi-portable assembly
> language combining C-like syntax w/ direct access to registers.
> Anathema to the Plan 9 philosophy I suppose but given that clock
> speeds seem to have hit a wall it's one way
> it could just be possible that you're using an editor that is not
> aware of the particular indentation requirements of said language, no?
>
> does it, at least, implement color coding?
you wascale wabble wowser! you're won of those pwython wuffians, awren't
you?
- erik
Robert William Fuller wrote:
I don't use Python for this very reason. This is probably why Ruby
exists. I will not use your language for the same reason. By adopting
such draconian white space rules you automatically alienate a large
number of programmers.
A blind programmer once told me
why does "upas/nedmail -c fubar3" create /mail/box/quanstro/fubar3/mbox
and not /mail/box/quanstro/fubar3?
minooka; upas/nedmail -c fubar3
creating new mbox: /mail/box/quanstro/fubar3/mbox
- erik
Chad Dougherty wrote:
Robert William Fuller wrote:
I don't use Python for this very reason. This is probably why Ruby
exists. I will not use your language for the same reason. By
adopting such draconian white space rules you automatically alienate a
large number of programmers.
A blind
> why does "upas/nedmail -c fubar3" create /mail/box/quanstro/fubar3/mbox
> and not /mail/box/quanstro/fubar3?
Because 'mail quanstro/fubar3' delivers to
/mail/box/quanstro/fubar3/mbox
and not /mail/box/quanstro/fubar3.
Russ
>> why does "upas/nedmail -c fubar3" create /mail/box/quanstro/fubar3/mbox
>> and not /mail/box/quanstro/fubar3?
>
> Because 'mail quanstro/fubar3' delivers to
> /mail/box/quanstro/fubar3/mbox
> and not /mail/box/quanstro/fubar3.
sure enough. but why does it do that?
- erik
>>> why does "upas/nedmail -c fubar3" create /mail/box/quanstro/fubar3/mbox
>>> and not /mail/box/quanstro/fubar3?
>>
>> Because 'mail quanstro/fubar3' delivers to
>> /mail/box/quanstro/fubar3/mbox
>> and not /mail/box/quanstro/fubar3.
>
> sure enough. but why does it do that?
Because 'mail qu
> > Yes, /lib/rfc/grabfc. Uncomment this line:
> >
> > /cron/sys/cron:#30 9 * * * local /lib/rfc/grabrfc
>
> thank you. unfortunately, it turns out that this script causes
> something that looks like deadlock between ramfs and ftpfs.
> i didn't get a bead on ramfs before ftpfs exited but it
>>> Because 'mail quanstro/fubar3' delivers to
>>> /mail/box/quanstro/fubar3/mbox
>>> and not /mail/box/quanstro/fubar3.
>>
>> sure enough. but why does it do that?
>
> Because 'mail quanstro' delivers to /mail/box/quanstro/mbox
> and not /mail/box/quanstro.
that makes sense. thanks.
however
All your previous questions were about mail delivery,
which I think is pretty consistent about not having
special cases.
> however, i'm not sure i fully understand the situation. why does
> echo fu | upas/marshal -Fs bar quanstro/baz
> deliver the copy to
> /mail/box/quanstro/(f/)?qua
>> however, i'm not sure i fully understand the situation. why does
>> echo fu | upas/marshal -Fs bar quanstro/baz
>> deliver the copy to
>> /mail/box/quanstro/(f/)?quanstro_baz
>> and not
>> /mail/box/quanstro/baz/(f/)?quanstro
>> where it would land if i filed it after-the-fact w
> ☺. i found it by reading the source. i was trying to track
> down all the places where mailboxes are fidded in the upas
> source.
>
> it does seem very wierd and marshal does a shimmy to
> pull it off. it would seem the only way to file outgoing
> & incoming mail to/from the same person in th
> ah, so the nedmail rf command invokes marshal -F.
> i would be inclined to change -F to take the name
> of the file, so that nedmail can be the sole arbiter of
> what goes where.
don't forget acme mail.
touching the poison upas is a thankless deal,
but at least one makes no progress. and the
s
>> ah, so the nedmail rf command invokes marshal -F.
>> i would be inclined to change -F to take the name
>> of the file, so that nedmail can be the sole arbiter of
>> what goes where.
>
> don't forget acme mail.
the "pick a save file based on address" logic is unique
to nedmail. acme mail has n
>> ☺. i found it by reading the source. i was trying to track
>> down all the places where mailboxes are fidded in the upas
>> source.
>>
>> it does seem very wierd and marshal does a shimmy to
>> pull it off. it would seem the only way to file outgoing
>> & incoming mail to/from the same perso
> there's one problem with that. marshal saves a copy of the
> email after all the attachments have been made.
>
> i can't replicate this easily with -C.
>
> echo x | upas/marshal -C quanstro/quanstro -s y quanstro/z
> Mail from 'quanstro'
> to 'quanstro/quanstro' alias `local!quanstro/quanstro
>> there's one problem with that. marshal saves a copy of the
>> email after all the attachments have been made.
>>
>> i can't replicate this easily with -C.
>>
>> echo x | upas/marshal -C quanstro/quanstro -s y quanstro/z
>> Mail from 'quanstro'
>> to 'quanstro/quanstro' alias `local!quanstro/
26 matches
Mail list logo
