Post Questions (V9)

[Rekd™]

Are there any functions in MP to parse strings? i.e. Instr(), Mid(), Replace() etc.

 

Is there a way to count ALL operations during posting the current MC9 file, even if some ops are set NOT to post?

 

Also, I see things like

 

fexist(sfilename2)

and

remove(sfilename2)

and

ex

 

I can guess what they're for (well, cept for EX), but are there more? Are they listed in my (extremely old) Post book that I haven't unpacked since the move?

 

 

Thanks!

[bryan314]

I'd contact you dealer about getting a v9 post proc cd. (Searchable pdfs, yeah) They're probably giving them away now that X is out.

 

As for parsing you could probably fake it with:

strstr -> is basically instring.

brksps -> will break a string into two strings at a position.

 

Bryan

[Rekd™]

Thanks Bryan. Took me a few tries to get the syntax right, but it's working now.

 

code:

---

	spathnc = brksps(strstr(sncf, spathnc), spathnc)

---

 

Is there anything close to instrrev() ??

 

Any other tidbits? Or are they listed in the CD?

 

[ 04-22-2006, 01:12 PM: Message edited by: Rekd ]

[Rekd™]

Is there a way to replace a string in a string?

 

I want to replace:

 

C:XXXXXX CUSTOMERSNCF FILESXX XXXXXXXXXXXXXXHOUSINGS680-003

 

with

 

C:XXXXXX CUSTOMERSSETUP SHEETSXX XXXXXXXXXXXXXXHOUSINGS680-003

 

TYIA

[Roger Martin from CNC Software]

There is not direct "replace that with this", but you can do it in a multi-step process using the MP string formulas; strstr and brksps

 

The code example below shows the addition of the pfixpath postblock (into the MPFAN.PST) which removes ‘soldstring’ from the ‘soriginalpath’ and replaces it with ‘snewstring’.

 

Resulting in this output ---

--------------

soriginalpath -> C:MCAMXCUSTOMERSNC FILESJob-680T.NC

--------------

snewpath -> C:MCAMXCUSTOMERSSETUP SHEETSJob-680T.NC

--------------

 

code:

---

soriginalpath  "C:MCAMXCUSTOMERSNC FILESJob-680T.NC"

snewpath ""

srepstring "SETUP SHEETS"

soldstring "NC FILES"

stempstr1 ""

stempstr2 ""

indexpos : 0

 

pfixpath

indexpos = strstr(soldstring, soriginalpath)

if indexpos <> 0,

[

# First part of string is now in ‘soriginalpath’

stempstr1 = brksps(indexpos, soriginalpath)

# Second part of string is now in ‘stempstr2’

stempstr2 = brksps(strlen(soldstring)+1, stempstr1)

# Stich ‘em all together

snewpath = soriginalpath + srepstring

snewpath = snewpath + stempstr2

]

 

 

psof$ #Start of file for non-zero tool number

 

"--------------", e$

"soriginalpath -> ", ~soriginalpath, e$

pfixpath

"--------------", e$

"snewpath -> ", snewpath, e$

"--------------", e$

---

Ah... I see you wanted this for v9

Just remove all the '$' (dollar signs) and it should work for v9.

[Chad 73]

Allright sombody hiding information

Where can i get more info on this stuff. I went to a post writing class and this wasn't in it. Is there anything or is it a undocumented bonus feature??

 

Thanks

[Roger Martin from CNC Software]

Hiding info?

No...

 

Even people who "know" and write posts may not be familar with the String Functions available in MP.

There aren't that many and very rarely used.

 

As Bryan said...

I'd contact you dealer about getting a v9 post proc cd. (Searchable pdfs, yeah)

[Rekd™]

Roger, using

 

code:

---

pfixpath

indexpos = strstr(soldstring, soriginalpath)

if indexpos <> 0,

[

# First part of string is now in ‘soriginalpath’

stempstr1 = brksps(indexpos, soriginalpath)

# Second part of string is now in ‘stempstr2’

stempstr2 = brksps(strlen(soldstring)+1, stempstr1)

# Stich ‘em all together

snewpath = soriginalpath + srepstring

snewpath = snewpath + stempstr2

]

---

Gives me this error...

 

"Variable not defined: if"

 

(it's on the "if indexpos <> 0" line)

 

[Roger Martin from CNC Software]

Looks like I many have lost the indentation of the 'indexpos = ...' line in my code sample. If you really have it starting in the first column as shown - that will not work. You need to indent it (at least one space).

[Rekd™]

 

It's nice to see MP being picky about it's syntax as well. (It's still pretty relaxed though )

 

I should have seen it. All is working nicely now. Thanks!