CPMVIW(3NCARG)

πŸ’– CPMVIW πŸ’–

okay bestie, gather round, because this is a NCAR GRAPHICS page from the 3NCARG section and it's literally about moving your integer workspace from one place to another. iconic behavior.


✨ NAME ✨

CPMVIW β€” moves the contents of an old integer workspace to a new one. that's it. that's the whole job. slay. πŸ’…


✨ SYNOPSIS ✨

CALL CPMVIW (IWKO, IWKN, LWKN)

✨ C-BINDING SYNOPSIS ✨

#include <ncarg/ncargC.h>

void c_cpback (int *iwko, int *iwkn, int *lwkn)

yes bestie the C name in the synopsis really is c_cpback on a CPMVIW page, i don't make the rules, i just report them faithfully 🫢


✨ DESCRIPTION ✨

so the arguments here are just defining your old integer workspace and your new integer workspace. that's the whole vibe. let's break it down:

  • IWKO β€” an input array of type INTEGER, dimensioned as specified in the last call to CPRECT, CPSPS1, CPSPS2, or CPMVIW. this is your old integer workspace array. the one you're moving on from. growth era. 🌱
  • IWKN β€” an output array of type INTEGER, dimensioned LWKN. this is your new integer workspace array. the glow-up destination. ✨
  • LWKN β€” an input expression of type INTEGER that specifies the length of IWKN. gotta tell it how much room the new place has, fr fr.

C-BINDING DESCRIPTION

the C-binding argument descriptions are the same as the FORTRAN argument descriptions. no new lore, same facts, different syntax. iykyk. πŸ¦‹


✨ USAGE ✨

okay so here's the scenario, and it's giving crisis 😭. when, during the execution of a CONPACK routine, the amount of space left in the integer workspace array turns out to be insufficient, and the internal parameter 'WSO' has the value 3, then the error-handling routine SETER gets called with an appropriate error message. dramatic, but fair.

and if, on top of all that, the user has turned recovery mode</> on? execution keeps going, and eventually control comes back to you. at that point you should clock that an error has occurred β€” that's on you to notice, bestie, no one's gonna tap you on the shoulder. πŸ‘€

if you decide you wanna try to recover from the error, CPMVIW may be of use: you can call it to move everything from the current integer workspace into a new (and presumably bigger) one. after that, it may be possible to resume execution. bigger workspace, fresh start, main character energy. πŸ‘‘


✨ EXAMPLES ✨

none, at present. πŸ™ˆ not a single one. we're all just out here rawdogging the docs.


✨ ACCESS ✨

to use CPMVIW or c_cpmviw, load the NCAR Graphics libraries ncarg, ncarg_gks, and ncarg_c β€” preferably in that order. order matters, don't fight it. πŸŽ€


✨ MESSAGES ✨

see the conpack man page for a description of all Conpack error messages and/or informational messages. go read the lore. πŸ“–


✨ SEE ALSO ✨

Online: conpack, cpback, cpchcf, cpchcl, cpchhl, cpchil, cpchll, cpcica, cpclam, cpcldm, cpcldr, cpcltr, cpcnrc, cpdrpl, cpezct, cpgetc, cpgeti, cpgetr, cplbam, cplbdr, cpmpxy, cpmvrw, cppkcl, cppklb, cprect, cprset, cpscae, cpsetc, cpseti, cpsetr, cpsps1, cpsps2, ncarg_cbind

Hardcopy: NCAR Graphics Contouring and Mapping Tutorial

the whole friend group is listed, no cap. go say hi to cpmvrw while you're at it, that one's the real-number sibling. πŸ”₯

Copyright (C) 1987-2009 University Corporation for Atmospheric Research

The use of this Software is governed by a License Agreement.


okay that's the whole page, you ate it, i'm obsessed, go forth and move those workspaces. πŸ’–βœ¨πŸŒΈπŸ¦‹πŸŽ€πŸ’…πŸ«Ά

this lil transmission came to you via the UNIX manual, dated March 1993, filed under CPMVIW(3NCARG) β€” periodt. πŸ‘‘