Recent Mailing List Items

Syndicate content
The mailing list for the Northfield Linux Users Group -- Northfield, MN USA. Please keep things on-topic in this list, and be certain to read the list rules: http://norlug.org/mailing-list/#rules
Updated: 1 hour 34 min ago

Re: [NORLUG] What is the best way to program in C?

1 hour 34 min ago
If your looking for a decent IDE for KDE try out Kdevelop

--
For archives and more options, visit this group at [link]
To unsubscribe from this group, send email to norlug-unsubscribe@googlegroup s.com

Re: [NORLUG] What is the best way to program in C?

1 hour 34 min ago
Althugh my approach has been to pick the language first, then find a project
I want to work on, if you've got a project in mind, I recommend picking what
seems to be the best (whatever that means) language and go for it.

--
For archives and more options, visit this group at [link]

[NORLUG] Speeding up Python

1 hour 34 min ago
Just read an interesting Python story:
[link]

<[link]>Talks about being able to compile
Python to c++ and from that to a faster binary than byte-code Python or
cPython.

A

--
Adam Gurno
a...@gurno.com

--
For archives and more options, visit this group at [link]

[NORLUG] What is the best way to program in C?

1 hour 34 min ago
Thanks for all the responses. As for an end goal, I guess I'm just
looking for something to do. But if I was to have some goals, it would
be to be more involved in the open source community or to author an
iPhone app. I will be using the new ubuntu release tomorrow, and I'll
look into the book that was first mentioned, the one written by the

Re: [NORLUG] Re: What is the best way to program in C?

1 hour 34 min ago
I learned my C from O'Reilly's _Practical C Programming_ (The Cow Book).
When I did C for a living, I used nothing more than Vim with 'set cindent'.
(When writing this, I realized that I purchased the cow book from UMM's
bookstore nigh on 20 years ago. That's crazy.)

Programming C with Vim:

Re: [NORLUG] Re: What is the best way to program in C?

1 hour 34 min ago
I think that if your goal is to learn C, then a Unix-based system is
easiest. Just get a text editor (with syntax coloring) and a terminal
window and edit/save/compile/run, edit/save/compile/run... So for this,
Linux and Mac beat Windows (unless you install cygwin on Windows, which
would give you the same effect).

Re: [NORLUG] Re: What is the best way to program in C?

1 hour 34 min ago
I recommend you stay away from any big IDE (VisualStudio, etc) and stick
with a plain text editor and compiler on the commandline. That setup is
equal on all platforms. Using an IDE sometimes "helps" you so much you dont
learn what is actually going on. If you want to learn the traditional way,

[NORLUG] Re: What is the best way to program in C?

1 hour 34 min ago
Thanks, I'll take a look. Is it besr to program in C on Windows or
Linux or OS X? Because I have all three...

--
Steven Carver

--
For archives and more options, visit this group at [link]
To unsubscribe from this group, send email to norlug-unsubscribe@googlegroup s.com

[NORLUG] Re: What is the best way to program in C?

1 hour 34 min ago
Thanks. I'll take a look. Also, is ut best to program C on a Windows
machine, or Linux?

--
Steven Carver

--
For archives and more options, visit this group at [link]
To unsubscribe from this group, send email to norlug-unsubscribe@googlegroup s.com

Re: [NORLUG] What is the best way to program in C?

1 hour 34 min ago
The best way, in my opinion, is to start with the basics. Pick one of the
three you have there and find a good book to teach it, and just sit down and
try to work with it. Which you pick is a matter of personal taste, but I
think C is a good place to start. For C, there is a great book: C

[NORLUG] What is the best way to program in C?

1 hour 34 min ago
Hi, new part of the mailing list. I live in Farmington, and I'm trying to
learn a bit of programming. I did some reading and discovered that it would
be best to learn C, C++, Objective-C... So where do I start? There are so
many resources that I'm overwhelmed. I do get the impression that you guys

Re: [NORLUG] Re: python question - copying a list or dictionary

1 hour 34 min ago
I suspect it's not so well-defined as "immutable types aren't copied." I think you have to investigate it on a type-by-type basis. Since tuples get used for things like packing function args and other internal uses (right?), it makes sense to optimize them to never be duplicated.

Small numbers and large numbers are both immutable, though: any operation on a number returns a new number. So large numbers are immutable, but get copied (for the reason Jeff described). Ruby and Lisp do a similar optimization. In Ruby, a variable slot is 32 bits, the high bit of which indicates whether it stores a Fixnum or an object reference. So you get 31-bit Fixnums, and Integers above that automatically become Bignums. Python appears to store small *positive* integers up to one byte:

Re: [NORLUG] Re: python question - copying a list or dictionary

1 hour 34 min ago
Python 2.6.4 (r264:75706, Apr 1 2010, 02:55:51)
[GCC 4.4.3 20100226 (Red Hat 4.4.3-8)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
True

Is immutability the key?
Small numbers are immutable, but large numbers are not??

--
For archives and more options, visit this group at [link]

Re: [NORLUG] Re: python question - copying a list or dictionary

1 hour 34 min ago
That strangeness has to do with how small integers are implemented.
Every reference to a small integer object (55 is apparently small enough
to be "small") is actually pointing to the same instance. Larger
numbers (e.g. 5555) act more like mutable types.

Python 2.5.1 (r251:54863, Feb 6 2009, 19:02:12)

Re: [NORLUG] Re: python question - copying a list or dictionary

1 hour 34 min ago
OTOH, is works strangely on immutable types:

Python 2.5.1 (r251:54863, Feb 6 2009, 19:02:12)
[GCC 4.0.1 (Apple Inc. build 5465)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
True 55 55
False 110 55

*shrug*

A

--
Adam Gurno
a...@gurno.com

[NORLUG] Re: python question - copying a list or dictionary

1 hour 34 min ago
I knew about "is" but didn't think to use it. As for dictionaries, no
"*" operation, so that answers that part of my question .

--
For archives and more options, visit this group at [link]
To unsubscribe from this group, send email to norlug-unsubscribe@googlegroup s.com

Re: [NORLUG] python question - copying a list or dictionary

1 hour 34 min ago
Python 2.5.1 (r251:54863, Feb 6 2009, 19:02:12)
[GCC 4.0.1 (Apple Inc. build 5465)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
False [] []
False [44, 'word', 5] [44, 'word', 5]
False [44, 'word', 5] [44, 'word', 5]

Copies copies everwhere, apparently.

[NORLUG] python question - copying a list or dictionary

1 hour 34 min ago
Simple question: if my_thing is a dictionary or list, will
x = my_thing*1
create a copy (rather than a reference)?

I'm aware of other methods of copying my_thing; just want to know if
the above is legit.

--
For archives and more options, visit this group at [link]

Re: Simple screenshooter?

1 hour 34 min ago
New version - doesn't require xmouse.so from mirage; uses xwininfo
from xorg-x11-utils:
"""
Screenshooter2.py
A simple screenshooter, modified from mirage
Copyright 2010 Rockdoctor <usdans...@gmail.com>
Version 2.04 20090317
Mirage Citation
Mirage, a fast GTK+ Image Viewer
Copyright 2007 Scott Horowitz <stonecr...@gmail.com>

Re: Simple screenshooter?

1 hour 34 min ago
After replacing gthumb with mirage as the image viewer for my now very
hacked up LXDE desktop, I decided to have another go at the screen-
shooter, just grabbing what I could from mirage. It works, I like it
(for now), and I don't need scrot, imlib, or giblib.
"""
Screenshooter2.py
A simple screenshooter, modified from mirage and uses its