User:JimD: Difference between revisions
Content added Content deleted
(New page: More of a sysadmin than a programmer; but I am pretty handy in ''sh'' (Bourne shell and its ilk) and in Python. At times I've been pretty good with Perl, too.) |
No edit summary |
||
| Line 1: | Line 1: | ||
More of a sysadmin than a programmer; but I am pretty handy in ''sh'' (Bourne shell and its ilk) and in Python. At times I've been pretty good with Perl, too. |
More of a sysadmin than a programmer; but I am pretty handy in ''sh'' (Bourne shell and its ilk) and in Python. At times I've been pretty good with Perl, too. |
||
I've been touching up some of the Python entries and thinking about what sorts of tasks we might want to add to the mix. |
|||
:[[User:JimD|JimD]] 12:34, 18 October 2007 (MDT) |
|||
Possible Tasks: |
|||
* SQL CRUD: Implement the simplest possible SQL RDBMS client showing the following: Create a table (and insert data into it), Retrieve data from it, Update data into it, and Delete data from it; (optionally drop the tables as well). (These common actions are sometimes referred to as "database CRUD" by programmers). |
|||
* ORM Object Persistence: For OO languages which support ORM (object-relational mapper) modules, classes, libraries, extensions (or whatever term is used for the language in question) implement the simplest program which demonstrates object persistence. |
|||
* Co-processing: Implement a program which spawns a separate process and establishes a "co-process" relationship with it (the ability to dispatch work to the co-process and read back results when they are available). (In Python this might be down by creating a pair of pipes, using ''os.fork()'' then having the processes manipulate their ends of these pipes to arrange for some to be closed, and some of the remaining ones to be non-blocking; then perhaps having the parent write arithmetic expressions to its co-process and perform non-blocking polls for the results). |
|||
Revision as of 18:34, 18 October 2007
More of a sysadmin than a programmer; but I am pretty handy in sh (Bourne shell and its ilk) and in Python. At times I've been pretty good with Perl, too.
I've been touching up some of the Python entries and thinking about what sorts of tasks we might want to add to the mix.
- JimD 12:34, 18 October 2007 (MDT)
Possible Tasks:
- SQL CRUD: Implement the simplest possible SQL RDBMS client showing the following: Create a table (and insert data into it), Retrieve data from it, Update data into it, and Delete data from it; (optionally drop the tables as well). (These common actions are sometimes referred to as "database CRUD" by programmers).
- ORM Object Persistence: For OO languages which support ORM (object-relational mapper) modules, classes, libraries, extensions (or whatever term is used for the language in question) implement the simplest program which demonstrates object persistence.
- Co-processing: Implement a program which spawns a separate process and establishes a "co-process" relationship with it (the ability to dispatch work to the co-process and read back results when they are available). (In Python this might be down by creating a pair of pipes, using os.fork() then having the processes manipulate their ends of these pipes to arrange for some to be closed, and some of the remaining ones to be non-blocking; then perhaps having the parent write arithmetic expressions to its co-process and perform non-blocking polls for the results).