Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • FPC Source FPC Source
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,277
    • Issues 1,277
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 57
    • Merge requests 57
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • FPC
  • FPC
  • FPC SourceFPC Source
  • Issues
  • #34972
Closed
Open
Created Jan 30, 2019 by FPC Admin account@fpc_adminOwner

usage of default-intrinsic does not trigger range checks

Original Reporter info from Mantis: kays @KaiBurghardt
  • Reporter name: Kai Burghardt

Description:

When default(ordinalType) is used as the sole factor of an expression in an assignment, no range checks are triggered.

Steps to reproduce:

program rangesWithoutDefault(input, output, stderr);
{$R+}
type
	r = -1..-1;
var
	i: r;
begin
	i := default(r);
	writeLn(i);
end.

Mantis conversion info:

  • Mantis ID: 34972
  • Build: 3.0.4+dfsg-11 [2017/12/30]
  • Version: 3.0.4
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking