Resourceful Code Reuse (Pragmatic Bookshelf)

PragmaticBookshelf
Reusing well-written, well-debugged, and well-tested code improves productivity, code quality, and configurability. It even takes some pressure off you as the software developer. Explore the benefits and drawbacks of seven popular code reuse models in Python and C so that you can start confidently reusing code at any development stage. Create static and dynamic libraries and adapt your code for the real world. Deploy functions remotely and then build software that accesses them using remote procedure calls. Don't lose it, reuse it!!

Dmitry Zinoviev @aqsaqal

edited by Adaobi Obi Tulton @aotulton

Get ready to take a deep dive into Python and C while learning to avoid the drawbacks and harness the benefits associated with seven common code reuse models. In no time at all, you’ll develop the confidence to reuse code at any stage of real-world development.

This one-stop solution covers the complete build cycle: editing, compiling, linking, and running a ready program. Apply Linux/macOS power software development tools, such as ld, ldd, ranlib, and nm, to construct and explore state-of-the-art function libraries in C that could be linked with application-specific code either permanently or for the duration of execution. Learn why Python has modules for reuse and how they differ from C object files and libraries. Understand the risks and other negative implications of sharing and reuse. As a bonus, distill the dependencies between your project’s components and automate and optimize your build process with the “make” utility.

Whether you are an amateur coder or an experienced developer, become a more productive and resourceful programmer by reusing previously written code.


Dmitry Zinoviev is a professor of Computer Science at Suffolk University in Boston and has a dual degree in Physics and Computer Science. He is passionate about C and Python programming, complex network analysis, computational social science, and digital humanities.


Don’t forget you can get 35% off with your Devtalk discount! Just use the coupon code “devtalk.com" at checkout :+1:

Latest Threads About This Book Top

New
Mikem3catsus
The term “BSS segment” is used just once in the document on page 24, but not defined. It would be helpful to explain what it is and/or wh...
New
Mikem3catsus
I didn’t know about the -MM switch in the c compiler - that’s really useful! In the Makefile example, on line 15, it should have the dep...
New
Mikem3catsus
I feel the author has overstated the challenges of decompiling back to source as an IP protection mechanism. Certainly you won’t get as c...
New
Mikem3catsus
I think it would be helpful to have a diagram showing how pieces of the jsontool.c file from pages 1-2 are split into the smaller files. ...
New
PragmaticBookshelf
Reusing well-written, well-debugged, and well-tested code improves productivity, code quality, and configurability. It even takes some pr...
New

Most Active This Week Top

Most Active This Month Top

Most Active This Year Top

Most Active Last Three Years Top

New

Most Active Over Three Years Top

PragmaticBookshelf
Reusing well-written, well-debugged, and well-tested code improves productivity, code quality, and configurability. It even takes some pr...
New
Mikem3catsus
The term “BSS segment” is used just once in the document on page 24, but not defined. It would be helpful to explain what it is and/or wh...
New
Mikem3catsus
I didn’t know about the -MM switch in the c compiler - that’s really useful! In the Makefile example, on line 15, it should have the dep...
New
Mikem3catsus
I think it would be helpful to have a diagram showing how pieces of the jsontool.c file from pages 1-2 are split into the smaller files. ...
New
Mikem3catsus
I feel the author has overstated the challenges of decompiling back to source as an IP protection mechanism. Certainly you won’t get as c...
New