What I mean is, of course, if the opening brace for the section is on the same line of a keyword that has a name as exemplified in the Subject.  Will Poser choke or treat the { as the opening brace instead of as part of the name?

Thanks,
Robert

Poser will tell you: "The file being read is not a valid Poser file"

When you close the error message, Poser will show the figure in some random diffuse color
but there is no actor or prop that can be selected from the drop downs.

The Hierarchy Editor will show all body parts, but treats the { as part of the name.

So Poser won't "choke", but you can't use the file for anything either, because you can't delete the item from the scene.

Martin

I suspect that even if Poser could cope with this, other programs that read Poser files probably wouldn't.

With some experimentation on a test CR2, it appears that Poser will handle incidents like this:

actor MyActor {

Don't know if it will handle spaces in the name part but I am assuming that any time an opening or closing brace is encountered it is parsed as such (unless in quotes etc.).

I suspect that Poser is using a state-machine type of parse to handle the nesting with braces as a token-by-token parse would be slow and less apt to handle names with whitespace properly.

Okay, so this works in Poser:

actor MyActor {

but this doesn't:

actor My Actor {

For my code, I'm going to go ahead and support either type - always considering a 'naked' { as a real section delimiter and not part of the name despite Poser's protestations under similar circumstances.
Thanks!