Class SyntaxPiece

Namespace

Hi.NcParsers.Syntaxs

Assembly

HiMech.dll

public class SyntaxPiece

Inheritance

object

SyntaxPiece

Inherited Members

object.Equals(object)

object.Equals(object, object)

object.GetHashCode()

object.GetType()

object.MemberwiseClone()

object.ReferenceEquals(object, object)

Extension Methods

DuplicateUtil.TryDuplicate<TSelf>(TSelf, params object[])

InvokeUtil.SelfInvoke<TSrc>(TSrc, Action<TSrc>)

InvokeUtil.SelfInvoke<TSrc, TDst>(TSrc, Func<TSrc, TDst>)

ColorUtil.GetGloomyColor(object, double, double)

NameUtil.GetSelectionName(object)

StringUtil.GetPropertyStringIfToStringNotOverloaded(object, bool, bool)

LockUtil.Lock(object)

Remarks

The design pattern of Sentence and JsonObject are one-one mapping.

JSON value type convention: Prefer base types (double, int) over string for numeric values in JsonObject. This applies to both parsing syntaxes and logic syntaxes. Strings should only be used when the value is genuinely textual (e.g., macro variable references like "#1", "Q2", coordinate IDs like "G54") or when the value cannot be parsed to a number. Use ParsingSyntaxs.FloatTagSetupSyntax, ParsingSyntaxs.IntegerTagSetupSyntax, or FloatParamPrefixes / IntParamPrefixes to store typed values at parse time.

Constructors

SyntaxPiece(Sentence, JsonObject)

public SyntaxPiece(Sentence sentence, JsonObject jsonObject)

Parameters

sentence Sentence

jsonObject JsonObject

Properties

JsonObject

public JsonObject JsonObject { get; set; }

Property Value

JsonObject

Sentence

public Sentence Sentence { get; set; }

Property Value

Sentence

Methods

ToString()

Serialize with Hi.NcParsers.Syntaxs.NcSyntaxUtil.Options to support NaN/Infinity.

public override string ToString()

Returns

string