regarding pd tiny ... made me think about the perl tiny compiler program 
...Then the wheels started turning , and that lead me to this thought ???
 why isn't there a interpreted language like "perl from C" to C#
what this would mean is that you could program in a Highlevel language like 
perland have it work on all operating systems;so a perl for C#  "I really like 
that Idea" , then you say is it possible ???
I though about this for nasm then I realized that system table calls would be 
different for 
different operating systems which would make a lot more work ... "Lazy perl 
right LOL"

as I keep thinking about tho, That sounds like the best Idea ... a  C# 
Interpreted perl    ..is perl6 doing that ???  What would be needed to get 
something like that done ???
Advantages :: write once, build once, use one executable everywhere on all 
OS's...Disadvantages :: Don't know C# or how to build a module ... would take a 
long time to do ...
well just some thoughts .. maybe someone could clarify those ideas ..
Thanks 

-Mark 




  

     On Sunday, January 11, 2015 2:01 PM, "[email protected]" 
<[email protected]> wrote:
   

 Send Perldl mailing list submissions to
    [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
    http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
or, via email, send a message with subject or body 'help' to
    [email protected]

You can reach the person managing the list at
    [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Perldl digest..."


Today's Topics:

  1. Re: PDL::Tiny --- what should be in it? (Chris Marshall)


----------------------------------------------------------------------

Message: 1
Date: Sun, 11 Jan 2015 15:36:15 -0500
From: Chris Marshall <[email protected]>
To: David Mertens <[email protected]>
Cc: "[email protected]" <[email protected]>,    pdl-porters
    <[email protected]>
Subject: Re: [Perldl] PDL::Tiny --- what should be in it?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi David-

I think if we start trying to get something in the perl5 core we'll 
rediscover the pain that Stevan Little found.  Right now my thought was 
to use the existing perl5 MOP (i.e., Mo[o[se]) to generate the PDL::Tiny 
classes and using that information to generate the C object 
binding/implementation.  I'm looking at the Enlightenment Object model 
as a starting point for the C object model to avoid re-inventing the 
wheel.  One nice thing there is that the EO library can be called from 
either C or *real* C++ code so you can have the best of both worlds 
without the problem of forcing the use of a specific C++ compiler 
everywhere....

--Chris

On 1/8/2015 20:41, David Mertens wrote:
> Hey Chris, porters,
>
> I was thinking again about this project. One thing that occurs to me 
> is that p5mop-redux, Stevan Little's attempt at creating something 
> like Moose that could be pushed into core Perl, has been stalled for 
> many months. I am not sure if p5mop-redux has a very good C API; 
> indeed, I am not sure if it has a C object API at all. I wonder if we 
> might consider stepping in an lending a hand to help build a C object 
> API, which would serve as the foundation for the mop.
>
> If we had a solid C object system with the high potential of getting 
> pushed into the core, we would be in excellent shape to create the 
> next generation of PDL.
>
> Thoughts?
> David
>




------------------------------

_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl


End of Perldl Digest, Vol 116, Issue 7
**************************************


   
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl

Reply via email to