09-26-2019
It's an interesting example of how discredited programming methods get renamed to make them acceptable again.
- Self-modifying code? Obviously bad and never allowed, at all, ever.
- Self-installable plugins? Too useful to get rid of.
- Goto? The despised root of all programming evil. Never do this!
- Try/catch? Too useful to get rid of.
But renaming them, instead of teaching them as what they are, downplays their risks.
These 2 Users Gave Thanks to Corona688 For This Post:
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
being ordinary user (not having any administrative rights) can avail myself a facility to know who logged and logged out with their timings get popped onto my terminal as if it get echo 'ed... (3 Replies)
Discussion started by: vkandati
3 Replies
2. Ubuntu
I stumbled across a somewhat strange behavior of tar and find no explanation for it: i was testing a DVD for read errors and thought to simply tar the content and direct the output to /dev/null:
tar -cvf - /my/mountpoint/*ts > /dev/null
This way i expected the system to read the complete... (4 Replies)
Discussion started by: bakunin
4 Replies
3. IP Networking
Hi,
We have a website running on a local centos 5.4 surfer, static IP.
The domain.com uses no-ip.com to take care of the DNS, it forwards all to my server.
My router receives the port 80 call, routes it to my server and the world can see domain.com perfectly fine.
However, we cannot see... (3 Replies)
Discussion started by: lawstudent
3 Replies
4. UNIX for Dummies Questions & Answers
I have scheduled couple of shell scripts to run using 'at' command.
The o/p of at -l is:
$ at -l
1320904800.a Thu Nov 10 01:00:00 2011
1320894000.a Wed Nov 9 22:00:00 2011
1320876000.a Wed Nov 9 17:00:00 2011
$ uname -a
SunOS dc2prcrptetl2 5.9 Generic_122300-54 sun4u sparc... (2 Replies)
Discussion started by: superparticle
2 Replies
5. Shell Programming and Scripting
I have the below to direct the values to a xml file,
echo "<xml version="1.0">" >> /root/xml/sample.xml
but when the check the sample.xml file, the output looks like the below one(without double quotes)
<xml version=1.0>
but i want the output like
<xml version="1.0">
Any help on... (8 Replies)
Discussion started by: vel4ever
8 Replies
6. UNIX for Beginners Questions & Answers
Hi All,
I have a requirement to get the address values from a large log file along with the user details.
line1,line2,city,stateCode,postalCode,countryCode. The below code as advised in the earlier post is giving the user data
zgrep -B1 "Failed to calculate Tax" log.2018-05-23.gz | grep... (8 Replies)
Discussion started by: nextStep
8 Replies
LEARN ABOUT SUSE
glxcopycontext
GLXCOPYCONTEXT() GLXCOPYCONTEXT()
NAME
glXCopyContext - copy state from one rendering context to another
C SPECIFICATION
void glXCopyContext( Display *dpy,
GLXContext src,
GLXContext dst,
unsigned long mask )
delim $$
PARAMETERS
dpy Specifies the connection to the X server.
src Specifies the source context.
dst Specifies the destination context.
mask Specifies which portions of src state are to be copied to dst.
DESCRIPTION
glXCopyContext copies selected groups of state variables from src to dst. mask indicates which groups of state variables are to be copied.
mask contains the bitwise OR of the same symbolic names that are passed to the GL command glPushAttrib. The single symbolic constant
GL_ALL_ATTRIB_BITS can be used to copy the maximum possible portion of rendering state.
The copy can be done only if the renderers named by src and dst share an address space. Two rendering contexts share an address space if
both are nondirect using the same server, or if both are direct and owned by a single process. Note that in the nondirect case it is not
necessary for the calling threads to share an address space, only for their related rendering contexts to share an address space.
Not all values for GL state can be copied. For example, pixel pack and unpack state, render mode state, and select and feedback state are
not copied. The state that can be copied is exactly the state that is manipulated by the GL command
glPushAttrib.
An implicit glFlush is done by glXCopyContext if src is the current context for the calling thread.
NOTES
A process is a single execution environment, implemented in a single address space, consisting of one or more threads.
A thread is one of a set of subprocesses that share a single address space, but maintain separate program counters, stack spaces, and other
related global data. A thread that is the only member of its subprocess group is equivalent to a process.
ERRORS
BadMatch is generated if rendering contexts src and dst do not share an address space or were not created with respect to the same screen.
BadAccess is generated if dst is current to any thread (including the calling thread) at the time glXCopyContext is called.
GLXBadCurrentWindow is generated if src is the current context and the current drawable is a window that is no longer valid.
GLXBadContext is generated if either src or dst is not a valid GLX context.
SEE ALSO
glPushAttrib, glXCreateContext, glXIsDirect
GLXCOPYCONTEXT()