A new Bentley is up. This defines hopefully all of the bitwise
operators I will support:
& | ^ << >> ~ (as in C)
<@ >@ (roll left and roll right, also called circular shift)
I'm still working on the base language, getting type checking working
and allowing logical AND, OR, XO
On May 7, 2008, at 5:24 AM, Matt Erickson wrote:
On 2008-05-02, erik quanstrom <[EMAIL PROTECTED]> pondered onto
the tubes:
one does
if key = 'c' then
scanline
runcommand
else
generate(key)
On 2008-05-02, erik quanstrom <[EMAIL PROTECTED]> pondered onto the tubes:
>> one does
>>
>> if key = 'c' then
>> scanline
>> runcommand
>> else
>> generate(key)
>> assemble(key)
>>
>> This is si
On May 4, 2008, at 10:24 PM, andrey mirtchovski wrote:
Set for the next release: bit arrays.
"I'd use plan 9 before i'd use bitfields" -- pjw
I'm aware of that quote. The design of bit arrays will be totally
different from the design of bitfields. They are true arrays that can
be used in
wow, sounds like a freshman assignment. don't steal ".b" from limbo, use limbo.
brucee
On Mon, May 5, 2008 at 11:45 AM, Pietro Gagliardi <[EMAIL PROTECTED]> wrote:
> I put up a new Bentley. This has support for, hopefully, all control
> structures:
>
>if e then
> > Set for the next release: bit arrays.
>
> "I'd use plan 9 before i'd use bitfields" -- pjw
>
funny, i've only know him as a bit array.
- erik
> Set for the next release: bit arrays.
"I'd use plan 9 before i'd use bitfields" -- pjw
I put up a new Bentley. This has support for, hopefully, all control
structures:
if e then if..then
s
if e then if..then..else
s
else
On Sun, May 4, 2008 at 8:48 AM, Pietro Gagliardi <[EMAIL PROTECTED]> wrote:
> s/one/two/ # don't forget c++
>
If only we could
-eric
s/one/two/ # don't forget c++
On May 4, 2008, at 8:18 AM, Bruce Ellis wrote:
I think the quote of the day was "We already support one C-like
language".
brucee
On Sun, May 4, 2008 at 5:57 PM, <[EMAIL PROTECTED]> wrote:
Just out of curiosity, why did alef die, or are some of you
still using
I think the quote of the day was "We already support one C-like language".
brucee
On Sun, May 4, 2008 at 5:57 PM, <[EMAIL PROTECTED]> wrote:
> > Just out of curiosity, why did alef die, or are some of you
> > still using it?
>
> A victim of rationalisation and reality: maintaining separate
> lib
> Just out of curiosity, why did alef die, or are some of you
> still using it?
A victim of rationalisation and reality: maintaining separate
libraries for two languages is a luxury Plan 9 colud no longer afford,
if I understood the rationale at the time.
++L
As I understand it the load of supporting two libraries was too much work, also
the alef (and perhaps limbo) experience lead to libthread which provides much of
the same functionality - abet not quite as neatly.
the sources of the 2nd edition alef have been released and there was a
one line change
Just out of curiosity, why did alef die, or are some of you
still using it?
--
John Stalker
School of Mathematics
Trinity College Dublin
tel +353 1 896 1983
fax +353 1 896 2282
Well KenC doesn't have any rat with it.
So you want spam spam spam bacon and KenC.
Or python and a bucket.
brucee
On Sun, May 4, 2008 at 12:43 PM, Eric Van Hensbergen <[EMAIL PROTECTED]> wrote:
> On Sat, May 3, 2008 at 6:32 PM, Bruce Ellis <[EMAIL PROTECTED]> wrote:
> > ratpie! tasty. i thought
> Can I have a piece without so much rat in it?
I had stir fried rat in vietnam once - well you gotta try things,
tasted a bit like wild (strong chewy) chicken.
-Steve
On Sat, May 3, 2008 at 6:32 PM, Bruce Ellis <[EMAIL PROTECTED]> wrote:
> ratpie! tasty. i thought a pindent was what a pinhead gets when you
> scone him with a frypan.
>
Can I have a piece without so much rat in it?
-eric
"Its the Bishop of Liechester"
We have two ratpies. They're ruby and perl. Pick your poison.
On May 3, 2008, at 7:32 PM, Bruce Ellis wrote:
ratpie! tasty. i thought a pindent was what a pinhead gets when you
scone him with a frypan.
brucee
On Sun, May 4, 2008 at 9:28 AM, Skip Tavakkolian <[EMAIL PROTECTED]>
wrote:
my ori
ratpie! tasty. i thought a pindent was what a pinhead gets when you
scone him with a frypan.
brucee
On Sun, May 4, 2008 at 9:28 AM, Skip Tavakkolian <[EMAIL PROTECTED]> wrote:
> my original suggestion for ratpy wasn't taken seriously, so i'll propose it
> again:
>
> http://groups.google.com/grou
my original suggestion for ratpy wasn't taken seriously, so i'll propose it
again:
http://groups.google.com/group/comp.os.plan9/msg/29eb245edcb78e91
>>> 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
> the Python distribution includes a tool called 'pindent'. it happily
> annotates Python source with block-closing comments and converts
> haphazardly indented source with block-closing comments into
> correctly indented Python source.
This is irony in a league all of its own!
++L
On 02/05/2008, at 8:34 AM, 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 numb
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
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
> 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
> 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
* 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 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
> 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
> Indentation by white space is a very bad idea in my experience.
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?
:D
Pietro Gagliardi wrote:
> The compiler generates Assembly in a temporary file,
> then calls up the assembler to make the program.
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
On Thu, May 1, 2008 at 9:54 PM, ron minnich <[EMAIL PROTECTED]> wrote:
> On Thu, May 1, 2008 at 9:41 PM, John Barham <[EMAIL PROTECTED]> wrote:
> > > I first saw it in a language in 1978 called Offal, by Aron Insinga.
> >
> > Well with a name like Offal at least he wasn't setting expectations
On Thu, May 1, 2008 at 9:41 PM, John Barham <[EMAIL PROTECTED]> wrote:
> > I first saw it in a language in 1978 called Offal, by Aron Insinga.
>
> Well with a name like Offal at least he wasn't setting expectations too
> high...
>
>
Just about as high as Python went, it turns out :-)
ron
> I first saw it in a language in 1978 called Offal, by Aron Insinga.
Well with a name like Offal at least he wasn't setting expectations too high...
Rob Pike wrote:
> I have lots of other examples of lesser disasters. As code grows,
> white space indentation becomes ever more problematic. It's a
> maintenance disaster.
I beg to differ, at least when it comes to my experience working w/
Python. I work day in and day out on a 50,000+ line P
you can do what you will, with your indentation-based language, but
that won't change the fact that indentation for lexical scope is a
horrible idea.
I first saw it in a language in 1978 called Offal, by Aron Insinga.
Aron was smart: after 6 weeks, he said, "this sucks", and put it away.
When I sa
Pietro Gagliardi wrote:
Put it this way: It's unwise to make program structure depend on
invisible characters.
There's a language made entirely of said invisible characters, called
Whitespace. It's esoteric, but it works. And Python, which has the same
style, is a phenomenal success. Whether
On May 1, 2008, at 10:21 PM, Pietro Gagliardi wrote:
On May 1, 2008, at 9:26 PM, erik quanstrom wrote:
one does
if key = 'c' then
scanline
runcommand
else
generate(key)
ass
On May 1, 2008, at 9:26 PM, erik quanstrom wrote:
one does
if key = 'c' then
scanline
runcommand
else
generate(key)
assemble(key)
This is similar to Python, and prevents the
On May 1, 2008, at 9:12 PM, Federico G. Benavento wrote:
Put it this way: It's unwise to make program structure depend on
invisible characters.
a white space is something hard to find, some time ago I helped a
friend
who couldn't get a mkfile working, he got something like:
"mk: mkfile:6: s
On May 1, 2008, at 9:52 PM, Rob Pike wrote:
Indentation by white space is a very bad idea in my experience.
Superficially attractive but ultimately very dangerous. I once spent a
couple of days tracking down a bug caused by a source-to-source code
tool that broke a major program because the cod
> Put it this way: It's unwise to make program structure depend on
> invisible characters.
a white space is something hard to find, some time ago I helped a friend
who couldn't get a mkfile working, he got something like:
"mk: mkfile:6: syntax error; expected one of :<="
all due to a ' ' in what w
Indentation by white space is a very bad idea in my experience.
Superficially attractive but ultimately very dangerous. I once spent a
couple of days tracking down a bug caused by a source-to-source code
tool that broke a major program because the code it was injecting into
had indented one more sp
(By 'indentation' of course I mean 'indentation to define structure')
-rob
Hello. I started working on Bentley, a new programming language. This
was inspired by and is based on the pseudocode in Jon Bentley's
"Programming Pearls" - a column for the CACM that became a book. The
compiler generates Assembly in a temporary file, then calls up the
assembler to make the
> one does
>
> if key = 'c' then
> scanline
> runcommand
> else
> generate(key)
> assemble(key)
>
> This is similar to Python, and prevents the nesting ambiguity of C,
> Pascal, and some
46 matches
Mail list logo
