New to Python; what about #include, extern and function prototypes

Irmen de Jong irmen at -NOSPAM-REMOVETHIS-xs4all.nl
Sun Mar 7 13:42:54 CET 2004


Bo Jacobsen wrote:

> I'm been looking at perl and python, and I really like the strict syntax,
> handling
> of function parameters etc. Without include and function prototyping though,
> will probably have the effect that large source files, with a lot of
> function
> definitions at the top, will be generated. Not god.

Why do you think this is so?

Have a look at any Python example sourcecode (for that matter,
at some of the .py files from Python's standard library; for instance
cgi.py) and you will see that Python's import mechanism is working fine.
No big source files with lots of definitions at the top.
Just import the module which contains the definitions you need...


> Perl on the other hand has it all, including very productive features as
> built-in
> regular expressions, file scanning etc.

Python has the re/sre module for regular expression stuff.
File scanning is often done like this:
	for line in open("myfile.txt"):
		process(line)

> . ./filename
> Is the shell "include/execute" command.

Python's "include" command is the import statement.
If you really want (but WHY?) to read in and directly
execute another source file, use the execfile function.

--Irmen



More information about the Python-list mailing list