[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New very simple methodology to create a m-file compiler.

From: GoSim
Subject: Re: New very simple methodology to create a m-file compiler.
Date: Tue, 7 May 2019 11:06:20 -0500 (CDT)

Carlo de Falco-2 wrote
>> Il giorno 07 mag 2019, alle ore 13:32, Nicholas Jankowski <

> jankowskin@

> > ha scritto:
>> On Mon, May 6, 2019 at 23:34 Andrew Janke <

> floss@

> > wrote:
>> On 5/6/19 11:13 PM, Nicholas Jankowski wrote:
>> > 
>> > I haven't identified any non-custom function that produces highly
>> > polymorphic output yet, maybe someone else can think of one. 
>> I've got a few.
>>  I guess what this boils down to is if you are going to require the user
>> to avoid polymorphism on outputs, and you are going to throw an Error
>> when they don’t , how will you be able to tell when they don’t? And if
>> you’ve gone through the problem of detecting all of the cases where they
>> Might not,  at that point wouldn’t it be better to just deal with the
>> polymorphism somehow  rather than require them to avoid one of the more
>> useful aspects of the programming language? 
> also, what is the actual purpose of this thread in the first place?
> is the OP poster proposing to change the grammar of the language in order
> to make it easier to compile?
> if you are looking for a language symilar to (but not compatible with)
> matlab that is faster to parse and compile then why not just look at
> https://julialang.org/ ?
> c.

The purpose is to make it possible to compile m-files for speed.

Sent from: http://octave.1599824.n4.nabble.com/Octave-Maintainers-f1638794.html

reply via email to

[Prev in Thread] Current Thread [Next in Thread]