Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Sounds like you have your solution, which is great. I have some suggestions for improving it. </p> <p>The method has a major usability problem, in that it is very confusing to understand (1) what the parameters going in mean, and (2) what the results coming out mean. Both are little puzzles that you have to figure out if you want to use the method.</p> <p>I would be more inclined to use the type system to make it much more clear what this method does.</p> <p>I'd start by defining a type -- perhaps a struct, particularly if it was going to be immutable -- called LineSegment. A LineSegment consists of two PointF structs representing the end point. </p> <p>Second, I would define an abstract base type "Locus" and derived types EmptyLocus, PointLocus, LineSegmentLocus and perhaps UnionLocus if you need to represent the locus that is the union of two or more loci. An empty locus is just a singleton, a point locus is just a single point, and so on.</p> <p>Now your method signature becomes much more clear:</p> <pre><code>static Locus Intersect(LineSegment l1, LineSegment l2) </code></pre> <p>This method takes two line segments and computes the locus of points that is their intersection -- either empty, a single point, or a line segment.</p> <p>Note that you can then generalize this method. Computing the intersection of a line segment with a line segment is tricky, but computing the intersection of a line segment with a point, or a point with a point, or anything with the empty locus is <em>easy</em>. And it's not hard to extend intersection to arbitrary unions of loci. Therefore, you could actually write:</p> <pre><code>static Locus Intersect(Locus l1, Locus l2) </code></pre> <p>And hey, now it becomes clear that Intersect could be an extension method on locus:</p> <pre><code>static Locus Intersect(this Locus l1, Locus l2) </code></pre> <p>Add an implicit conversion from PointF to PointLocus and LineSegment to LineSegmentLocus, and you can say things like</p> <pre><code>var point = new PointF(whatever); var lineseg = new LineSegment(somepoint, someotherpoint); var intersection = lineseg.Intersect(point); if (intersection is EmptyLocus) ... </code></pre> <p>Using the type system well can massively improve the readability of a program.</p>
    singulars
    1. This table or related slice is empty.
    1. PODetecting coincident subset of two coincident line segments
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USEric Lippert
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODetecting coincident subset of two coincident line segments
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the recommendations and extensions.
      singulars
      1. PO
      1. USJared Updike
    2. COThis is a great method Eric, I was previously using enums combined with other objects to provide a result. This is elegant and far superior. Thank you.
      singulars
      1. PO
      1. USArcane Engineer
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload