Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options
 
PerlMonks  

Re: Frivolous function names

by tadman (Prior)
on Dec 06, 2001 at 03:42 UTC ( #129804=note: print w/ replies, xml ) Need Help??


in reply to Frivolous function names

Whimsy, in the kernel?

while (is_computer_on() && !is_computer_on_fire()) { do_stuff(); }
From BeOS.

No, really.

As for semantics, I like to keep function names paired, such as Get/Set, Load/Save, Begin/End, Start/Finish and so forth, and try not to mix them.

The use of something like fetch_record() implies that it will try and retrieve it if possible, unless there is no record to fetch. However, get_record() may imply that it gets a record, even creating a new one of required. That get_record() might come back empty handed could be a bit of a surprise. It's like, "Hey! I asked for a record, where is it?"


Comment on Re: Frivolous function names
Download Code
Re^2: Frivolous function names
by davies (Vicar) on May 20, 2005 at 12:34 UTC
    IIRC, some of the old 68xx processors had undefined opcodes. Most of these were effectively NOP, but at least one sent the processor into a mad series of loops,and could be stopped only by powering the machine down. I always heard it called "HCF", standing for "Halt and Catch Fire". I never saw it for myself, but it had its fifteen minutes of fame.

    Regards,

    John Davies
Re^2: Frivolous function names
by Aristotle (Chancellor) on Dec 30, 2005 at 15:57 UTC

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://129804]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (6)
As of 2014-12-20 12:56 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (95 votes), past polls