Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.programming > #5076

Re: compiling python

From BartC <bc@freeuk.com>
Newsgroups comp.programming
Subject Re: compiling python
References <39a759ea-06c0-4e33-93e8-6c5f99fa9303@googlegroups.com> <cPZrw.416147$Kl4.243354@fx01.am4> <fd777291-69c4-494a-91c6-6ee6c7b28467@googlegroups.com>
Message-ID <zh8sw.436765$td3.273392@fx34.am4> (permalink)
Organization virginmedia.com
Date 2015-01-10 11:45 +0000

Show all headers | View raw


On 09/01/2015 23:59, fir wrote:
> W dniu sobota, 10 stycznia 2015 00:50:35 UTC+1 użytkownik Bart napisał:

>>    a=b+c
>>
>> In a scripting language with dynamic types, what would you compile it
>> to? You don't know what the types are! They could be integers, floats,
>
> i think in most cases (code floe paths) you know, even if you dont know, they are one of the few probably so you could combine different versions and call the appriopriate once with strings once with integers..
> no? maybe they are to lazy to do that? 9wrote compiles as maybe it is a bit of work? idont know

If your aim is to get a faster Python, then there have been plenty of 
attempts, with varying success. Some might use type inference. (But 
PyPy, the most impressive I've seen, uses rather different methods.)

 >
 > this is the only reason?
 > still i dont see it clearly but it seem that teopretically with an 
amount of worc it could be compiled..

Perhaps you'd like to have go; source codes for Python are readily 
available.

(I've tried compiling for my own interpreter projects: translating 
naively to C source then compiling that. But it was slower than just 
interpreting! I think partly because it was no longer practical to use 
function inlining, and the code was more sprawling compared with a 
compact interpreter core.)

-- 
Bartc

Back to comp.programming | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

compiling python fir <profesor.fir@gmail.com> - 2015-01-09 15:36 -0800
  Re: compiling python BartC <bc@freeuk.com> - 2015-01-09 23:50 +0000
    Re: compiling python fir <profesor.fir@gmail.com> - 2015-01-09 15:59 -0800
      Re: compiling python BartC <bc@freeuk.com> - 2015-01-10 11:45 +0000
        Re: compiling python fir <profesor.fir@gmail.com> - 2015-01-10 07:09 -0800
    Re: compiling python Kaz Kylheku <kaz@kylheku.com> - 2015-01-10 19:19 +0000
      Re: compiling python BartC <bc@freeuk.com> - 2015-01-10 22:02 +0000
        Re: compiling python fir <profesor.fir@gmail.com> - 2015-01-11 10:52 -0800
        Re: compiling python Kaz Kylheku <kaz@kylheku.com> - 2015-01-11 19:24 +0000
          Re: compiling python BartC <bc@freeuk.com> - 2015-01-11 20:23 +0000
          Re: compiling python BartC <bc@freeuk.com> - 2015-01-24 15:01 +0000
            Re: compiling python Kaz Kylheku <kaz@kylheku.com> - 2015-01-24 16:58 +0000
              Re: compiling python Bartc <bc@freeuk.com> - 2015-01-24 19:18 +0000
                Re: compiling python Kaz Kylheku <kaz@kylheku.com> - 2015-01-24 23:54 +0000
                Re: compiling python Bartc <bc@freeuk.com> - 2015-01-25 01:26 +0000
  Re: compiling python Robert Wessel <robertwessel2@yahoo.com> - 2015-01-09 18:13 -0600
    Re: compiling python fir <profesor.fir@gmail.com> - 2015-01-09 16:27 -0800
  Re: compiling python Mok-Kong Shen <mok-kong.shen@t-online.de> - 2015-01-12 18:28 +0100

csiph-web