Re: http://www.ora.com/news/vhll_1299.html

2001-07-10 Thread Ask Bjoern Hansen
On Mon, 9 Jul 2001, Sam Tregar wrote: [...] > On Mon, 9 Jul 2001, Adam Turoff wrote: > Um, that's not what the article was talking about The proposal is to use > an XML syntax to program in existing "VHLL" languages, including Perl. > This would supposedly allow programmers to embed drawings as

do.. while and label operators..

2001-07-10 Thread Edward Peschko
hey A small nitpick, but I really do hope that perl6 includes a 'next', 'last', etc for 'do..while'.. enclosing every condition on which to actually do the block becomes a real pain: do { if ($dont_skip || $dont_skip2) { } } while (..) I'd much rather: do { nex

Re: Per-object inheritance in core a red herring?

2001-07-10 Thread David L. Nicol
Adam Turoff wrote: > > On Tue, Jul 10, 2001 at 02:08:58AM -0500, David L. Nicol wrote: > > Uh, C++ virtual methods can be overloaded on a per-object basis, not > > just a per-class basis, since the object drags around its virtual jump > > table with it wherever it goes, so the jump can get compil

Re: Between-Opcode Callbacks

2001-07-10 Thread Jarkko Hietaniemi
On Tue, Jul 10, 2001 at 09:45:19PM +0200, Paul Johnson wrote: > On Mon, Jul 09, 2001 at 11:46:30PM -0500, Jarkko Hietaniemi wrote: > > > > > > > XML > > is > > much > > too > > verbose > > And it should be neither written nor read by people ;-) Thank you, at least someone got my po

Re: Per-object inheritance in core a red herring?

2001-07-10 Thread David L. Nicol
Adam Turoff wrote: > And what's the linguistic hook that allows C++ object-based inheritance? > And where's the guarantee that vtbls are per-object and not per-class? > > Z. You're right, it might be a side effect of a particular implementation of virtual methods. But AIUI that implementation

Re: Between-Opcode Callbacks

2001-07-10 Thread Paul Johnson
On Mon, Jul 09, 2001 at 11:46:30PM -0500, Jarkko Hietaniemi wrote: > > > XML > is > much > too > verbose And it should be neither written nor read by people ;-) > . > > -- Paul Johnson - [EMAIL PROTECTED] http://www.pjcj.net

Re: "You can't make a hot fudge sundae with mashed potatoes instead of ice cream, either."

2001-07-10 Thread John Porter
[EMAIL PROTECTED] wrote: > ...just made them a convenience for identifying type errors... I.e. type-safe macros. -- John Porter

Re: "Implied types, first try." Or "Its amazing what you can do with potatoes"

2001-07-10 Thread John Porter
David L. Nicol wrote: > First off, I'm going to pound on one of my deceased horses a bit: I'll add one obligatory thwack with my own barbed flog, David. Hear hear. > > my Num$dec = 4.0; > > my Int$int = $dec; # Num -> Int okay since 4.0 truncates to 4 > >

Re: "Implied types, first try." Or "Its amazing what you can do with potatoes"

2001-07-10 Thread Steve Fink
Michael G Schwern wrote: > On Mon, Jul 09, 2001 at 08:54:49PM -0700, Steve Fink wrote: > >>my Num $x = 3.0; >>$x++; >>my Int $y = $x; >> >>Could be compile-time, if you do constant folding first. >> > > Alot of how much checking we can do at compile-time depends on how > long we have to compile

Re: Per-object inheritance in core a red herring?

2001-07-10 Thread Dan Sugalski
At 02:10 PM 7/10/2001 -0400, Mark J. Reed wrote: >Not quite authoritative, I'm afraid. :) I'm looking at the new edition >of the Stroustroup book, and the very existence of vtables is an >implementation detail not guaranteed by the language spec (now that >there actually is a language spec for C++

Re: Per-object inheritance in core a red herring?

2001-07-10 Thread Mark J. Reed
Not quite authoritative, I'm afraid. :) I'm looking at the new edition of the Stroustroup book, and the very existence of vtables is an implementation detail not guaranteed by the language spec (now that there actually is a language spec for C++). Further, in the example which mentions vetables,

Re: Per-object inheritance in core a red herring?

2001-07-10 Thread Dan Sugalski
At 11:01 AM 7/10/2001 -0400, Adam Turoff wrote: >And where's the guarantee that vtbls are per-object and not per-class? VTABLES ARE PER OBJECT. So mote it be. :) Dan --"it's like this"--- Dan Sugalski

Re: reparsing the ambiguous

2001-07-10 Thread Dan Brian
> I wonder how long (less than a year?) it will be until people are writing > computer languages that know enough about context to select a parsing that > Makes Sense when faced with an ambiguous construction. Not long. My Linguana talk/paper @ TPC treats (in part) a natural language programming

Re: Per-object inheritance in core a red herring?

2001-07-10 Thread Adam Turoff
On Tue, Jul 10, 2001 at 02:08:58AM -0500, David L. Nicol wrote: > Uh, C++ virtual methods can be overloaded on a per-object basis, not > just a per-class basis, since the object drags around its virtual jump > table with it wherever it goes, so the jump can get compiled into > "jump to the address

Re: Per-object inheritance in core a red herring?

2001-07-10 Thread David L. Nicol
[EMAIL PROTECTED] wrote: > Anyhow, if you want Perl 6 objects to be able to act as if they're in > their own class (ie. have their own methods, inheritance, etc...) how > are you going to do this without having the moral equivalent of a > stash associated with it? And if you can do something that